1. @benwerd loving your work on idno! Just had a look at the source, great that you’re using 2, I have some suggestions/corrections:

    • .h-entry is better off where you’ve got .idno-entry so then the author .h-card can be scoped into the entry
    • add .p-author to the .h-card for each .h-entry to explicitly declare authorship
    • put .h-as-* on the same element as .h-entry .idno-entry
    • put .u-url where you currently have .dt-published, move .dt-published to the time element

    Thanks to Aaron Parecki you can see how a page is parsed here, or use my php-mf2 demo sandbox for experimentation by hand.

  2. Aitor García Rey: In fact, I’ve been playing for a very long time with the idea of creating a service for lowering the entry barriers to use personal domains.

    @_aitor what are you up to on the 22nd/23rd? We're remote participating indiewebcamp.com, it'd be great to talk about this stuff with you, drop into the office if you're free?

  3. Why is structured querying of your personal data important? Self-reflection.

    Example in point: seeing what I’ve quoted, from who, about what, and what I’ve said about the quotes. How it’s changed over time. How I talk about it and present it in my personal context. From a technical point of view; how I mark it up.

    Twitter does the opposite of this, and encourages us to throw away our history, much less peruse it and learn from it. Facebook aims to present a glorified timeline emphasising the most “important” events in our life. I feel neither are particularly valuable.

  4. It’s funny — people are saying so much about the /federated social web not being a “Facebook Killer”, and yet it’s killed my usage of FB beyond occasional passive consumption.

    So, implementors: build stuff which kills your own FB usage before trying to kill facebook.

  5. Sandeep Shetty: PubSubHubbub (by Google for Google) or any push based solution for the web is unnecessarily complex for #indieweb. Polling works just fine.

    sandeepshetty hm, I'd actually say push based systems are super useful (certainly I have personal use cases which are too big for me to want to poll) but PuSH is way too complicated. It’s actually something I’m working on improving, as you did with Pingback => webfinger

  6. After RSVPing the local meetup tonight, I get an email with shared signup details for wp10.wordpress.net so I can post my photos from the party to their site.

    This is another, rather bizarre example of WordPress promoting monoculture. Even funnier is this misguided quote from the email:

    If you don't already have the WordPress mobile app for your smartphone, you'll want to download it so that you can upload pictures and post to the site right from the party. It would be a good idea to add the site to your mobile app before your party so you don't have to worry about it later.

    Paraphrased: “So that you can participate TO THE MAX, post to our hosted silo and download yet another app that you’ll delete straight away”.

    Nevertheless, I plan to download the app and try it out as I’ve never used it before and WordPress UX tends to be pretty good. Perhaps then discuss the whole thing in on freenode to brainstorm a better way of doing this topic-based aggregation.