Everybody on Twitter wants to know where to go now. The answer is your own website, syndicating out to wherever else people end up. This is the IndieWeb. Let me know if you’d be interested in a talk about how to get set up.
{
"type": "entry",
"author": {
"name": "Kimberly Hirsh, PhD",
"url": "https://kimberlyhirsh.com",
"photo": "https://avatars.micro.blog/avatars/2022/8984.jpg"
},
"url": "https://kimberlyhirsh.com/2022/04/25/everybody-on-twitter.html",
"content": {
"html": "<p>Everybody on Twitter wants to know where to go now. The answer is your own website, syndicating out to wherever else people end up. This is the <a href=\"https://indieweb.org/\">IndieWeb</a>. Let me know if you\u2019d be interested in a talk about how to get set up.</p>",
"text": "Everybody on Twitter wants to know where to go now. The answer is your own website, syndicating out to wherever else people end up. This is the IndieWeb. Let me know if you\u2019d be interested in a talk about how to get set up."
},
"published": "2022-04-25T17:02:46+00:00",
"post-type": "note",
"_id": "33380003",
"_source": "7224",
"_is_read": true
}
As I continue reading and sometimes re-posting things written on this day, I've decided to do one more thing at the end of a session: go to a random site in the IndieWeb WebRing. Today, I found something that resonates down the years: how to organise the content of a weblog.
{
"type": "entry",
"author": {
"name": "Jeremy Cherfas",
"url": "https://jeremycherfas.net/",
"photo": "https://www.gravatar.com/avatar/0649cdd53ddf1146308f316b3406f97f?s=96&d=https%3A%2F%2Fmicro.blog%2Fimages%2Fblank_avatar.png"
},
"url": "https://stream.jeremycherfas.net/2022/as-i-continue-reading-and-sometimes-re-posting",
"content": {
"html": "<p>As I continue reading and sometimes re-posting things written on this day, I've decided to do one more thing at the end of a session: go to a random site in the IndieWeb WebRing. Today, I found something that resonates down the years: how to organise the content of a weblog.</p>",
"text": "As I continue reading and sometimes re-posting things written on this day, I've decided to do one more thing at the end of a session: go to a random site in the IndieWeb WebRing. Today, I found something that resonates down the years: how to organise the content of a weblog."
},
"published": "2022-04-25T07:36:39+00:00",
"post-type": "note",
"_id": "33380004",
"_source": "7224",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-21T17:32:00+0100",
"url": "https://www.jvt.me/mf2/2022/04/leh7m/",
"category": [
"indieauth"
],
"bookmark-of": [
"https://david.shanske.com/2022/04/21/indieauth-spec-updates-2022/"
],
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "bookmark",
"refs": {
"https://david.shanske.com/2022/04/21/indieauth-spec-updates-2022/": {
"type": "entry",
"summary": "Over the course of 2021, the IndieWeb community had several popup sessions to continue the refining of the spec. This culminated in a release of the latest iteration on February 22, 2022. I really \u2026",
"url": "https://david.shanske.com/2022/04/21/indieauth-spec-updates-2022/",
"name": "IndieAuth Spec Updates 2022",
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": null
},
"post-type": "article"
}
},
"_id": "28609872",
"_source": "2169",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-21T11:47:38-04:00",
"syndication": [
"https://news.indieweb.org/en/david.shanske.com/2022/04/21/indieauth-spec-updates-2022/",
"https://twitter.com/dshanske/status/1517168901976727553",
"https://micro.blog/dshanske/12729173"
],
"name": "IndieAuth Spec Updates 2022 - April 21, 2022",
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://david.shanske.com/avatar/dshanske?s=96"
},
"post-type": "article",
"_id": "28608429",
"_source": "5",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-21T11:47:38-04:00",
"syndication": [
"https://news.indieweb.org/en/david.shanske.com/2022/04/21/indieauth-spec-updates-2022/",
"https://twitter.com/dshanske/status/1517168901976727553"
],
"name": "IndieAuth Spec Updates 2022 - April 21, 2022",
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://david.shanske.com/avatar/dshanske?s=96"
},
"post-type": "article",
"_id": "28608412",
"_source": "5",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-21T11:47:38-04:00",
"url": "https://david.shanske.com/2022/04/21/indieauth-spec-updates-2022/",
"name": "IndieAuth Spec Updates 2022 - April 21, 2022",
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://david.shanske.com/avatar/dshanske?s=96"
},
"post-type": "article",
"_id": "28608381",
"_source": "5",
"_is_read": true
}
I’m looking for tech podcast suggestions, more unique stuff… based on indieweb, alt operating systems, or other interesting and less common things???
{
"type": "entry",
"author": {
"name": "Tim Apple",
"url": "https://timapple.com",
"photo": "https://avatars.micro.blog/avatars/2022/96710.jpg"
},
"url": "https://timapple.com/2022/04/16/im-looking-for.html",
"content": {
"html": "<p>I\u2019m looking for tech podcast suggestions, more unique stuff\u2026 based on indieweb, alt operating systems, or other interesting and less common things???</p>",
"text": "I\u2019m looking for tech podcast suggestions, more unique stuff\u2026 based on indieweb, alt operating systems, or other interesting and less common things???"
},
"published": "2022-04-16T20:41:09+00:00",
"post-type": "note",
"_id": "33380005",
"_source": "7224",
"_is_read": true
}
Always nice to see more webmention support. Did you hook up brid.gy to get tweets too?
{
"type": "entry",
"published": "2022-04-16T14:58:51+0000",
"url": "http://known.kevinmarks.com/2022/always-nice-to-see-more-webmention-support",
"in-reply-to": [
"https://bofh.org.uk/2022/04/16/we-have-webmentions/"
],
"content": {
"text": "Always nice to see more webmention support. Did you hook up brid.gy to get tweets too?"
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "http://known.kevinmarks.com/file/9255656669173b7867ab839ee6556f9e"
},
"post-type": "reply",
"_id": "28512573",
"_source": "205",
"_is_read": true
}
elon can have twitter but he can never have my website
{
"type": "entry",
"published": "2022-04-14T10:51:43-07:00",
"url": "https://aaronparecki.com/2022/04/14/8/web",
"category": [
"indieweb"
],
"syndication": [
"https://twitter.com/aaronpk/status/1514662705616986124"
],
"content": {
"text": "elon can have twitter but he can never have my website"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aaronparecki.com/images/profile.jpg"
},
"post-type": "note",
"_id": "28477774",
"_source": "16",
"_is_read": true
}
Thanks to the mistrust of big tech, the creation of better tools for developers, and the weird and wonderful creativity of ordinary people, we’re seeing an incredibly unlikely comeback: the web is thriving again.
Smart analyis from Anil, though I’m not sure I’d agree with his emphasis on tools and frameworks—it’s the technology built into browsers that has really come along in leaps and bounds, allowing people to do more with less code.
But then there’s this:
So if we have the tech, then why hasn’t it happened already? The biggest thing that may be missing is just awareness of the modern web’s potential. Unlike the Facebooks and Googles of the world, the open, creative web doesn’t have a billion-dollar budget for promoting itself. Years of control from the tech titans has resulted in the conventional wisdom that somehow the web isn’t “enough”, that you have to tie yourself to proprietary platforms if you want to build a big brand or a big business.
True! Anil also points to an act of rebellion and resistance:
Get your own site going, though, and you’ll have a sustainable way of being in control of your own destiny online.
{
"type": "entry",
"published": "2022-04-14T07:38:52Z",
"url": "https://adactio.com/links/18980",
"category": [
"indieweb",
"personal",
"publishing",
"technology",
"websites",
"frontend",
"development",
"open",
"platforms",
"silos"
],
"bookmark-of": [
"https://anildash.com/2022/04/13/a-web-renaissance/"
],
"content": {
"text": "A Web Renaissance\n\n\n\n\n Thanks to the mistrust of big tech, the creation of better tools for developers, and the weird and wonderful creativity of ordinary people, we\u2019re seeing an incredibly unlikely comeback: the web is thriving again.\n\n\nSmart analyis from Anil, though I\u2019m not sure I\u2019d agree with his emphasis on tools and frameworks\u2014it\u2019s the technology built into browsers that has really come along in leaps and bounds, allowing people to do more with less code.\n\nBut then there\u2019s this:\n\n\n So if we have the tech, then why hasn\u2019t it happened already? The biggest thing that may be missing is just awareness of the modern web\u2019s potential. Unlike the Facebooks and Googles of the world, the open, creative web doesn\u2019t have a billion-dollar budget for promoting itself. Years of control from the tech titans has resulted in the conventional wisdom that somehow the web isn\u2019t \u201cenough\u201d, that you have to tie yourself to proprietary platforms if you want to build a big brand or a big business.\n\n\nTrue! Anil also points to an act of rebellion and resistance:\n\n\n Get your own site going, though, and you\u2019ll have a sustainable way of being in control of your own destiny online.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://anildash.com/2022/04/13/a-web-renaissance/\">\nA Web Renaissance\n</a>\n</h3>\n\n<blockquote>\n <p>Thanks to the mistrust of big tech, the creation of better tools for developers, and the weird and wonderful creativity of ordinary people, we\u2019re seeing an incredibly unlikely comeback: the web is thriving again.</p>\n</blockquote>\n\n<p>Smart analyis from Anil, though I\u2019m not sure I\u2019d agree with his emphasis on tools and frameworks\u2014it\u2019s the technology built into browsers that has really come along in leaps and bounds, allowing people to do more with less code.</p>\n\n<p>But then there\u2019s this:</p>\n\n<blockquote>\n <p>So if we have the tech, then why hasn\u2019t it happened already? The biggest thing that may be missing is just awareness of the modern web\u2019s potential. Unlike the Facebooks and Googles of the world, the open, creative web doesn\u2019t have a billion-dollar budget for promoting itself. Years of control from the tech titans has resulted in the conventional wisdom that somehow the web isn\u2019t \u201cenough\u201d, that you have to tie yourself to proprietary platforms if you want to build a big brand or a big business.</p>\n</blockquote>\n\n<p>True! Anil also points to an act of rebellion and resistance:</p>\n\n<blockquote>\n <p>Get your own site going, though, and you\u2019ll have a sustainable way of being in control of your own destiny online.</p>\n</blockquote>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "28467559",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-11T10:27:53.536349342Z",
"url": "https://www.jvt.me/mf2/2022/04/xhw2i/",
"category": [
"indieweb",
"personal-website",
"blogging"
],
"bookmark-of": [
"https://indieblog.page/"
],
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "bookmark",
"refs": {
"https://indieblog.page/": {
"type": "entry",
"url": "https://indieblog.page/",
"name": "Random Indie Weblog Posts",
"post-type": "article"
}
},
"_id": "28403547",
"_source": "2169",
"_is_read": true
}
How to set up OAuth2/OpenID Connect authentication with an Architect Framework application.
{
"type": "entry",
"published": "2022-04-11T11:10:29+01:00",
"summary": "How to set up OAuth2/OpenID Connect authentication with an Architect Framework application.",
"url": "https://www.jvt.me/posts/2022/04/11/architect-oidc-login/",
"featured": "https://media.jvt.me/4bea95efe8.png",
"category": [
"blogumentation",
"architect-framework",
"nodejs",
"aws-lambda",
"oidc",
"indieauth",
"oauth2"
],
"photo": [
"https://media.jvt.me/4bea95efe8.png"
],
"name": "Protecting an Architect Framework Application with OAuth2 or OpenID Connect Authentication",
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "photo",
"_id": "28403338",
"_source": "2169",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-10T23:58:49+02:00",
"url": "https://notiz.blog/2022/04/10/metaformats/",
"name": "metaformats",
"content": {
"text": "Vor ein paar Tagen bin ich \u00fcber einen Post von Tantek \u00c7elik gestolpert, in dem er metaformats vorstellt.\n\n\n\n\nIntroducing #metaformats (https://microformats.org/wiki/metaformats), an extension to #microformats2 for parsing invisible data published in HTML meta tags, for backward compatibility with existing vocabularies consumed by multiple testable interoperable implementations.\nhttps://tantek.com/2022/091/t1/metaformats\n\n\n\n\nDer Vorschlag ist vom 01. April und war wohl urspr\u00fcnglich als als April-Scherz gedacht.\n\n\n\n\nmetaformats started as an April Fools joke concept to describe how to both publish using microformats class names and openly parse meta tags as a fallback for what should be in-the-body visible data, including backcompat with OGP, Twitter Cards, and meta author, description, and anything else real sites (like search engines) appear to consume.\nhttps://indieweb.org/metaformats\n\n\n\n\nEine Art Fallback-Spezifikation f\u00fcr Microformats-Parser finde ich in der Tat etwas sperrig, aber ich mag die Idee eines Fallbacks an sich.\n\n\n\nMicroformats sind ein Building-Block des IndieWebs und werden unter anderem auch von Webmentions genutzt. Microformats sind ein Markup-Format zur semantischen Auszeichnung von HTML. In der Version 2, werden Microformats aber fast ausschlie\u00dflich von der IndieWeb Community benutzt und sind dar\u00fcber hinaus wenig bekannt.\n\n\n\nAber gerade f\u00fcr WordPress ist es extrem schwer, bestehende Themes nachtr\u00e4glich mit Microformats zu \u201everedeln\u201c. Wir haben es mit diversen Plugins versucht, mit nur m\u00e4\u00dfigem Erfolg. Andere Formate wie das Open Graph Protocol oder Schema.org (JSON-LD) sind da wesentlich einfacher zu integrieren, da sie nicht bestehendes HTML erweitern und durch den Support der gro\u00dfen Suchmaschinen und sozialen Netzwerke, auch viel attraktiver sind.\n\n\n\nIch bin kein gro\u00dfer Fan von embedded JSON-LD, aber wenn es nicht anders funktioniert und seine Reichweite hat, warum sollte man es dann ignorieren?\n\n\n\nDas IndieWeb hat eigentlich eine gro\u00dfartige Philosophie um mit solchen \u201eProblemen\u201c umzugehen.\n\n\n\n\nbridge all the things is a nascent IndieWeb philosophy that prioritizes interoperability over ideology, NIH, historical disagreements, etc. ecosystems are valuable and powerful, and one easy way to extend an ecosystem is to bridge it with other existing ecosystems.\nhttps://indieweb.org/bridge_all_the_things\n\n\n\n\nF\u00fcr das Webmention Plugin haben David und ich schon vor Monaten einen ganz \u00e4hnlichen Ansatz gew\u00e4hlt. Neben Microformats unterst\u00fctzen wir auch OGP, Twitter-Cards, Schema.org, Meta-Header und die WordPress API, um eventuell fehlende Microformats v2 zu kompensieren.\n\n\n\nSelbst wenn \u201emetaformats\u201c nur als April Schwerz gedacht waren, hat die Idee potential um speziell Webmentions voran zu treiben.\n\n\n\nBridge all the things!",
"html": "<p>Vor ein paar Tagen bin ich \u00fcber <a href=\"https://tantek.com/2022/091/t1/metaformats\">einen Post von Tantek \u00c7elik</a> gestolpert, in dem er <strong>metaformats</strong> vorstellt.</p>\n\n\n\n<blockquote>\n<p>Introducing #metaformats (<a href=\"https://microformats.org/wiki/metaformats\">https://microformats.org/wiki/metaformats</a>), an extension to #microformats2 for parsing invisible data published in HTML meta tags, for backward compatibility with existing vocabularies consumed by multiple testable interoperable implementations.</p>\n<a href=\"https://tantek.com/2022/091/t1/metaformats\">https://tantek.com/2022/091/t1/metaformats</a>\n</blockquote>\n\n\n\n<p>Der Vorschlag ist vom 01. April und war wohl urspr\u00fcnglich als als April-Scherz gedacht.</p>\n\n\n\n<blockquote>\n<p><strong><a href=\"https://microformats.org/wiki/metaformats\">metaformats</a></strong> started as an April Fools joke concept to describe how to both publish using microformats class names and openly parse meta tags as a fallback for what should be in-the-body visible data, including backcompat with <a href=\"https://indieweb.org/OGP\">OGP</a>, <a href=\"https://indieweb.org/Twitter_Cards\">Twitter Cards</a>, and meta author, description, and anything else real sites (like search engines) appear to consume.</p>\n<a href=\"https://indieweb.org/metaformats\">https://indieweb.org/metaformats</a>\n</blockquote>\n\n\n\n<p>Eine Art Fallback-Spezifikation f\u00fcr <a href=\"https://microformats.io/#parsers\">Microformats-Parser</a> finde ich in der Tat etwas sperrig, aber ich mag die Idee eines Fallbacks an sich.</p>\n\n\n\n<p><a href=\"https://notiz.blog/2006/11/20/microformats/\">Microformats</a> sind ein <a href=\"https://indieweb.org/Category:building-blocks\">Building-Block</a> des IndieWebs und werden unter anderem auch von Webmentions genutzt. Microformats sind ein Markup-Format zur semantischen Auszeichnung von HTML. In der <a href=\"https://notiz.blog/2012/07/03/microformats-the-next-generation/\">Version 2</a>, werden Microformats aber fast ausschlie\u00dflich von der IndieWeb Community benutzt und sind dar\u00fcber hinaus wenig bekannt.</p>\n\n\n\n<p>Aber gerade f\u00fcr WordPress ist es extrem schwer, bestehende Themes nachtr\u00e4glich mit Microformats zu \u201everedeln\u201c. Wir haben es mit <a href=\"https://wordpress.org/plugins/wp-uf2/\">diversen</a> <a href=\"https://wordpress.org/plugins/mf2-feed/\">Plugins</a> versucht, mit nur m\u00e4\u00dfigem Erfolg. Andere Formate wie das <a href=\"https://ogp.me/\">Open Graph Protocol</a> oder <a href=\"https://developers.google.com/search/docs/advanced/structured-data/intro-structured-data?hl=de\">Schema.org (JSON-LD)</a> sind da wesentlich einfacher zu integrieren, da sie nicht bestehendes HTML erweitern und durch den Support der gro\u00dfen Suchmaschinen und sozialen Netzwerke, auch viel attraktiver sind.</p>\n\n\n\n<p>Ich bin <a href=\"https://notiz.blog/2013/08/07/embedded-json-ld/\">kein gro\u00dfer Fan von embedded JSON-LD</a>, aber wenn es nicht anders funktioniert und seine Reichweite hat, warum sollte man es dann ignorieren?</p>\n\n\n\n<img width=\"593\" height=\"421\" src=\"https://notiz.blog/wp-content/uploads/2022/04/bridge-all-the-things.jpg\" alt=\"\" />\n\n\n\n<p>Das IndieWeb hat eigentlich eine gro\u00dfartige Philosophie um mit solchen \u201eProblemen\u201c umzugehen.</p>\n\n\n\n<blockquote>\n<p><strong>bridge all the things</strong> is a nascent IndieWeb philosophy that prioritizes interoperability over ideology, NIH, historical disagreements, etc. ecosystems are valuable and powerful, and one easy way to extend an ecosystem is to bridge it with other existing ecosystems.</p>\n<a href=\"https://indieweb.org/bridge_all_the_things\">https://indieweb.org/bridge_all_the_things</a>\n</blockquote>\n\n\n\n<p>F\u00fcr das <a href=\"https://wordpress.org/plugins/webmention/\">Webmention Plugin</a> haben <a href=\"https://david.shanske.com/\">David</a> und ich schon vor Monaten einen ganz \u00e4hnlichen Ansatz gew\u00e4hlt. Neben Microformats unterst\u00fctzen wir auch <a href=\"https://notiz.blog/tag/open-graph-protocol/\">OGP</a>, <a href=\"https://notiz.blog/2012/06/22/twitter-cards/\">Twitter-Cards</a>, <a href=\"https://notiz.blog/2012/09/21/schema-org-what-ive-learned-so-far/\">Schema.org</a>, <a href=\"https://de.wikipedia.org/wiki/Meta-Element\">Meta-Header</a> und die WordPress API, um eventuell fehlende Microformats v2 zu kompensieren.</p>\n\n\n\n<p>Selbst wenn \u201emetaformats\u201c nur als April Schwerz gedacht waren, hat die Idee potential um speziell Webmentions voran zu treiben.</p>\n\n\n\n<p><strong>Bridge all the things!</strong></p>"
},
"author": {
"type": "card",
"name": "Matthias Pfefferle",
"url": "https://notiz.blog/author/matthias-pfefferle/",
"photo": "https://secure.gravatar.com/avatar/75512bb584bbceae57dfc503692b16b2?s=40&d=mm&r=g"
},
"post-type": "note",
"_id": "28396377",
"_source": "206",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-09T20:20:38+00:00",
"url": "https://werd.io/2022/known-and-idno",
"name": "Known and Idno",
"content": {
"text": "Rewriting software from scratch is usually a terrible idea. But I\u2019m thinking about it.The Known open source codebase is now 9 years old; a PHP kludge that I wrote while my mother was recovering from a double lung transplant still powers my site and many others. It became the foundation of my second startup, and is still an open source project today. But there were a number of years when I didn\u2019t pay attention to the codebase, and there\u2019s a lot to unpick.Meanwhile, the hosting landscape has completely changed. It used to be that you\u2019d buy some space with a shared host and upload files via (S)FTP; these days virtual hosts are commonplace and getting easier to use. There are one-click installation buttons for Heroku and other hosts.I\u2019d like to clean PHP Known up, and I\u2019m trying my best in between all the other things that are going on in my life. Probably that should mostly be about getting to another stable release: a lot of the architecture has been changed (by other developers) and a lot of users are having trouble installing it. So bringing that back to accessibility would be nice.I also want to fix import / export, so that people can take their Known content and use it elsewhere. A lot of folks, rightly, would like to migrate to WordPress or Ghost in particular. They should be able to do that with ease.But I also like the idea of going back to basics with Idno, the underlying platform, and thinking about it again. The original core idea was that you could create a stream of arbitrary content, set fine-grained permissions on it, and both post to it and consume from it in a bunch of different ways. If you wanted to post via the web, great; via a webhook, API endpoint or common standard like Micropub, also great. Likewise, reading via the web, JSON, RSS, MRSS, ActivityStreams, and so on would all be easily possible. Permissions would limit both reading and writing to a customizable set of people, from everyone on the internet down to one person.That\u2019s not really where Known ended up going, but I still find that potentially interesting as a project. Instead of PHP, I\u2019d be more inclined to write it as a Node service these days (or use it to learn something I\u2019m less familiar with, like Go).I wish I had more time to work on these sorts of projects. But it\u2019s something I\u2019d love to figure out how to fit in: I want to clean Known up, and return to Idno as a way to write scalable streams of arbitrary content. In the meantime, it\u2019s fun to think about.",
"html": "<p>Rewriting software from scratch is usually a terrible idea. But I\u2019m thinking about it.</p><p>The <a href=\"https://github.com/idno/known\">Known open source codebase</a> is now 9 years old; a PHP kludge that I wrote while my mother was recovering from a double lung transplant still powers my site and many others. It became the foundation of my second startup, and is still an open source project today. But there were a number of years when I didn\u2019t pay attention to the codebase, and there\u2019s a lot to unpick.</p><p>Meanwhile, the hosting landscape has completely changed. It used to be that you\u2019d buy some space with a shared host and upload files via (S)FTP; these days virtual hosts are commonplace and getting easier to use. There are one-click installation buttons for Heroku and other hosts.</p><p>I\u2019d like to clean PHP Known up, and I\u2019m trying my best in between all the other things that are going on in my life. Probably that should mostly be about getting to another stable release: a lot of the architecture has been changed (by other developers) and a lot of users are having trouble installing it. So bringing that back to accessibility would be nice.</p><p>I also want to fix import / export, so that people can take their Known content and use it elsewhere. A lot of folks, rightly, would like to migrate to WordPress or Ghost in particular. They should be able to do that with ease.</p><p>But I also like the idea of going back to basics with Idno, the underlying platform, and thinking about it again. The original core idea was that you could create a stream of arbitrary content, set fine-grained permissions on it, and both post to it and consume from it in a bunch of different ways. If you wanted to post via the web, great; via a webhook, API endpoint or common standard like Micropub, also great. Likewise, reading via the web, JSON, RSS, MRSS, ActivityStreams, and so on would all be easily possible. Permissions would limit both reading and writing to a customizable set of people, from everyone on the internet down to one person.</p><p>That\u2019s not really where Known ended up going, but I still find that potentially interesting as a project. Instead of PHP, I\u2019d be more inclined to write it as a Node service these days (or use it to learn something I\u2019m less familiar with, like Go).</p><p>I wish I had more time to work on these sorts of projects. But it\u2019s something I\u2019d love to figure out how to fit in: I want to clean Known up, and return to Idno as a way to write scalable streams of arbitrary content. In the meantime, it\u2019s fun to think about.</p>"
},
"author": {
"type": "card",
"name": "Ben Werdm\u00fcller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://werd.io/file/5d388c5fb16ea14aac640912/thumb.jpg"
},
"post-type": "article",
"_id": "28377942",
"_source": "191",
"_is_read": true
}
I can’t remember the last time that a website made me smile like this.
{
"type": "entry",
"published": "2022-04-07T08:26:45Z",
"url": "https://adactio.com/links/18963",
"category": [
"websites",
"childhood",
"personal",
"publishing",
"indieweb",
"growing",
"learning",
"sharing",
"geocities",
"homepages",
"html",
"design",
"frontend",
"development"
],
"bookmark-of": [
"https://sailorhg.com/home_sweet_homepage/"
],
"content": {
"text": "home sweet homepage\n\n\n\nI can\u2019t remember the last time that a website made me smile like this.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://sailorhg.com/home_sweet_homepage/\">\nhome sweet homepage\n</a>\n</h3>\n\n<p>I can\u2019t remember the last time that a website made me smile like this.</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "28325075",
"_source": "2",
"_is_read": true
}
On this 4/04 day, pour one out for sites & permalinks lost this past year like:
* Google App Maker (site not found)
* Yahoo Groups (posts & permalinks gone, subdomain redirects)
More 404 Not Found: https://indieweb.org/site-deaths#2021
#404NotFound, day of the #deadweb
{
"type": "entry",
"published": "2022-04-04 23:54-0700",
"url": "http://tantek.com/2022/094/t1/404-not-found",
"category": [
"404NotFound",
"deadweb"
],
"content": {
"text": "On this 4/04 day, pour one out for sites & permalinks lost this past year like:\n* Google App Maker (site not found)\n* Yahoo Groups (posts & permalinks gone, subdomain redirects)\n\nMore 404 Not Found: https://indieweb.org/site-deaths#2021\n#404NotFound, day of the #deadweb",
"html": "On this 4/04 day, pour one out for sites & permalinks lost this past year like:<br />* Google App Maker (site not found)<br />* Yahoo Groups (posts & permalinks gone, subdomain redirects)<br /><br />More 404 Not Found: <a href=\"https://indieweb.org/site-deaths#2021\">https://indieweb.org/site-deaths#2021</a><br />#<span class=\"p-category\">404NotFound</span>, day of the #<span class=\"p-category\">deadweb</span>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "http://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "28281054",
"_source": "1",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-03T22:14:09+02:00",
"url": "https://notiz.blog/2022/04/03/cloudfest-2022-hackathon-indieweb-for-wordpress/",
"featured": "https://notiz.blog/wp-content/uploads/2022/03/CFH202229-900x675.jpeg",
"name": "CloudFest Hackathon: WordPress and the IndieWeb",
"content": {
"text": "Vom 19. bis 21. M\u00e4rz fand der CloudFest Hackathon in Rust statt und ich hatte die Chance ein Projekt einzureichen und zu leiten:\n\n\n\n\nWordPress and the IndieWeb\nThe IndieWeb is a community of individual personal websites, connected by simple standards, based on the principles of owning your domain, using it as your primary identity, to publish on your own site (optionally syndicate elsewhere), and own your data.\nThere are a variety of WordPress-plugins implementing these standards and principles, to help people to stay independent. Most of these plugins are very basic, have no or only little documentation with a poor user experience. Help the movement to mature and gain a broader audience.\n\n\n\n\nIch hatte mir im Vorfeld nicht viel Gedanken zum Hackathon gemacht, hab aber insgeheim gehofft, der Version 5.0 vom Webmention Plugin (einer nahezu kompletten \u00dcberarbeitung an der David Shanske und ich schon eine halbe Ewigkeit arbeiten) ein wesentliches St\u00fcck n\u00e4her zu kommen\u2026 Das Wochenende lief dann aber doch etwas anders\u2026 auch gro\u00dfartig, aber anders \ud83d\ude42\n\n\n\n1. Tag\n\n\n\nWir waren eine wild zusammengew\u00fcrfelte Truppe von 8 Leuten mit den verschiedensten Lebensl\u00e4ufen und ich hab mir den ersten Tag viel M\u00fche gegeben, das IndieWeb und Webmentions zu erkl\u00e4ren. Die Diskussionen waren spannend und hitzig und gingen sogar so weit, dass ich zwischendurch den generellen Sinn und Zweck des Webmention Plugins verteidigen musste.\n\n\n\nLetztendlich haben aber nicht meine Argumente die Gruppe \u00fcberzeugt, sondern eine Pr\u00e4sentation des Plugins mit all seinen aktuellen Features. Wer diesen Erkenntnisprozess nachvollziehen m\u00f6chte, kann gerne Hagen Grafs \u201eWebmention Journey\u201c auf Twitter verfolgen \ud83d\ude42\n\n\n\nMeine Fazit des ersten Tages?\n\n\n\nMan muss nicht die Geschichte des IndieWebs verstehen und auch nicht den Webmention Standard gelesen haben um von der Funktionalit\u00e4t begeistert zu werden, vor allem in der Kombination mit Brid.gy (Brid.gy schl\u00e4gt eine Br\u00fccke zwischen dem Webmention Standard und den propriet\u00e4ren APIs der bekannten Social Networks. So landen dann auch Likes auf Facebook und Kommentare auf Twitter, im eigenen Blog).\n\n\n\nIch werde Versuchen mich zuk\u00fcnftig weniger auf Geschichte und Technologie zu konzentrieren und auf Vortr\u00e4gen und Hackathons mehr Fokus auf die Funktionalit\u00e4t zu legen.\n\n\n\nIch hab die Plugins in erster Linie erstmal f\u00fcr mich Gebaut. Frei nach dem Motto \u201eeat your own dogfood\u201e. Das hat f\u00fcr die IndieWeb Community ganz gut funktioniert, aber um eine breitere Masse anzusprechen, muss das Plugin verst\u00e4ndlicher werden.\n\n\n\nF\u00fcr den Hackathon haben wir uns deshalb dazu entschieden, die Usability und die User Experience des Plugin zu beleuchten und (im besten Fall) zu verbessern.\n\n\n\nWebmention-Settings\n\n\n\nDie Einstellungen setzen relativ viel Kenntnisse \u00fcber die Funktionsweise von Webmentions voraus. Ein Teil der Gruppe hat sich daran gemacht, die Seite zu \u00fcberarbeiten und zu vereinfachen.\n\n\n\nDas Resultat ist eine Art Wizard, der beim ersten Aufruf gestartet wird und den User Schritt f\u00fcr Schritt durch die Einstellungen f\u00fchrt und sie ausf\u00fchrlich erkl\u00e4rt. Der Wizard soll nur beim ersten Laden starten und die klassischen Einstellungen nicht ersetzen.\n\n\n\n(Der Pull Request dazu: #328)\n\n\n\nDie zweite Idee war Brid.gy tiefer in das Webmentions Plugin zu integrieren. Die aktuelle Diskussion dazu findet auf GitHub statt.\n\n\n\nResponse-Types\n\n\n\nIm Gegensatz zu Trackbacks und Pingbacks, m\u00fcssen Webementions nicht immer \u201enur\u201c ein simpler ping sein. Es ist auch m\u00f6glich dezentrale Likes, Bookmarks, RSVPs oder Reposts zu verschicken.\n\n\n\nAktuell muss man dazu im Block-Editor auf die HTML Ansicht wechseln und dem Link eine CSS-Klasse hinzuf\u00fcgen:\n\n\n<a class=\"u-like-of\" href=\"http://example.com/\">Example</a>Code-Sprache: HTML, XML (xml)\n\n\nDas ist nicht praktikabel und in keiner Weise anwenderfreundlich. Aus diesem Grund hat eine zweite Gruppe, an einem User Interface f\u00fcr den Response-Type gearbeitet.\n\n\n\nResponse-Types f\u00fcr Links im Block EditorAm Ende des Hackathons gab es auch einen ersten Draft, mit der man Links als Likes auszeichnen konnte. Den PR gibt es leider noch nicht, aber ich werde ihn nachreichen wenn es soweit ist.\n\n\n\nWebmaininnat suomeksi\n\n\n\n\u2026ja Carolinan ansiosta Webmaininnat-laajennus on nyt saatavilla my\u00f6s suomeksi! Kiitos paljon \ud83d\ude42\n\n\n\nFazit\n\n\n\nEs war extrem spannend mit Leuten, au\u00dferhalb der IndieWeb und (teilweise) auch au\u00dferhalb der WordPress-Community, \u00fcber das IndieWeb im Allgemeinen und das Webmention Plugin im Speziellen zu sprechen.\n\n\n\nVielen Dank an Moritz Bappert, Stefan Euchenhofer, Marko Feldmann, Hagen Graf, Carolina Lindqvist, Jason Rouet und Jan Vogt f\u00fcr eure tolle Arbeit! Danke f\u00fcr die neue Perspektive und f\u00fcr euer Feedback!\n\n\n\nDanke auch an Robert Windisch und Alain Schlesser, mit denen ich viel \u00fcber das Potential von Webmentions im WordPress Core geredet habe.\n\n\n\nDie 5.0er Version des Webmention Plugins wird gro\u00dfartig!",
"html": "<p>Vom 19. bis 21. M\u00e4rz fand der <a href=\"https://www.cloudfest.com/hackathon\">CloudFest Hackathon</a> in Rust statt und ich hatte die Chance ein <a href=\"https://www.cloudfest.com/project/wordpress-and-the-indieweb\">Projekt</a> einzureichen und zu leiten:</p>\n\n\n\n<blockquote>\n<p><strong>WordPress and the IndieWeb</strong></p>\n<p>The IndieWeb is a community of individual personal websites, connected by simple standards, based on the principles of owning your domain, using it as your primary identity, to publish on your own site (optionally syndicate elsewhere), and own your data.</p>\n<p>There are a variety of WordPress-plugins implementing these standards and principles, to help people to stay independent. Most of these plugins are very basic, have no or only little documentation with a poor user experience. Help the movement to mature and gain a broader audience.</p>\n</blockquote>\n\n\n\n<p>Ich hatte mir im Vorfeld nicht viel Gedanken zum Hackathon gemacht, hab aber insgeheim gehofft, der <a href=\"https://github.com/pfefferle/wordpress-webmention/tree/5.X\">Version 5.0</a> vom <a href=\"https://wordpress.org/plugins/webmention/\">Webmention Plugin</a> (einer nahezu kompletten \u00dcberarbeitung an der <a href=\"https://david.shanske.com/\">David Shanske</a> und ich schon eine halbe Ewigkeit arbeiten) ein wesentliches St\u00fcck n\u00e4her zu kommen\u2026 Das Wochenende lief dann aber doch etwas anders\u2026 auch gro\u00dfartig, aber anders \ud83d\ude42</p>\n\n\n\n<h2>1. Tag</h2>\n\n\n\n<p>Wir waren eine wild zusammengew\u00fcrfelte Truppe von 8 Leuten mit den verschiedensten Lebensl\u00e4ufen und ich hab mir den ersten Tag viel M\u00fche gegeben, das <a href=\"https://indieweb.org/\">IndieWeb</a> und <a href=\"https://webmention.net/\">Webmentions</a> zu erkl\u00e4ren. Die Diskussionen waren spannend und hitzig und gingen sogar so weit, dass ich zwischendurch den generellen Sinn und Zweck des Webmention Plugins verteidigen musste.</p>\n\n\n\n<img width=\"900\" height=\"506\" src=\"https://notiz.blog/wp-content/uploads/2022/04/signal-2022-03-22-212819_017-900x506.jpeg\" alt=\"Hackathon Gruppe\" /><p>Letztendlich haben aber nicht meine Argumente die Gruppe \u00fcberzeugt, sondern eine Pr\u00e4sentation des Plugins mit all seinen aktuellen Features. Wer diesen Erkenntnisprozess nachvollziehen m\u00f6chte, kann gerne <a href=\"https://hagen.cocoate.com/\">Hagen Graf</a>s \u201e<a href=\"https://twitter.com/search?q=%40hagengraf%20%23CFHack2022&src=typed_query&f=live\">Webmention Journey</a>\u201c auf Twitter verfolgen \ud83d\ude42</p>\n\n\n\n<p>Meine Fazit des ersten Tages?</p>\n\n\n\n<p>Man muss nicht die Geschichte des IndieWebs verstehen und auch nicht den <a href=\"https://www.w3.org/TR/webmention/\">Webmention Standard</a> gelesen haben um von der Funktionalit\u00e4t begeistert zu werden, vor allem in der Kombination mit <a href=\"https://brid.gy/\">Brid.gy</a> (Brid.gy schl\u00e4gt eine Br\u00fccke zwischen dem Webmention Standard und den propriet\u00e4ren APIs der bekannten Social Networks. So landen dann auch Likes auf Facebook und Kommentare auf Twitter, im eigenen Blog).</p>\n\n\n\n<p>Ich werde Versuchen mich zuk\u00fcnftig weniger auf Geschichte und Technologie zu konzentrieren und auf Vortr\u00e4gen und Hackathons mehr Fokus auf die Funktionalit\u00e4t zu legen.</p>\n\n\n\n<p>Ich hab die Plugins in erster Linie erstmal f\u00fcr mich Gebaut. Frei nach dem Motto \u201e<a href=\"https://indieweb.org/dogfood\">eat your own dogfood</a>\u201e. Das hat f\u00fcr die IndieWeb Community ganz gut funktioniert, aber um eine breitere Masse anzusprechen, muss das Plugin verst\u00e4ndlicher werden.</p>\n\n\n\n<p>F\u00fcr den Hackathon haben wir uns deshalb dazu entschieden, die <em>Usability</em> und die <em>User Experience</em> des Plugin zu beleuchten und (im besten Fall) zu verbessern.</p>\n\n\n\n<h3>Webmention-Settings</h3>\n\n\n\n<p>Die Einstellungen setzen relativ viel Kenntnisse \u00fcber die Funktionsweise von Webmentions voraus. Ein Teil der Gruppe hat sich daran gemacht, die Seite zu \u00fcberarbeiten und zu vereinfachen.</p>\n\n\n\n<a href=\"https://notiz.blog/?attachment_id=21835\"><img width=\"1200\" height=\"1200\" src=\"https://notiz.blog/wp-content/uploads/2022/03/signal-2022-03-22-212819_011.jpeg\" alt=\"\" /></a><a href=\"https://notiz.blog/?attachment_id=21833\"><img width=\"1024\" height=\"767\" src=\"https://notiz.blog/wp-content/uploads/2022/03/signal-2022-03-22-212819_005.jpeg\" alt=\"\" /></a><p>Das Resultat ist eine Art <em>Wizard</em>, der beim ersten Aufruf gestartet wird und den User Schritt f\u00fcr Schritt durch die Einstellungen f\u00fchrt und sie ausf\u00fchrlich erkl\u00e4rt. Der Wizard soll nur beim ersten Laden starten und die klassischen Einstellungen nicht ersetzen.</p>\n\n\n\n<p>(Der Pull Request dazu: <a href=\"https://github.com/pfefferle/wordpress-webmention/pull/328\">#328</a>)</p>\n\n\n\n<p>Die zweite Idee war Brid.gy tiefer in das Webmentions Plugin zu integrieren. Die aktuelle Diskussion dazu findet auf <a href=\"https://github.com/pfefferle/wordpress-webmention/issues/329\">GitHub</a> statt.</p>\n\n\n\n<h2>Response-Types</h2>\n\n\n\n<p>Im Gegensatz zu Trackbacks und Pingbacks, m\u00fcssen Webementions nicht immer \u201enur\u201c ein simpler <em>ping</em> sein. Es ist auch m\u00f6glich dezentrale <em>Likes</em>, <em>Bookmarks</em>, <em>RSVPs</em> oder <em>Reposts</em> zu verschicken.</p>\n\n\n\n<p>Aktuell muss man dazu im Block-Editor auf die HTML Ansicht wechseln und dem Link eine CSS-Klasse hinzuf\u00fcgen:</p>\n\n\n<pre><code><span><<span>a</span> <span>class</span>=<span>\"u-like-of\"</span> <span>href</span>=<span>\"http://example.com/\"</span>></span>Example<span></<span>a</span>></span></code><span>Code-Sprache:</span> <span>HTML, XML</span> <span>(</span><span>xml</span><span>)</span></pre>\n\n\n<p>Das ist nicht praktikabel und in keiner Weise anwenderfreundlich. Aus diesem Grund hat eine zweite Gruppe, an einem <em>User Interface</em> f\u00fcr den <em>Response-Type</em> gearbeitet.</p>\n\n\n\n<img width=\"900\" height=\"675\" src=\"https://notiz.blog/wp-content/uploads/2022/03/signal-2022-03-22-212819_004-900x675.jpeg\" alt=\"\" />Response-Types f\u00fcr Links im Block Editor<p>Am Ende des Hackathons gab es auch einen ersten Draft, mit der man Links als <em>Likes</em> auszeichnen konnte. Den PR gibt es leider noch nicht, aber ich werde ihn nachreichen wenn es soweit ist.</p>\n\n\n\n<h2>Webmaininnat suomeksi</h2>\n\n\n\n<p>\u2026ja Carolinan ansiosta Webmaininnat-laajennus on nyt saatavilla my\u00f6s suomeksi! Kiitos paljon \ud83d\ude42</p>\n\n\n\n<h2>Fazit</h2>\n\n\n\n<p>Es war extrem spannend mit Leuten, au\u00dferhalb der IndieWeb und (teilweise) auch au\u00dferhalb der WordPress-Community, \u00fcber das <a href=\"https://indieweb.org/\">IndieWeb</a> im Allgemeinen und das <a href=\"https://wordpress.org/plugins/webmention/\">Webmention Plugin</a> im Speziellen zu sprechen.</p>\n\n\n\n<p>Vielen Dank an <a href=\"https://github.com/moritzbappert\">Moritz Bappert</a>, <a href=\"https://github.com/euchenhofer\">Stefan Euchenhofer</a>, <a href=\"https://github.com/derHerrFeldmann\">Marko Feldmann</a>, <a href=\"https://hagen.cocoate.com/\">Hagen Graf</a>, <a href=\"https://www.linkedin.com/in/carolili/\">Carolina Lindqvist</a>, <a href=\"https://www.jasonna.de/\">Jason Rouet</a> und <a href=\"https://www.linkedin.com/in/janvogt/\">Jan Vogt</a> f\u00fcr eure tolle Arbeit! Danke f\u00fcr die neue Perspektive und f\u00fcr euer Feedback!</p>\n\n\n\n<p>Danke auch an <a href=\"https://profiles.wordpress.org/nullbyte/\">Robert Windisch</a> und <a href=\"https://www.alainschlesser.com/\">Alain Schlesser</a>, mit denen ich viel \u00fcber das <a href=\"https://core.trac.wordpress.org/ticket/35435\">Potential von Webmentions im WordPress Core</a> geredet habe.</p>\n\n\n\n<p>Die 5.0er Version des Webmention Plugins wird gro\u00dfartig!</p>"
},
"author": {
"type": "card",
"name": "Matthias Pfefferle",
"url": "https://notiz.blog/author/matthias-pfefferle/",
"photo": "https://secure.gravatar.com/avatar/75512bb584bbceae57dfc503692b16b2?s=40&d=mm&r=g"
},
"post-type": "article",
"_id": "28254063",
"_source": "206",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-02T15:42:38+00:00",
"url": "https://werd.io/2022/my-indieweb-real-estate-website-part-one",
"name": "My indieweb real estate website (part one)",
"content": {
"text": "One of the things a realtor will often do for you when you\u2019re selling a house is to set up a website for it. It\u2019s often built by the people who take the photos, and is created to a set template. It turns out there are a handful of services that exist to do just that: host a single-page site that showcases your home. We\u2019re selling our family home in Santa Rosa - the one my parents lived in for a decade - and I\u2019m a web developer. Don\u2019t get me wrong, these are nice sites, and we\u2019ll probably set one up. But I\u2019m also going to set up my own. Because of course I am. It sounds like fun, and I want to have fun with it, but wouldn\u2019t it be great if it brought in the buyer?I\u2019m giving myself a few restrictions:It\u2019ll be a hand-rolled static site. No frameworks for the HTML, JS, or CSS, and no pre-set templates: just me, a text editor, and some design tools. It\u2019s a home with shared ownership - everyone gets a say on the content and design - but I\u2019m going to build it.It needs to get an A for SEO, site performance, and security.And it needs to be up over the next two weeks. There\u2019s a lot going on, so this is a bit of a challenge.Wish me luck. And hey, if you\u2019re in the market for a three bedroom, two and a half bathroom single-family home in the heart of wine country \u2026",
"html": "<p>One of the things a realtor will often do for you when you\u2019re selling a house is to set up a website for it. It\u2019s often built by the people who take the photos, and is created to a set template. It turns out there <a href=\"https://theclose.com/single-property-websites/\">are a handful of services that exist to do just that</a>: host a single-page site that showcases your home. </p><p>We\u2019re selling our family home in Santa Rosa - the one my parents lived in for a decade - and I\u2019m a web developer. Don\u2019t get me wrong, <a href=\"https://www.zenmodernhome.com/\">these are nice sites</a>, and we\u2019ll probably set one up. But I\u2019m <em>also</em> going to set up my own. Because of <em>course</em> I am. It sounds like fun, and I want to have fun with it, but wouldn\u2019t it be great if it brought in the buyer?</p><p>I\u2019m giving myself a few restrictions:</p><p>It\u2019ll be a hand-rolled static site. No frameworks for the HTML, JS, or CSS, and no pre-set templates: just me, a text editor, and some design tools. It\u2019s a home with shared ownership - everyone gets a say on the content and design - but I\u2019m going to build it.</p><p>It needs to get an A for SEO, site performance, and security.</p><p>And it needs to be up over the next two weeks. There\u2019s a lot going on, so this is a bit of a challenge.</p><p>Wish me luck. And hey, if you\u2019re in the market for a three bedroom, two and a half bathroom single-family home in the heart of wine country \u2026</p>"
},
"author": {
"type": "card",
"name": "Ben Werdm\u00fcller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://werd.io/file/5d388c5fb16ea14aac640912/thumb.jpg"
},
"post-type": "article",
"_id": "28232857",
"_source": "191",
"_is_read": true
}
Introducing #metaformats (https://microformats.org/wiki/metaformats), an extension to #microformats2 for parsing invisible data published in HTML meta tags, for backward compatibility with existing vocabularies consumed by multiple testable interoperable implementations.
{
"type": "entry",
"published": "2022-04-01 23:59-0700",
"url": "http://tantek.com/2022/091/t1/metaformats",
"category": [
"metaformats",
"microformats2"
],
"content": {
"text": "Introducing #metaformats (https://microformats.org/wiki/metaformats), an extension to #microformats2 for parsing invisible data published in HTML meta tags, for backward compatibility with existing vocabularies consumed by multiple testable interoperable implementations.",
"html": "Introducing #<span class=\"p-category\">metaformats</span> (<a href=\"https://microformats.org/wiki/metaformats\">https://microformats.org/wiki/metaformats</a>), an extension to #<span class=\"p-category\">microformats2</span> for parsing invisible data published in HTML meta tags, for backward compatibility with existing vocabularies consumed by multiple testable interoperable implementations."
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "http://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "28228728",
"_source": "1",
"_is_read": true
}
Announcing a hosted service for converting TikTok metadata to a Microformats2 object.
{
"type": "entry",
"published": "2022-04-01T21:28:42+01:00",
"summary": "Announcing a hosted service for converting TikTok metadata to a Microformats2 object.",
"url": "https://www.jvt.me/posts/2022/04/01/tiktok-mf2/",
"featured": "https://media.jvt.me/7d22b1d040.png",
"category": [
"tiktok",
"tiktok-mf2",
"indieweb",
"microformats2"
],
"photo": [
"https://media.jvt.me/7d22b1d040.png"
],
"name": "Introducing tiktok-mf2.tanna.dev, for converting TikTok video metadata to Microformats2",
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "photo",
"_id": "28220750",
"_source": "2169",
"_is_read": true
}
