1. php-mf2 users: requesting your feedback for Mf2\fetch() microformats-from-URL function just added to dev-master. I want to get this nice and polished before adding it to a versioned release, and would appreciate feedback, specifically on the documentation and debugging support.

  2. Thoughts about whilst reading Lakoff’s Women, Fire and Dangerous Things — mf vocabularies e.g. h-card, h-entry, h-event are basic-level categories, the level at which:

    • it is easiest for humans to learn and reason about,
    • we have the shortest, most common names for them,
    • defined by how we interact with them

    E.g. h-entry ≈ “post”

    • short name
    • extremely common on the web
    • well-defined interaction patterns e.g. writing, posting, replying, reading, browsing through a feed, searching for/within, liking, reposting, quoting etc.

    Rather than RDF or schema.org which seek to create pure, objectivist, hierarchies of categories — our brains simply don’t work like that.

  3. Last night: built commenting on posts direct from my feedreader using — video demo:

    Example replies sent using this technique: 1, 2

    Next up: cleaning code, implementing likes, distilling learnt knowledge into diagrams, code.

    Futher reading:

  4. Thomas Steiner: Getting started w/ #microformats2 http://microformats.org/2014/03/05/getting-started-with-microformats2 …. @BarnabyWalters, is http://waterpigs.co.uk/php-mf2  100% correct w/ single elem & > 1 type?

    @tomayac for example like this?

    <a class="h-card h-org">Hypothetica Inc.</a>
    

    php-mf2 gives

    {
        "items": [
            {
                "type": [
                    "h-card",
                    "h-org"
                ],
                "properties": {
                    "name": [
                        "Things"
                    ]
                }
            }
        ],
        "rels": [
    
        ]
    }
    

    which is correct, one microformat with multiple vocabularies, which effectively allows multiple vocabularies to be mixed, e.g. you can have a h-review which is also an h-entry.

  5. Jon Zuck: Anyone still using microformats? Their site seems out-of-date; says to use microformats2, but most documentation is for old formats.

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

  6. Aitor García Rey: @BarnabyWalters Base format to describe a recipe (not only in html contexts) as source for apps and recipe repositories.

    @_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?

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

  8. Joschi Kuphal 吉: @BarnabyWalters Implemented the authorship algo today https://github.com/jkphl/micrometa  — What's considered best practice to determine authorship >

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

  9. 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)

    • hosted on google silo
    • long complex ugly URL
    • presentation tied to paged dead-tree media with ugly results: text breaks across artificial “pages”
    • no author URL, just corporate silo email, and email != web
    • javascript required
    • no microformats2 or even semantic HTML article markup — even js-generated markup is predictably disgusting with vast quantities of nested divs and spans with inline styles
    • 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:
      the body text is tiny and does not wrap, the high-traffic warning is truncated and unreadable

    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
    • Author attributed by name+personal (non-silo) URL, with profile photo/logo for quick human association