tantekI'm having trouble justifying learning / dealing with the particular usage of those tags - given they seem to have no impact in any browser or any other consumer
tantek.comedited /h-entry (+480) "/* Issues */ subheads for specific issues, note clustering of current bad hentry properties issue examples, analysis, hypothesis, proposal resolution" (view diff)
tantekGWG - very rarely do they say "no one adopted **our** standard" - quite the opposite, creators of standards are nearly always extremely defensive (emotional attachment) about **their** standard.
tantekHowever, since the collossal failure of XML to replace HTML, it has become more acceptable for someone e.g. in W3C to say "no one adopted (or bothers with) *this* standard" about some other W3C standard
tantekthe hard part is figuring out rationally what amount of time is "as fast as possible" as sometimes (often) it takes *years* to gather adoption/reaction data to a standard
KartikPrabhuI have seen arguments that microformats is antiquated since "most people" have not adopted it and its proliferation is only due to default use in Wordpress themes
tantekKartikPrabhu: to be fair, there were several key issues with classic microformats that took us a while to gather data on to understand the depth/nature of, and incorporate solutions into microformats2
tantekwhich we are fixing with microformats2, and driving it by *requiring* real world use-cases *before* adding *anything* (properties or new formats)
tantekand not realizing that they're making all the same assumptions / statements about JSON being "it" for APIs etc. the way they were about XML being "it"
tantekbtw - re: before about bad hentrys - aaronpk, kylewm I didn't see any objections to *not* implying properties when doing backcompat parsing of microformats
@tStable 5+ years, yet any browsers do anything special with #HTML5 article aside figure footer header nav section tags? (ttk.me t4Zt4) (twitter.com/_/status/549788622099345409)
tantekno real pattern to like post slugs - most put nothing, second most put some sort of auto-slug of the post they're liking, even if the liked post has no slug of its own
tantekupon consideration, putting a slug on a like (especially more of a slug than the liked post) seems like a bad idea as it potentially does more "SEO" than the original liked post, which seems like bad form from a community / peer respect perspective
tantekcan't think of a good use-case for a slug on a like post, and can think of downsides (any form of out-SEOing the liked post or author thereof), thus going with no slugs on like posts for now.
tantekin order to make storing like posts as minimal/efficient as possible, I'm re-assessing/questioning all aspects of everything I store about a post in my flat file storage
tantek.comedited /Red_Wind (-13) "drop initial == Description == subhead as it is self-evident, moves relevant content further up, adjust icon size to fit better" (view diff)
tantekKevinMarks: "When weird nerds watch the cool kids jockeying for social position on Twitter, we see no difference between these status games and the ones we opted out of in high school." <--- guess what, we *are* the weird nerds opting out of social position on Twitter *AND* Medium - unlike the article
tantekI believe I may have put them there only as legacy thinking from when id attributes were an essential part of the permalinks of my blog posts (2002-2008)
tantek.comedited /like (+1132) "/* Brainstorming */ order clusterings in reverse time order as they would be if stacked individually, note special case of two with "and" no commas" (view diff)
KartikPrabhu, eburcat_, gRegor` and asdofindia joined the channel
brettantek: iirc safari reader view button was a fork of the early readability open source code... which uses some combination of microformats and semantic html tags :) https://readability.com/developers/guidelines
LoqiThe sidefile-antipattern is a violation of the DRY principle by the use of secondary files (typically in some one-off XML format) to provide information that is a duplicate of information available in primary files on a website (in HTML), and is an antipattern due to typical DRY violation problems such as out-of-date, missing, corrupted, or outright false data https://indiewebcamp.com/sidefile
kylewmthinking about the "isn't it just wordpress" confusion from yesterday; i do feel like the homepage could do a better job answering the question at the top "What is the IndieWeb?"
LoqiThe indieweb is about owning your domain and using it as your primary identity, to publish on your own site (optionally syndicate elsewhere), and ownyourdata https://indiewebcamp.com/indieweb
LoqiThe indieweb is about owning your domain and using it as your primary identity, to publish on your own site (optionally syndicate elsewhere), and ownyourdata https://indiewebcamp.com/indieweb
tantekso that's the fundamental challenge to people that don't get why/who indieweb is different from blogs / wordpress / decentralized monoculture hooha
kylewmmaybe my proposal would be, move the "Your content is yours/ you are better connected /you are in control" block above "What is the IndieWeb?" and bolster the "people focused alternative to the corporate web" with the practical description "publishing on your own site"
LoqiThe indieweb is about owning your domain and using it as your primary identity, to publish on your own site (optionally syndicate elsewhere), and ownyourdata https://indiewebcamp.com/indieweb
voxpelliNever made a 2015-01-01 commitment, but sort of worked on a feature anyway: There's now interaction support and facepiles on https://webmention.herokuapp.com/ !
voxpelliKevinMarks_: The data is there now, but I haven't pushed the facepiles out to existing embeds because that would require everyone to update the styling of their sites
voxpelliRight now I pushed the facepiles it to a new experimental embed and I will push a new opt-in embed version with it eventually – would preferably want some feedback/experience on the new facepiles first though
voxpelliKevinMarks_: If you like to test it before that you can try it right now if you like by adding a version=cutting-edge query param to the /api/embed script that you include – but I will push other experimental stuff eventually as well, so should move to a new stable embed soon
ben_thatmustbemepretty soon I plan to start a cordova app to do some things such as an mp-client and hopefully notifier. I think getting indieauth methods correct will be the most complex bit though
tantekI was thinking about this - all it does is send the person a duplicate on their original (via Bridgy), and give more credence/relevance to silo copies