@okikio_dev This is a good place to start: https://indieweb.org/Webmention
There are lots of implementations in many languages you can use as examples or borrow from. Ask in chat.indieweb.org/dev/ for pointers/advice/help to cut through documentation and jargon.
{
"type": "entry",
"published": "2022-04-27T19:24:54+00:00",
"url": "http://stream.boffosocko.com/2022/okikio_dev-this-is-a-good-place-to-start-webmentionthere-are",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1519397310932955137"
],
"in-reply-to": [
"https://twitter.com/okikio_dev/status/1519003572037378050"
],
"content": {
"text": "@okikio_dev This is a good place to start: https://indieweb.org/Webmention\n\nThere are lots of implementations in many languages you can use as examples or borrow from. Ask in chat.indieweb.org/dev/ for pointers/advice/help to cut through documentation and jargon.",
"html": "<a href=\"https://twitter.com/okikio_dev\">@okikio_dev</a> This is a good place to start: <a href=\"https://indieweb.org/Webmention\">https://indieweb.org/Webmention</a><br />\nThere are lots of implementations in many languages you can use as examples or borrow from. Ask in chat.indieweb.org/dev/ for pointers/advice/help to cut through documentation and jargon."
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "reply",
"_id": "28737679",
"_source": "192",
"_is_read": true
}
Twitter’s only conclusion can be abandonment: an overdue MySpace-ification. I am totally confident about this prediction, but that’s an easy confidence, because in the long run, we’re all MySpace-ified.
What Robin said.
{
"type": "entry",
"published": "2022-04-27T08:45:51Z",
"url": "https://adactio.com/links/19020",
"category": [
"twitter",
"social",
"networks",
"silos",
"indieweb",
"myspace",
"platforms"
],
"bookmark-of": [
"https://www.robinsloan.com/lab/lost-thread/"
],
"content": {
"text": "The lost thread\n\n\n\n\n Twit\u00adter\u2019s only con\u00adclu\u00adsion can be abandonment: an over\u00addue MySpace-ification. I am totally con\u00adfi\u00addent about this prediction, but that\u2019s an easy confidence, because in the long run, we\u2019re all MySpace-ified.\n\n\nWhat Robin said.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.robinsloan.com/lab/lost-thread/\">\nThe lost thread\n</a>\n</h3>\n\n<blockquote>\n <p>Twit\u00adter\u2019s only con\u00adclu\u00adsion can be abandonment: an over\u00addue MySpace-ification. I am totally con\u00adfi\u00addent about this prediction, but that\u2019s an easy confidence, because in the long run, we\u2019re all MySpace-ified.</p>\n</blockquote>\n\n<p>What Robin said.</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "28725315",
"_source": "2",
"_is_read": true
}
@lauren_n_roth I'd buy! I can't wait to see what you come up with...
I've been helping to collect some prior art, examples, and UI patterns here if it helps to jumpstart your research/work: https://indieweb.org/directory
{
"type": "entry",
"published": "2022-04-26T22:49:40+00:00",
"url": "http://stream.boffosocko.com/2022/lauren_n_roth-id-buy-i-cant-wait-to-see-what-you",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1519086420916424707"
],
"in-reply-to": [
"https://twitter.com/lauren_n_roth/status/1518646498992480257"
],
"content": {
"text": "@lauren_n_roth I'd buy! I can't wait to see what you come up with...\n\nI've been helping to collect some prior art, examples, and UI patterns here if it helps to jumpstart your research/work: https://indieweb.org/directory",
"html": "<a href=\"https://twitter.com/lauren_n_roth\">@lauren_n_roth</a> I'd buy! I can't wait to see what you come up with...<br />\nI've been helping to collect some prior art, examples, and UI patterns here if it helps to jumpstart your research/work: <a href=\"https://indieweb.org/directory\">https://indieweb.org/directory</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "reply",
"_id": "28717045",
"_source": "192",
"_is_read": true
}
Welcome to all new faces. I hope some of you become passionate about the indieweb and our slice of it 🙂
{
"type": "entry",
"author": {
"name": "Fabio Russo",
"url": "https://fabiorusso.net",
"photo": "https://micro.blog/fabio/avatar.jpg"
},
"url": "https://www.fabiorusso.net/2022/04/26/welcome-to-all.html",
"content": {
"html": "<p>Welcome to all new faces. I hope some of you become passionate about the <a href=\"https://indieweb.org\">indieweb</a> and our slice of it \ud83d\ude42</p>",
"text": "Welcome to all new faces. I hope some of you become passionate about the indieweb and our slice of it \ud83d\ude42"
},
"published": "2022-04-26T14:16:32+00:00",
"post-type": "note",
"_id": "33380002",
"_source": "7224",
"_is_read": true
}
Not sure why, but seems like a lot of people on Twitter are sharing this link about downloading an archive of your data: https://twitter.com/settings/download_your_data
#OwnYourData #IndieWeb
{
"type": "entry",
"published": "2022-04-26T00:41:33+00:00",
"url": "http://stream.boffosocko.com/2022/not-sure-why-but-seems-like-a-lot-of-people",
"category": [
"OwnYourData",
"IndieWeb"
],
"syndication": [
"https://twitter.com/ChrisAldrich/status/1518752791665287169"
],
"content": {
"text": "Not sure why, but seems like a lot of people on Twitter are sharing this link about downloading an archive of your data: https://twitter.com/settings/download_your_data\n#OwnYourData #IndieWeb",
"html": "Not sure why, but seems like a lot of people on Twitter are sharing this link about downloading an archive of your data: <a href=\"https://twitter.com/settings/download_your_data\">https://twitter.com/settings/download_your_data</a><br /><a href=\"http://stream.boffosocko.com/tag/OwnYourData\" class=\"p-category\">#OwnYourData</a> <a href=\"http://stream.boffosocko.com/tag/IndieWeb\" class=\"p-category\">#IndieWeb</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "note",
"_id": "28695212",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-25T18:38:18+02:00",
"url": "https://notiz.blog/2022/04/25/die-twitter-posse/",
"name": "Die (Twitter) Posse",
"content": {
"text": "Im modernen Sprachgebrauch wird der Begriff [Posse] in \u00fcbertragenem Sinn [\u2026] genutzt, um als grotesk empfundene Vorg\u00e4nge in Gesellschaft und Politik zu beschreiben.\nhttps://de.wikipedia.org/wiki/Posse\n\n\n\n\nWer sich (aus gegebenem Anlass) sorgen um Twitter macht, sollte sich mal mit der etwas anderen POSSE befassen.\n\n\n\n\nPOSSE is an abbreviation for Publish (on your) Own Site, Syndicate Elsewhere, the practice of posting content on your own site first, then publishing copies or sharing links to third parties (like social media silos) with original post links to provide viewers a path to directly interacting with your content.\nhttps://indieweb.org/POSSE\n\n\n\n\nInstalliert euch WordPress! Ver\u00f6ffentlicht Texte, Bilder, Videos und Ideen nicht auf Twitter sondern auf eurer eigenen Seite! Teilt eure Inhalte \u00fcber Twitter!\n\n\n\nUnd sollte Twitter \u201everschwinden\u201c, teilt es \u00fcber Mastodon! usw, usw\u2026\n\n\n\nSchaut euch dazu gerne auch mal Brid.gy an!",
"html": "<blockquote>\n<p>Im modernen Sprachgebrauch wird der Begriff [Posse] in \u00fcbertragenem Sinn [\u2026] genutzt, um als grotesk empfundene Vorg\u00e4nge in Gesellschaft und Politik zu beschreiben.</p>\n<a href=\"https://de.wikipedia.org/wiki/Posse\">https://de.wikipedia.org/wiki/Posse</a>\n</blockquote>\n\n\n\n<p>Wer sich (<a href=\"https://www.faz.net/aktuell/wirtschaft/unternehmen/twitter-offenbar-doch-zum-verkauf-bereit-was-hat-elon-musk-vor-17982559.html\">aus gegebenem Anlass</a>) sorgen um Twitter macht, sollte sich mal mit der etwas anderen <strong>POSSE</strong> befassen.</p>\n\n\n\n<blockquote>\n<p><strong>POSSE</strong> is an abbreviation for <strong>Publish (on your) Own Site, <a href=\"https://indieweb.org/Category:syndication\">Syndicate</a> Elsewhere</strong>, the practice of posting content on your own site first, then publishing copies or sharing links to third parties (like <a href=\"https://indieweb.org/social_media\">social media</a> silos) with <a href=\"https://indieweb.org/original_post_link\">original post links</a> to provide viewers a path to directly interacting with your content.</p>\n<a href=\"https://indieweb.org/POSSE\">https://indieweb.org/POSSE</a>\n</blockquote>\n\n\n\n<p>Installiert euch WordPress! Ver\u00f6ffentlicht Texte, Bilder, Videos und Ideen nicht auf Twitter sondern auf eurer eigenen Seite! Teilt eure Inhalte \u00fcber Twitter!</p>\n\n\n\n<p>Und <a href=\"https://indieweb.org/site-deaths\">sollte Twitter \u201everschwinden\u201c</a>, <a href=\"https://notiz.blog/2020/12/31/activitypub-fuer-wordpress/\">teilt es \u00fcber Mastodon</a>! usw, usw\u2026</p>\n\n\n\n<p>Schaut euch dazu gerne auch mal <a href=\"https://notiz.blog/2014/01/16/bridgy-webmentions-fuer-twitter-und-facebook/\">Brid.gy</a> an!</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": "28691294",
"_source": "206",
"_is_read": true
}
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
}
