@tomayac fixed on both copies — thanks!
@tomayac fixed on both copies — thanks!
@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.
@andycarter a favourite place of mine is Mandi, off Ingólfstorg (location on map below) — they do really good syrian wraps
@andycarter welcome to Reykjavík! You’re just round the corner from me :)
@bracki pity it doesn’t work on Squeeze (why is that?), as far as I can see it doesn’t depend on a particular version of PHP, just anything greater than 5.3.9 — "php": ">=5.3.9"
, to be exact.
@aral weird — isn’t that basically CC-BY-NC-as-a-service?
@karltryggvason a few thousand maybe? I’m not much good at judging crowd size.
@snarfed ah, I tend to scrape twitter.com using github.com/indieweb/php-mf2-shim as it’s forced to return results which are useful to humans :)
@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
@_minego links with the rel
semantic can be used both in human-visible markup for improved back-compatibility and quick error-spotting (as well as layering on top of existing solution) and also in HTTP headers for machine-only use
@_minego which existing clients would be broken by adding a classname or rel
value to the HTML page someone downloads something from, or a Link
header to the download itself?
Of course the more significant thing is UI considerations: how to offer this info to the downloader, how to explain what the various possible outcomes mean and what action the user should take as a result of them
@justincormack @janl possibly, human-visible links/keys less likely to go out of date, also better BC as easier for people with dumb browsers to manually verify than invisible header info
@sophiedennis haha yeah “dissociation” is the French word for trompette rhythms to go with the melody, abbreviated to “disso”. But if anyone could do disco gurdy, it’s Gregory Jolivet ;)
@t woah that looks amazing — also loving their detailed, transparent blog (very similar tone to blog.technical.io) and selfdogfood framing e.g. "what would we want on our own personal longboards?"
.
Presumably you’re already aware of the brain-controlled skateboard?
@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.
@roopagulati thanks! Currently mainly working on improving my pizza technique — I can do pretty good sourdough bases now, just bought a pizza stone and it’s had a huge effect. Pizza is now crispy but flexible and a little charred on the bottom.
@_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?
@seldaek apparently you can! packagist.org/packages/barnabywalters/gist-test#v0.1.0 Agreed it’s unlikely to be optimal for a lot of cases, but worth experimenting with reducing code sharing friction and boilerplate