@_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
@_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 :(
.Jeremy Keith @shanehudson @indiewebcamp et al: php-mf2 is now dependencyless, go forth and build stuff with #microformats! Thanks to Aaron Parecki for writing the URL resolution code.
From now on I am framing all web standards-type discussions with the question “what is it reasonable to demand that authors do”
For example, it’s not reasonable to demand authors publish content in more than one format. It’s not reasonable to demand that authors learn how RDF works. It is reasonable to require authors to publish HTML. It is reasonable to require authors to add some simple microformats like rel-author, h-entry or h-card.
Aaaaand… @appdotnet rolls out support for #microformats2! Great work @voidfiles.
Et tu @twitter? It’s never too late to catch up :) Previously: waterpigs.co.uk/notes/4QqDmw
The revolution will be marked up with microformats2
Aral Balkan best place to start is h-card on the homepage (with rel=me on twitter/email links) and h-entry on your notes. All the mf2 vocab pages have examples on, and let me know if you run into any problems — we’re always looking to make the docs better.