#microformats 2018-01-15

2018-01-15 UTC
#
gRegorLove I'm interested in examples where it's causing a problem currently, slightly different than adding the ability to remove already-authored mf2.
#
gRegorLove WordPress might have some examples
#
aaronpk The quickest way i find these examples is by looking at the reply context or comments on my site, as well as looking at the feeds I'm following in Monocle
#
aaronpk all those use XRay which has all the logic for deduping name/content so when something looks bad there I investigate further
#
gRegorLove To clarify, I mean the "any properties should block implied p-name" case. I think we have enough examples of "any p-* should block implied p-name"
#
gRegorLove So looking for examples with a messed up implied p-name that does not have any p-* properties
[cleverdevil], KartikPrabhu, echarlie and [tantek] joined the channel
#
[tantek] reads backlog
#
[tantek] Gregorlove's reasoning is on the right track
#
[tantek] I do like and see the appeal of adding any explicit e- props as also stopping an implied p-name. The e-content example makes sense there
#
[tantek] Yes re smaller change less likely to result in unexpected outcomes (braking things)
[jeremycherfas], nitot and [tantek] joined the channel
#
@ummjackson @pfrazee To be frank, I think most of the standards existing decentralized social protocols have used are ridiculously tedious and a pain to work with. Microformats for example 🙁 (twitter.com/_/status/952813149849239552)
[pfefferle], KartikPrabhu, barpthewire, nitot_, adactio, nitot and [kevinmarks] joined the channel
#
[kevinmarks] Ignore that chap, engage with this one https://twitter.com/pfrazee/status/952653827840278529
#
Loqi [@pfrazee] f you're the sort of person that has strong feelings about JSON-LD, ActivityPub, etc., now's a good time join our Beaker issue about how to handle app compatibility and decentralized development. All ideas are on the table! https://github.com/beakerbrowser/beaker/issues/820
#
@kevinmarks @ummjackson @pfrazee If you think microformats are tedious, try parsing sites from multiple vendors without any agreement on naming elements. (twitter.com/_/status/952853847046852608)
#
@csarven @kevinmarks @ummjackson @pfrazee That's literally the core issue with mf. Recall u-utility, u-sizeViewHeightMin100.. how you think that your usage is correct and others should change their definition? I thought so. I suggest brushing up on https://web.archive.org/save/http://microformats.org/wiki/namespaces-inconsistency and then proceed as usual by handwaving :) (twitter.com/_/status/952858849094103041)
#
@csarven @kevinmarks @ummjackson @pfrazee That's literally the core issue with mf. Recall u-utility, u-sizeViewHeightMin100.. how you think that your usage is correct and others should change their definition? I thought so. I suggest brushing up on https://web.archive.org/web/20170522154207/http://microformats.org/wiki/namespaces-inconsistency-issue … and then proceed as usual by handwaving :) (twitter.com/_/status/952859425894780928)
barpthewire, nitot and [tantek] joined the channel
#
[tantek] Hmmm arguments about decentralized protocols ... on Twitter. Is this like an annual irony performance?
webchat117 joined the channel
#
[tantek] (Not the beaker folks, who are clearly using twitter for distribution here to invite folks to discuss the issue, but the others just arguing)
#
[tantek] I suppose GitHub is becoming the (issues) silo we go to now due to UX? Seems to be sucking in nearly all open source and open standards efforts.
[kevinmarks] joined the channel
#
[kevinmarks] I like what the Beaker Browser people are doing in a broad sense, but there is a reinventing the web as json thing going on too.
#
[kevinmarks] Fritter is nicely done.
#
sknebel does Mastodon/ActivityPub have a way to follow keywords yet? Maybe Loqi is just missing some of what's going on...
#
sknebel and yes on the GitHub thing. Even GitLab I don't see often, and the discussions around old-fashioned projects can get grating ("why do they not use github like evryone else, mucheasier?!!")
#
sknebel (to be fair, random mailing-lists or old, broken redmine installs as bugtrackers *are* less nice to deal with)
#
Zegnat I think the biggest UX problem with issue trackers is that most of them require login, thus require you create yet-another-account. A lot of developers have GitHub accounts already so that does not suffer from the same problem.
[pfefferle] and nitot joined the channel
#
aaronpk edited /app (+45) "link to indieweb brainstorming of h-app" (view diff)
#
@kevinmarks @csarven @ummjackson @pfrazee No need for that tone. There is a pattern where each silo says "add custom markup to your site for us" to make their lives easier. Microformats tries to converge that. The "replace your entire website with bespoke json and a custom parser" approach has problems too. (twitter.com/_/status/952922892001579011)
nitot, [kevinmarks], vivus and gRegorLove joined the channel
#
sknebel Zegnat: true, for a seperately hosted issue tracker a login-by-mail option sounds like a good idea, if you do not want to allow anonymous access
#
@wpulsarblog Author hReview Plugin Review in 2017 + WPRichSnippets https://www.wpulsar.com/author-hreview-plugin/ (twitter.com/_/status/953001506306916353)
[kevinmarks] and [miklb] joined the channel