#idea: a microformat for download signatures/checksums, allowing browsers to automatically verify files without people having to go into the terminal and use
@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
@_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?
@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.
The medium with which you choose to express a message shapes that message — be careful it doesn’t contradict it.
articlemarkup — even js-generated markup is predictably disgusting
Everything about this is anti-web, practically screaming “ignore me”.
It’s already possible to use web action toolbelt to add indieweb reply/bookmark buttons to twitter.com and weave to expand POSSEd copies into full posts, but I think that’s as far as the “progressively enhance the twitter UI for indieweb support” train goes. Remaining pain points:
Pieces in place allowing a seamless transition from using twitter.com:
Pain points still to be resolved:
Playing with Yahoo Pipes for the first time. This is the UI I’ve been dreaming of for years. The data sources are bogged down with nasty RSS/ATOM semantics, but that’s mostly irrelevant. The important things:
I made a Pipe to convert #microformats2 h-feed/h-entry markup into RSS from scratch in about 15 mins, having never used the tool before (bear in mind also that this is not a tool built for consuming mf2 data structures): Convert Microformats to RSS. The tiny feedback loop the Pipes tool provides, both in deploying, sharing and debugging, enabled Tantek Çelik to find a bug in his site’s markup.
Again: WHY DOES NO-ONE KNOW ABOUT THIS? If it’s because processing stodgy, outdated, DRY-violating formats is its bread and butter, fair enough. Let’s rebuild this with microformats2.
v0.2.0 update to php-mf2 (BREAKING CHANGES) contains lots of goodness, including