9 ms·
Microformats Wiki
- dane-pgp 4y agoI used to wonder "What would Social Networking look like if it were based on self-hosted pages written with microformats like h-card[0]?", but presumably the answer is "a privacy nightmare" (even more so than existing social networks). Perhaps a better answer to that question is "the Fediverse", which is based on ActivityPub. Unfortunately, though, there still seem to be open questions about how well/widely the Fediverse supports something like "circles" (the concept that Google Plus had) for selectively sharing content with different groups of people. [0] http://microformats.org/wiki/h-card http://microformats.org/wiki/h-card [1] https://rusingh.com/fediverse-google-plus-circles/ https://rusingh.com/fediverse-google-plus-circles/
- fsiefken 4y agoYes, this is something were facebook excels at, but it can also create in-group and out-group dynamics. A possible federated solution: https://beesbuzz.biz/blog/6128-Federated-access-control-with-Atom-and-WebSub https://beesbuzz.biz/blog/6128-Federated-access-control-with...
- madrox 4y agoThe specific idea, way back then, was DiSo [1]. Believe it or not, privacy wasn't the concern back then. The real problem was UX. Setting up and maintaining this stuff was Hard, and the network effect mattered a lot more in getting adoption. Facebook was really good at onboarding flows. OpenID lost to Facebook Connect for similar reasons. 1: https://diso-project.org/ https://diso-project.org/
- willnorris 4y agoUX definitely ended up being one of the hardest parts. We also never got to the point of really building a compelling product on top of the protocols. We did actually do some work on privacy though, but it never got super far. For example, you could set simple access controls on content that was only available to friends that logged in with an OpenID. I think I had it so that certain of your hcard attributes were only included for authenticated users as well. Some of the work we did then still exists today in various forms. Activity Steams led to Activity Pub, which has seen far more adoption than we ever did. And microformats are still widely used in some communities, though certainly not like it could have been, largely things to Google putting weight behind schema.org. For example, nearly all of the indieweb.org work is based around microformats at the core, with things like webmention, micropub, etc
- madrox 4y agoThe man himself! Thanks for chiming in.
- mawise 4y agoHaven[1] is my open-source, self-hosted side project for building exactly this (social networking based on self-hosted pages) in a privacy-first manner. There's a lot from the IndieWeb community that I want to emulate, and microformats is one of them--partly in order to create compatibility with the various MF2/IndieAuth client (phone) apps. My experience/opinion is that a circles-based approach is a usability nightmare since relationships are fluid and fuzzy, so Haven only has one "share group"--everyone with access to your Haven. That said, it's all built on open protocols (RSS), so it would be pretty straightforward for someone to fork it or build their own that implemented a circles-style approach to sharing. [1]: https://havenweb.org https://havenweb.org
- marginalia_nu 4y agoI don't get it. The big problem with the old meta tags is that nobody follows standards[1], and they were frequently abused to misrepresent the document in a favorable way (especially keywords and description). How would this help alleviate those problems? [1] To this day. I've learned, from building a parser for my search engine, you can't just select the <title> tag if you want the title of a page. You need to select the title tag in the <head>-tag. Otherwise you'll get the title-tags people semi-regularly use in the body as well... Like not just hobbyists. Found a major American university that used title-tags to wrap navigational links.
- soneil 4y agoI keep finding these when I least expect it and they've been fantastic every time - it usually means whatever I'm trying to automate is 90% solved for me. Scraping recipes from the bbc, flight reservations from my email, etc. If something includes schema.org/RsvpAction it probably needs to be actioned, if something contains schema.org/DiscountOffer it can probably go in the Noise folder. If someone starts sending spam containing flight reservation meta I'm going to be so sorely disappointed in the human race.
- marginalia_nu 4y agoI've gotten spam calendar appointments that my email client has helpfully added to my calendar so that I'm helpfully reminded of their spam sometime in the future with a push notification.
- logisticpeach 4y agoGood grief that has to be confusing. I'm often temporarily baffled by legit entries when notified, letalone strange or unexpected spam entries :)
- myfonj 4y agoPlus <title> tag is valid in SVG context, where it does what `title` attribute does on HTML elements (provides content for HTML tooltips and screen readers). And since inline SVG is valid in HTML, you can get valid title tags (from SVG namespace) outside HEAD element Plus if there wasn't TITLE in the head and is encountered inside BODY (not valid), it is adopted into the HEAD from document object model's perspective as if it was hoisted there (but it is not, just its value): data:text/html;charset=utf-8,<head> <!-- <title>not here</title> --> </head> <body bgcolor=dimgray> <svg viewbox="0 -15 80 20" fill=cyan> <title>SVG Tooltip</title> <text>Some SVG<text> </svg> <title>Title For Adoption.</title> <title>Second late title.</title> <p>And the title is: »<output id=o></output>«. <body onload="o.value = document.title"> <body text=snow> Resulting paragraph reads: "And the title is: »Title For Adoption.«." ("Yet unseen attributes" of the consecutive BODY tags are physically "hoisted" to real body node, but it's a different chapter.) Plus both <head> / </head> tags are optional — and implied — so "selecting title in head tag" can become very hard task, if taken seriously. Making HTML parser ain't easy.
- alpb 4y agoIt's worth noting Microformats is introduced 17 years ago, and was last updated about 12 years ago. It never really picked up traction, largely because players like Google have their own knowledge graph, and similar structured formats like RSS have lost their popularity since then.
- epeus 4y agoThat's not exactly accurate. The wiki has been edited recently, and change discussions are now done through github issues before updating the wiki, as that is more convenient than inline chat in many cases https://github.com/microformats https://github.com/microformats Also a lot of the practical discussion of microformats use is at the indieweb wiki - see https://indieweb.org/posts#Types_of_Posts https://indieweb.org/posts#Types_of_Posts for h-entry for example
- jillesvangurp 4y agoSEO was always a good argument to adopt some of the microformats. Search engines can make use of that to pick apart content. It's just that we have a few more tools than just microformats for that now; including some structural html 5 tags. What died out is attempts to do stuff with microformats via browser extensions. This was once a thing that e.g. MS did when they launched Edge. Those extensions have largely disappeared or just never really caught on.
- sleepyhead 4y agoGoogle prefers JSON-LD though[0]. Also I'm not keen on defining content with styling classes. [0] https://www.searchenginejournal.com/google-structured-data-preference/297479/#close https://www.searchenginejournal.com/google-structured-data-p...
- lawtalkinghuman 4y agoThe class attribute isn't just for styling though. See https://html.spec.whatwg.org/multipage/dom.html#global-attributes:classes-2 https://html.spec.whatwg.org/multipage/dom.html#global-attri... > authors are encouraged to use values that describe the nature of the content, rather than values that describe the desired presentation of the content.
- sleepyhead 4y agoTIL! So those obnoxious JavaScript frameworks using classes for declaring logic are actually valid???!!
- sleepyhead 4y ago> values that describe the nature of the content vs > rather than values that describe the desired presentation of the content. Or could it be that the meaning here is that you should write descriptive classes such as 'alert-box' instead of 'red-box'.
- oneeyedpigeon 4y agoBut that gets your "not just for styling" property for free — now another component can use the knowledge that the element is an alert box.
- jamietanna 4y agoAs mentioned in https://www.jvt.me/posts/2020/03/02/google-microformats-support/ https://www.jvt.me/posts/2020/03/02/google-microformats-supp... Microformats are still a recommended route
- cxr 4y agoPSA: the best way to enable Microformat-like stuff with almost no effort is to keep describing content with reasonable class names even if you never pay any special attention to the microformats.org standards. One unfortunate side effect of things like Tailwind CSS is that some folks with a single-minded focus on looks are now using only the Tailwind class names, but you can do both. If before you'd have written something like class="video-thumbnail" and styled the content with a class selector in your CSS, but now you've adopted Tailwind and have excised all the descriptive class name from the content (rather than just rming your stylesheet and adding Tailwind classes to whatever class names are already there), then please put the descriptive class names back in! And if you have colleagues submitting patches that remove class names because you're migrating to Tailwind, tell them to use Tailwind classes in a way that adds to the classification instead of as a replacement for traditional, descriptive class names. (A similar thing happens with CSS compilers. The autogenerated stuff served up on podcasts.google.com is nasty, for example.)
- firecall 4y agoYou could probably just chuck those class names in declaration anyway, even they werent attached to any styles! Of course, having well considered structured semantic works very well! For instance, with images, you can use attached caption markup to describe an images purpose and reference it in the written body of the document.
- a-priori 4y agoI'd argue that using the `class` attribute for describing the content of a field is overloading it, and that it should only be used for linking to CSS styles. You're better off using another attribute, e.g. some data-* attribute, for semantic information.
- chrisoverzero 4y agoThe HTML Standard disagrees: > […] authors are encouraged to use values that describe the nature of the content, rather than values that describe the desired presentation of the content. [*]: https://html.spec.whatwg.org/multipage/dom.html#global-attributes:classes-2 https://html.spec.whatwg.org/multipage/dom.html#global-attri...
- avgcorrection 4y agoThe data that you mark up might be micro but the markup isn’t.
- dang 4y agoRelated: Microformats: Still Relevant? - https://news.ycombinator.com/item?id=32285207 https://news.ycombinator.com/item?id=32285207 - July 2022 (1 comment) Google confirms microformats are still a supported metadata format for content - https://news.ycombinator.com/item?id=22521666 https://news.ycombinator.com/item?id=22521666 - March 2020 (40 comments) Ask HN: Is it worth it to implement HTML5 microformats? - https://news.ycombinator.com/item?id=14515178 https://news.ycombinator.com/item?id=14515178 - June 2017 (1 comment) Microformats are easy to learn, and pay off well in SEO and mobile - https://news.ycombinator.com/item?id=4328853 https://news.ycombinator.com/item?id=4328853 - Aug 2012 (4 comments) Ask HN: Micro-formats, are they still relevant/useful? - https://news.ycombinator.com/item?id=2702516 https://news.ycombinator.com/item?id=2702516 - June 2011 (2 comments) Ask HN: Microformats - Still useful? - https://news.ycombinator.com/item?id=1747657 https://news.ycombinator.com/item?id=1747657 - Oct 2010 (5 comments) Microformats.org at 5: Two Billion Pages With hCards - https://news.ycombinator.com/item?id=1583784 https://news.ycombinator.com/item?id=1583784 - Aug 2010 (1 comment) Ask HN: Micro formats? Or, how to make my site's google link look good? - https://news.ycombinator.com/item?id=1224242 https://news.ycombinator.com/item?id=1224242 - March 2010 (3 comments) Microformats: Boon or Bane? - https://news.ycombinator.com/item?id=987688 https://news.ycombinator.com/item?id=987688 - Dec 2009 (5 comments) Rest/ahah · Microformats Wiki - https://news.ycombinator.com/item?id=808251 https://news.ycombinator.com/item?id=808251 - Sept 2009 (1 comment) Google Announces Support for Microformats and RDFa - https://news.ycombinator.com/item?id=606126 https://news.ycombinator.com/item?id=606126 - May 2009 (8 comments) If the next "version" of the web is all about semantics, why aren't more people using microformats? - https://news.ycombinator.com/item?id=171818 https://news.ycombinator.com/item?id=171818 - April 2008 (34 comments) Consolidate and take back your social network with XFN, openID and microformats - https://news.ycombinator.com/item?id=29512 https://news.ycombinator.com/item?id=29512 - June 2007 (5 comments)
- T3RMINATED 4y ago
- epeus 4y agoBoth Mastodon and Tumblr have microformats support built in. Twitter and Facebook used to, but they decided they'd rather be silos than protocols
- jamietanna 4y agoSee also https://microformats.io https://microformats.io
- dalf 4y agohttp://webdatacommons.org/structureddata/#toc3 http://webdatacommons.org/structureddata/#toc3 The Web Data Commons project extracts all Microdata, JSON-LD, RDFa, and Microformats data from the Common Crawl web corpus