↪
Joschi Kuphal 吉:
@BarnabyWalters href attribute in https://github.com/sandeepshetty/authorship-test-cases/blob/master/h-entry_with_rel-author_pointing_to_h-card_with_u-url_equal_to_u-uid_equal_to_self.html …, testing fails atm. Should this be fixed in php-mf2 or the test file?

@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.

no microformats2 or even semantic HTML article markup — even js-generated markup is predictably disgusting

Redirecting to different (non-canonical? difficult to tell due to ugliness) URL due to large amounts of traffic, likely indicative of infrastructural problems or incorrect medium

Broken on mobile devices:

Everything about this is anti-web, practically screaming “ignore me”.

Improvements:

Host on personal site or project commons with CC license

Short, consistent, readable URI

Static semantic HTML with microformats2 h-entry for easy citations, archival and replying, no JS required — this would also solve infrastructural problems as HTML is pretty easy to serve and much faster than JS-rendered DOM-heavy “documents”applications

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:

Ads and other UI noise

Lack of good search

Lack of control over timeline — lists, following and blocking are the only ways to control what you see

How to fall back to subscribing to someone’s twitter feed if they don’t publish their notes on their own site?

Whether or not to support ATOM+RSS — sure there’s a lot of it around, but it’s a nightmare, and I don’t want to encourage publishing invisible DRY-violating data. Perhaps superfeedr’s normalisation will be of use

What to do about all the wordpress blogs around with half-baked microformats support — auto-detect and use their ATOM feed? Try to find a related twitter account?

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:

Live, context-sensitive debugging. Want to know what the data looks like at a particular point in the graph? Click there. What if I change this parameter? It updates. WHY ARE PEOPLE NOT RAVING ABOUT THIS? THIS IS HUGE!

All parameters are programmable, but with the ability to specify defaults

Everything is declarative — not only textually, but visually.

One-click publish and deploy, with facilities to create basic UI and pre-fill it

Ability to clone and reuse pipes — each pipe is a module you can use in other pipes. Take someone elses pipe and view source, change it, reuse it.

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.

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.

↪
Aral Balkan:
@BarnabyWalters Will definitely look into it :) Any suggestions that pop out at you?

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.