@justincormack @janl possibly, human-visible links/keys less likely to go out of date, also better BC as easier for people with dumb browsers to manually verify than invisible header info
@justincormack @janl possibly, human-visible links/keys less likely to go out of date, also better BC as easier for people with dumb browsers to manually verify than invisible header info
@sophiedennis haha yeah “dissociation” is the French word for trompette rhythms to go with the melody, abbreviated to “disso”. But if anyone could do disco gurdy, it’s Gregory Jolivet ;)
@t woah that looks amazing — also loving their detailed, transparent blog (very similar tone to blog.technical.io) and selfdogfood framing e.g. "what would we want on our own personal longboards?"
.
Presumably you’re already aware of the brain-controlled skateboard?
@frimmin people are indeed using microformats, classic docs are still majority of the wiki but mf2 vocabs all documented microformats.org/wiki/microformats2#v2_vocabularies, open source microformats.org/wiki/parsers available, validation tools e.g. indiewebify.me
A lot of microformats activity in the indiewebcamp.com community enabling things like cross-site comments/likes/reposts/rsvps, link previews, autodiscovery, feed readers just beginning development.
@roopagulati thanks! Currently mainly working on improving my pizza technique — I can do pretty good sourdough bases now, just bought a pizza stone and it’s had a huge effect. Pizza is now crispy but flexible and a little charred on the bottom.
@_aitor “apps/repositories” not specific or user-focused enough to base improvements/requirements on — what is the data being *used* for, in terms of the people using the UIs you want to build?
E.G. do you want people to be able to search based on ingredient(s)? Or find only recipes which can be made within time available? Or to offer a UI to convert quantities into units the cook is more familiar with? Or to scale quantities depending on the number of people the cook is making food for?
@seldaek apparently you can! packagist.org/packages/barnabywalters/gist-test#v0.1.0 Agreed it’s unlikely to be optimal for a lot of cases, but worth experimenting with reducing code sharing friction and boilerplate
@_aitor what is the use case and how does h-recipe fail to address it? #microformats IRC on freenode is a better place to discuss it than twitter
@voxpelli thanks for the links, auphonic looks like a great service! Certainly going to look into using that for automating stuff like audio encoding.
@benwerd …owls?
With tentacles?
@emckean feed my lizard
@crispinwalker you’ve been doing Pratchett—inspired morris dancing? That is all kinds of awesome
@Jack_Way such nonsense is why my github profile photo stubbornly remains geometric shapes. I already gave them my URL, just get the favicon or parse the h-card photo out instead of using SPOF silo.
@aaronpk and accepting a reply from the same UI :) This calls for cake — going to have a go at those cookie recipes you posted!
@igorwhiletrue thanks! I was aware of stackphp/run
, but wondered if there was an alternative which left the run method in place — Silex is such an exquisitely designed and concise abstraction it’s a pity to have to give that up and introduce extra packages, namespaces and functions (more surface area to learn and remember).
@jkphl hm that’s an interesting case — href
is technically a url-potentially-surrounded-by-spaces, question is whether or not it’s php-mf2’s responsibility to strip out the spaces in u-
properties. I’d say it is, as those spaces are never going to be useful data which we’re throwing away, so opened an issue.
@jkphl great work! There are a few different scenarios, indiewebcamp.com/authorship covers some e.g. follow rel=author
and parse for h-card. There are some other heuristics in use like looking for author
on h-feed
(e.g. my homepage), not yet documented but should certainly be in the spec.
@benwerd chain emails spreading works of art? That’s a new one on me. Sounds like fun!