@bromann all the interesting work being done in the indiewebcamp.com community (e.g. cross-site comments are being done with mf2, and they’re easier to author+more clearly documented than classic mf, so makes a lot of sense to start using now!
@bromann all the interesting work being done in the indiewebcamp.com community (e.g. cross-site comments are being done with mf2, and they’re easier to author+more clearly documented than classic mf, so makes a lot of sense to start using now!
@bromann even better (and easier!), add microformats2 h-card microformats.org/wiki/h-card, validate with indiewebify.me/validate-h-card
#idea: a microformat for download signatures/checksums, allowing browsers to automatically verify files without people having to go into the terminal and use shasum
or gpg --verify
@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.
@_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?
@_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
@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.
Beginning experimentation with tipping UIs: added BTC and DOGE tipping links to homepage with rel-payment
and experimental u-x-payment
, documented a bunch of tipping UI examples on microformats.org/wiki/payment-examples
The medium with which you choose to express a message shapes that message — be careful it doesn’t contradict it.
Case in point: A Rational Web Platform (via @brucel)
article
markup — even js-generated markup is predictably disgusting Everything about this is anti-web, practically screaming “ignore me”.
Improvements:
#indieweb goal: by 2014-01-01, no longer be using twitter.com to read+reply to my friends’ content.
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:
Just released php-mf2-shim v0.2.2. New in this version: improved twitter.com parsing, now scrapes h-card and h-entries from profile pages #microformats #indieweb
.@aaronparecki noted, updated mine to include URI component encoding, also added ability to toggle between results and original page. #microformats
@johnbhartley yep, ready for real-world use and consumed by various people, but still a good idea to include classic hCard markup too. Same for all the other microformats2 vocabularies
@johnbhartley good question — covered in the hCard FAQ, it’s enough of an issue that we fixed it in the microformats2 vocabularies e.g. h-card — naming is now consistent and predictable.
.@julien51 URLs are worth caring about, data formats shouldn’t make them worthless. #microformats #indieweb
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
mf2
→ Mf2
)Go get it now from Packagist, or try it out at pin13.net/mf2
Discuss adding #microformats to @duckduckgo special result pages here: duck.co/topic/add-microformats-to-results
Unfortunately page has a JS error on FF Nightly :(