{
"type": "entry",
"published": "2023-02-19T16:45:51-0500",
"url": "https://martymcgui.re/2023/02/19/this-week-in-the-indieweb-audio-edition--february-11th---17th-2023/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://media.martymcgui.re/a7/84/66/43/7902a7a5e1d8a413bd3a2262a02b736d4e00881370ae34e3977cea22.mp3"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 February 11th - 17th, 2023",
"content": {
"text": "Show/Hide Transcript\n \n Rel you? Rel me. It\u2019s the audio edition for This Week in the IndieWeb for February 11th - 17th, 2023.\nYou can find all of my audio editions and subscribe with your favorite podcast app here: martymcgui.re/podcasts/indieweb/.\nMusic from Aaron Parecki\u2019s 100DaysOfMusic project: Day 85 - Suit, Day 48 - Glitch, Day 49 - Floating, Day 9, and Day 11\nThanks to everyone in the IndieWeb chat for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!",
"html": "Show/Hide Transcript\n \n <p>Rel you? Rel me. It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2023-02-17.html\">This Week in the IndieWeb for February 11th - 17th, 2023</a>.</p>\n<p>You can find all of my audio editions and subscribe with your favorite podcast app here: <a href=\"https://martymcgui.re/podcasts/indieweb/\">martymcgui.re/podcasts/indieweb/</a>.</p>\n<p>Music from <a href=\"https://aaronparecki.com/\">Aaron Parecki</a>\u2019s <a href=\"https://100.aaronparecki.com/\">100DaysOfMusic project</a>: <a href=\"https://aaronparecki.com/2017/03/15/14/day85\">Day 85 - Suit</a>, <a href=\"https://aaronparecki.com/2017/02/06/7/day48\">Day 48 - Glitch</a>, <a href=\"https://aaronparecki.com/2017/02/07/4/day49\">Day 49 - Floating</a>, <a href=\"https://aaronparecki.com/2016/12/29/21/day-9\">Day 9</a>, and <a href=\"https://aaronparecki.com/2016/12/31/15/\">Day 11</a></p>\n<p>Thanks to everyone in the <a href=\"https://chat.indieweb.org/\">IndieWeb chat</a> for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "audio",
"_id": "35271997",
"_source": "175",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2023/02/19/wrapping-up-activitypub.html",
"name": "Wrapping up ActivityPub improvements",
"content": {
"html": "<p>Another week, another round of ActivityPub-related improvements! Over the last few months we\u2019ve been filling in little details for Mastodon compatibility in Micro.blog. Were at the point where Micro.blog is a good fediverse citizen and has everything most people should need.</p>\n<p>Today I rolled out initial support for setting a Mastodon profile header image. This is a feature that Micro.blog doesn\u2019t currently have for its own profiles. Should it? I\u2019m not sure, but in the meantime I didn\u2019t want it to hold back anyone who likes profile headers on Mastodon.</p>\n<p>You can upload a profile header in Micro.blog under Account \u2192 View Mastodon Details. When Mastodon users follow your account, they will see the header on Mastodon. Here\u2019s a screenshot of part of the settings screen:</p>\n<img src=\"https://cdn.uploads.micro.blog/10/2023/0a38b2c7cd.png\" alt=\"Screenshot of Mastodon details page on Micro.blog with header upload button.\" style=\"max-width:600px;\" /><p>Micro.blog also does a better job of notifying followers on other servers when a profile photo updates. Mastodon generally has a different philosophy for storing images than Micro.blog does. Micro.blog loads most images as needed when they are viewed and caches them for a certain length of time, whereas Mastodon waits for a server to tell it that a profile or post has updated and then copies any images to its own server.</p>\n<p>We could take most major features in Micro.blog and keep fine-tuning them indefinitely. Mastodon support is no exception, but I think this is a good time to pause. Next week I\u2019m excited to revisit some pieces of the core Micro.blog platform that don\u2019t necessary have anything to do with the fediverse.</p>",
"text": "Another week, another round of ActivityPub-related improvements! Over the last few months we\u2019ve been filling in little details for Mastodon compatibility in Micro.blog. Were at the point where Micro.blog is a good fediverse citizen and has everything most people should need.\nToday I rolled out initial support for setting a Mastodon profile header image. This is a feature that Micro.blog doesn\u2019t currently have for its own profiles. Should it? I\u2019m not sure, but in the meantime I didn\u2019t want it to hold back anyone who likes profile headers on Mastodon.\nYou can upload a profile header in Micro.blog under Account \u2192 View Mastodon Details. When Mastodon users follow your account, they will see the header on Mastodon. Here\u2019s a screenshot of part of the settings screen:\nMicro.blog also does a better job of notifying followers on other servers when a profile photo updates. Mastodon generally has a different philosophy for storing images than Micro.blog does. Micro.blog loads most images as needed when they are viewed and caches them for a certain length of time, whereas Mastodon waits for a server to tell it that a profile or post has updated and then copies any images to its own server.\nWe could take most major features in Micro.blog and keep fine-tuning them indefinitely. Mastodon support is no exception, but I think this is a good time to pause. Next week I\u2019m excited to revisit some pieces of the core Micro.blog platform that don\u2019t necessary have anything to do with the fediverse."
},
"published": "2023-02-19T10:48:54-06:00",
"category": [
"Photos",
"Essays"
],
"post-type": "article",
"_id": "35265835",
"_source": "12",
"_is_read": false
}
Blogged: Webmentions can help create small networks around websites rather than social media ✍️ Webmentions provide a space for a small number of people to congregate online, wherever they find your posts. That’s why I’ve stuck with them.
{
"type": "entry",
"author": {
"name": "@leonp",
"url": "https://fosstodon.org/@leonp",
"photo": null
},
"url": "https://fosstodon.org/@leonp/109892402349859910",
"content": {
"html": "<p>Blogged: Webmentions can help create small networks around websites rather than social media \u270d\ufe0f Webmentions provide a space for a small number of people to congregate online, wherever they find your posts. That\u2019s why I\u2019ve stuck with them.<br /><br /> \ud83c\udff7 <a href=\"https://fosstodon.org/tags/Indieweb\">#<span>Indieweb</span></a> <a href=\"https://fosstodon.org/tags/Netlify\">#<span>Netlify</span></a> <a href=\"https://fosstodon.org/tags/RSS\">#<span>RSS</span></a> <a href=\"https://fosstodon.org/tags/webmentions\">#<span>webmentions</span></a><br /><a href=\"https://www.thisdaysportion.com/posts/stick-with-webmentions-to-create-small-networks/\"><span>https://www.</span><span>thisdaysportion.com/posts/stic</span><span>k-with-webmentions-to-create-small-networks/</span></a></p>",
"text": "Blogged: Webmentions can help create small networks around websites rather than social media \u270d\ufe0f Webmentions provide a space for a small number of people to congregate online, wherever they find your posts. That\u2019s why I\u2019ve stuck with them.\n\n \ud83c\udff7 #Indieweb #Netlify #RSS #webmentions\nhttps://www.thisdaysportion.com/posts/stick-with-webmentions-to-create-small-networks/"
},
"published": "2023-02-19T16:43:07+00:00",
"post-type": "note",
"_id": "35265667",
"_source": "7235",
"_is_read": false
}
I don't think people appreciate the role that #OperaSoftware played in fostering the #OpenWeb and #IndieWeb during the first #browserWar (when the #OperaBrowser was still built on their proprietary #Presto engine), and a fortiori the role it had in their demise (when they switched to being “just another #WebKit/#Blink skin”), despite their browser never even reaching a 3% market share.
{
"type": "entry",
"author": {
"name": "@oblomov",
"url": "https://sociale.network/@oblomov",
"photo": null
},
"url": "https://sociale.network/@oblomov/109891147483410236",
"content": {
"html": "<p>I don't think people appreciate the role that <a href=\"https://sociale.network/tags/OperaSoftware\">#<span>OperaSoftware</span></a> played in fostering the <a href=\"https://sociale.network/tags/OpenWeb\">#<span>OpenWeb</span></a> and <a href=\"https://sociale.network/tags/IndieWeb\">#<span>IndieWeb</span></a> during the first <a href=\"https://sociale.network/tags/browserWar\">#<span>browserWar</span></a> (when the <a href=\"https://sociale.network/tags/OperaBrowser\">#<span>OperaBrowser</span></a> was still built on their proprietary <a href=\"https://sociale.network/tags/Presto\">#<span>Presto</span></a> engine), and a fortiori the role it had in their demise (when they switched to being \u201cjust another <a href=\"https://sociale.network/tags/WebKit\">#<span>WebKit</span></a>/#Blink skin\u201d), despite their browser never even reaching a 3% market share.</p>",
"text": "I don't think people appreciate the role that #OperaSoftware played in fostering the #OpenWeb and #IndieWeb during the first #browserWar (when the #OperaBrowser was still built on their proprietary #Presto engine), and a fortiori the role it had in their demise (when they switched to being \u201cjust another #WebKit/#Blink skin\u201d), despite their browser never even reaching a 3% market share."
},
"published": "2023-02-19T11:23:59+00:00",
"post-type": "note",
"_id": "35259848",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@box464",
"url": "https://mastodon.social/@box464",
"photo": null
},
"url": "https://mastodon.social/@box464/109887173564115329",
"content": {
"html": "<p>Hey <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a>, with webmentions.app down for the past few weeks, what alternatives are being recommended for sending <a href=\"https://mastodon.social/tags/WebMentions\">#<span>WebMentions</span></a> to others from a <a href=\"https://mastodon.social/tags/StaticSite\">#<span>StaticSite</span></a> that uses <a href=\"https://mastodon.social/tags/Jekyll\">#<span>Jekyll</span></a>, <a href=\"https://mastodon.social/tags/Hugo\">#<span>Hugo</span></a>, <a href=\"https://mastodon.social/tags/Eleventy\">#<span>Eleventy</span></a>? </p><p>Whatever it is, I want something self contained that I run locally. I think the <a href=\"https://mastodon.social/tags/POSSE\">#<span>POSSE</span></a> mentality is finally taking over for me. \ud83d\ude05</p><p>Looking at this one once I get moved over to Netlify, but would love to get a thread going with other options, too. </p><p><a href=\"https://www.netlify.com/integrations/community-built/webmentions-build-plugin/\"><span>https://www.</span><span>netlify.com/integrations/commu</span><span>nity-built/webmentions-build-plugin/</span></a></p>",
"text": "Hey #IndieWeb, with webmentions.app down for the past few weeks, what alternatives are being recommended for sending #WebMentions to others from a #StaticSite that uses #Jekyll, #Hugo, #Eleventy? Whatever it is, I want something self contained that I run locally. I think the #POSSE mentality is finally taking over for me. \ud83d\ude05Looking at this one once I get moved over to Netlify, but would love to get a thread going with other options, too. https://www.netlify.com/integrations/community-built/webmentions-build-plugin/"
},
"published": "2023-02-18T18:33:22+00:00",
"post-type": "note",
"_id": "35247856",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@m2m",
"url": "https://indieweb.social/@m2m",
"photo": null
},
"url": "https://indieweb.social/@m2m/109886091660089799",
"content": {
"html": "<p>If you have iOS or macOS (Monterey or later) and you use Shortcuts, this is a brilliant way to exploit the tools with Micropub:</p><p><a href=\"https://cagrimmett.com/development/2023/02/12/ios-shortcut-actions-for-micropub-posting/\"><span>https://</span><span>cagrimmett.com/development/202</span><span>3/02/12/ios-shortcut-actions-for-micropub-posting/</span></a></p><p>Written by <a href=\"https://toot.cafe/@cagrimmett\"><span>https://</span><span>toot.cafe/@cagrimmett</span><span></span></a></p><p><a href=\"https://indieweb.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://indieweb.social/tags/MicroPub\">#<span>MicroPub</span></a></p>",
"text": "If you have iOS or macOS (Monterey or later) and you use Shortcuts, this is a brilliant way to exploit the tools with Micropub:https://cagrimmett.com/development/2023/02/12/ios-shortcut-actions-for-micropub-posting/Written by https://toot.cafe/@cagrimmett#IndieWeb #MicroPub"
},
"published": "2023-02-18T13:58:13+00:00",
"post-type": "note",
"_id": "35242654",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@etta",
"url": "https://gusto.masto.host/@etta",
"photo": null
},
"url": "https://gusto.masto.host/@etta/109885847326202659",
"content": {
"html": "<p>\u5b8c\ud83d\udd3b\u5168\ud83d\udd3b\u540c\ud83d\udd3b\u610f</p><p>\u201cSometimes I feel like thanking Elon for driving me towards the <a href=\"https://gusto.masto.host/tags/Fediverse\">#<span>Fediverse</span></a> <a href=\"https://gusto.masto.host/tags/Mastodon\">#<span>Mastodon</span></a> and <a href=\"https://gusto.masto.host/tags/IndieWeb\">#<span>IndieWeb</span></a> plus reviving my love for personal <a href=\"https://gusto.masto.host/tags/blogging\">#<span>blogging</span></a> . \u201d</p><p>\u201cMy online creative life has improved immeasurably as a result \u201d</p><p><a href=\"https://hachyderm.io/@liztai/109883631400740139\"><span>https://</span><span>hachyderm.io/@liztai/109883631</span><span>400740139</span></a></p>",
"text": "\u5b8c\ud83d\udd3b\u5168\ud83d\udd3b\u540c\ud83d\udd3b\u610f\u201cSometimes I feel like thanking Elon for driving me towards the #Fediverse #Mastodon and #IndieWeb plus reviving my love for personal #blogging . \u201d\u201cMy online creative life has improved immeasurably as a result \u201dhttps://hachyderm.io/@liztai/109883631400740139"
},
"published": "2023-02-18T12:56:05+00:00",
"post-type": "note",
"_id": "35241753",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@davidrobin",
"url": "https://mastodon.social/@davidrobin",
"photo": null
},
"url": "https://mastodon.social/@davidrobin/109884868716090527",
"content": {
"html": "<p>CSS Container Queries (now available on major browers as Firefox just followed suit) look promising to craft our websites even more subtly, brand new container query length units attached <a href=\"https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries\"><span>https://</span><span>developer.mozilla.org/en-US/do</span><span>cs/Web/CSS/CSS_Container_Queries</span></a> <a href=\"https://mastodon.social/tags/webdev\">#<span>webdev</span></a> <a href=\"https://mastodon.social/tags/css\">#<span>css</span></a> <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodon.social/tags/attentiontodetails\">#<span>attentiontodetails</span></a></p>",
"text": "CSS Container Queries (now available on major browers as Firefox just followed suit) look promising to craft our websites even more subtly, brand new container query length units attached https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries #webdev #css #indieweb #attentiontodetails"
},
"published": "2023-02-18T08:47:12+00:00",
"post-type": "note",
"_id": "35238719",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@brianjesse",
"url": "https://mastodon.social/@brianjesse",
"photo": null
},
"url": "https://mastodon.social/@brianjesse/109883849053762165",
"content": {
"html": "<p>amazing to see all of the new micro blogging networks: Scuttlebutt, Nostr, Mastodon and Feedland - I think RSS will be huge in the new landscape because there are 15 million+ sites already equipped - huge ecosystem. I wonder how the Tweetbot mastodon client is doing, anyone using it ? <a href=\"https://mastodon.social/tags/microblogging\">#<span>microblogging</span></a> <a href=\"https://mastodon.social/tags/RSS\">#<span>RSS</span></a> <a href=\"https://mastodon.social/tags/blockchain\">#<span>blockchain</span></a> <a href=\"https://mastodon.social/tags/activitypub\">#<span>activitypub</span></a> <a href=\"https://mastodon.social/tags/feedland\">#<span>feedland</span></a> <a href=\"https://mastodon.social/tags/ostatus\">#<span>ostatus</span></a> <a href=\"https://mastodon.social/tags/pubsubhubbub\">#<span>pubsubhubbub</span></a> <a href=\"https://mastodon.social/tags/identica\">#<span>identica</span></a> <a href=\"https://mastodon.social/tags/laconica\">#<span>laconica</span></a> <a href=\"https://mastodon.social/tags/twitarmy\">#<span>twitarmy</span></a> <a href=\"https://mastodon.social/tags/friendfeed\">#<span>friendfeed</span></a> <a href=\"https://mastodon.social/tags/track\">#<span>track</span></a> <a href=\"https://mastodon.social/tags/xmpp\">#<span>xmpp</span></a> <a href=\"https://mastodon.social/tags/jabber\">#<span>jabber</span></a> <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodon.social/tags/dweb\">#<span>dweb</span></a> <a href=\"https://mastodon.social/tags/web3\">#<span>web3</span></a></p>",
"text": "amazing to see all of the new micro blogging networks: Scuttlebutt, Nostr, Mastodon and Feedland - I think RSS will be huge in the new landscape because there are 15 million+ sites already equipped - huge ecosystem. I wonder how the Tweetbot mastodon client is doing, anyone using it ? #microblogging #RSS #blockchain #activitypub #feedland #ostatus #pubsubhubbub #identica #laconica #twitarmy #friendfeed #track #xmpp #jabber #indieweb #dweb #web3"
},
"published": "2023-02-18T04:27:54+00:00",
"post-type": "note",
"_id": "35236206",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@cordillera",
"url": "https://social.horrorhub.club/@cordillera",
"photo": null
},
"url": "https://social.horrorhub.club/@cordillera/109883817957414554",
"content": {
"html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://hachyderm.io/@liztai\">@<span>liztai</span></a></span> <a href=\"https://social.horrorhub.club/tags/Mastodon\">#<span>Mastodon</span></a> is only the gateway drug to the <a href=\"https://social.horrorhub.club/tags/IndieWeb\">#<span>IndieWeb</span></a> lmao</p><p>what activity pub. you mean blogs?? \ud83d\ude04</p>",
"text": "@liztai #Mastodon is only the gateway drug to the #IndieWeb lmaowhat activity pub. you mean blogs?? \ud83d\ude04"
},
"published": "2023-02-18T04:20:39+00:00",
"post-type": "note",
"_id": "35236207",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@liztai",
"url": "https://hachyderm.io/@liztai",
"photo": null
},
"url": "https://hachyderm.io/@liztai/109883631400740139",
"content": {
"html": "<p>Sometimes I feel like thanking Elon for driving me towards the <a href=\"https://hachyderm.io/tags/Fediverse\">#<span>Fediverse</span></a> <a href=\"https://hachyderm.io/tags/Mastodon\">#<span>Mastodon</span></a> and <a href=\"https://hachyderm.io/tags/IndieWeb\">#<span>IndieWeb</span></a> plus reviving my love for personal <a href=\"https://hachyderm.io/tags/blogging\">#<span>blogging</span></a> .</p><p>Without his nonsense at <a href=\"https://hachyderm.io/tags/Twitter\">#<span>Twitter</span></a> I would not have discovered a way to escape walled platforms \ud83d\ude06</p><p>My online creative life has improved immeasurably as a result</p><p>Give credit where credit is due</p>",
"text": "Sometimes I feel like thanking Elon for driving me towards the #Fediverse #Mastodon and #IndieWeb plus reviving my love for personal #blogging .Without his nonsense at #Twitter I would not have discovered a way to escape walled platforms \ud83d\ude06My online creative life has improved immeasurably as a resultGive credit where credit is due"
},
"published": "2023-02-18T03:32:32+00:00",
"post-type": "note",
"_id": "35235837",
"_source": "7235",
"_is_read": false
}
How does one improve the "reach" of a single user instance? The basic issue is when clicking on a toot from my other persona I regularly do not see many other replies unless I go to the original.
Here on #IndieWeb that's less of a problem. Obviously if I were more interesting and provoked greater engagement this would probably improve on its own. But let's just make the assumption that I'm going to continue to post garbage...
{
"type": "entry",
"author": {
"name": "@thom",
"url": "https://indieweb.social/@thom",
"photo": null
},
"url": "https://indieweb.social/@thom/109880959519565047",
"content": {
"html": "<p>Question regarding <a href=\"https://indieweb.social/tags/federation\">#<span>federation</span></a> -</p><p>How does one improve the \"reach\" of a single user instance? The basic issue is when clicking on a toot from my other persona I regularly do not see many other replies unless I go to the original.</p><p>Here on <a href=\"https://indieweb.social/tags/IndieWeb\">#<span>IndieWeb</span></a> that's less of a problem. Obviously if I were more interesting and provoked greater engagement this would probably improve on its own. But let's just make the assumption that I'm going to continue to post garbage...</p><p><a href=\"https://indieweb.social/tags/MastoAdmin\">#<span>MastoAdmin</span></a> <a href=\"https://indieweb.social/tags/MastodonQuestion\">#<span>MastodonQuestion</span></a></p>",
"text": "Question regarding #federation -How does one improve the \"reach\" of a single user instance? The basic issue is when clicking on a toot from my other persona I regularly do not see many other replies unless I go to the original.Here on #IndieWeb that's less of a problem. Obviously if I were more interesting and provoked greater engagement this would probably improve on its own. But let's just make the assumption that I'm going to continue to post garbage...#MastoAdmin #MastodonQuestion"
},
"published": "2023-02-17T16:13:03+00:00",
"post-type": "note",
"_id": "35222762",
"_source": "7235",
"_is_read": false
}
C# will still be a language for me, but getting #OpenCAD off the ground right now is a little more important than being able to send #IndieWeb#Webmentions from #dotnet.
{
"type": "entry",
"author": {
"name": "@katmmoss",
"url": "https://social.faebornnetworks.org/@katmmoss",
"photo": null
},
"url": "https://social.faebornnetworks.org/@katmmoss/109880138618182255",
"content": {
"html": "<p>C# will still be a language for me, but getting <a href=\"https://social.faebornnetworks.org/tags/OpenCAD\">#<span>OpenCAD</span></a> off the ground right now is a little more important than being able to send <a href=\"https://social.faebornnetworks.org/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://social.faebornnetworks.org/tags/Webmentions\">#<span>Webmentions</span></a> from <a href=\"https://social.faebornnetworks.org/tags/dotnet\">#<span>dotnet</span></a>.</p>",
"text": "C# will still be a language for me, but getting #OpenCAD off the ground right now is a little more important than being able to send #IndieWeb #Webmentions from #dotnet."
},
"published": "2023-02-17T12:44:17+00:00",
"post-type": "note",
"_id": "35217916",
"_source": "7235",
"_is_read": false
}
Sighs at getting the 422 error from the Mastodon server when my RSS feed pushed to Mastodon via IFTTT. Brings back memories of it taking hours to get crossposting up and running.
{
"type": "entry",
"author": {
"name": "@leonp",
"url": "https://fosstodon.org/@leonp",
"photo": null
},
"url": "https://fosstodon.org/@leonp/109880134005724387",
"content": {
"html": "<p>Sighs at getting the 422 error from the Mastodon server when my RSS feed pushed to Mastodon via IFTTT. Brings back memories of it taking hours to get crossposting up and running.</p><p>No-one ever said <a href=\"https://fosstodon.org/tags/indieweb\">#<span>indieweb</span></a> was gonna be easy.</p><p> <br /><br /><br /><a href=\"https://www.thisdaysportion.com/notes/no-one-ever-said-indieweb-was-gonna-be-easy\"><span>https://www.</span><span>thisdaysportion.com/notes/no-o</span><span>ne-ever-said-indieweb-was-gonna-be-easy</span></a></p>",
"text": "Sighs at getting the 422 error from the Mastodon server when my RSS feed pushed to Mastodon via IFTTT. Brings back memories of it taking hours to get crossposting up and running.No-one ever said #indieweb was gonna be easy. \n\n\nhttps://www.thisdaysportion.com/notes/no-one-ever-said-indieweb-was-gonna-be-easy"
},
"published": "2023-02-17T12:43:06+00:00",
"post-type": "note",
"_id": "35217917",
"_source": "7235",
"_is_read": false
}
Almost done getting a #dataviz#gephi academic researcher to join the open web with his own micro.blog as a starter!
Which reminds me that my blog has been down for lazy/lack of time reasons for more than a year and it's high time I fix it and give it some love and regularity! #indieweb
{
"type": "entry",
"author": {
"name": "@rmdes",
"url": "https://mstdn.social/@rmdes",
"photo": null
},
"url": "https://mstdn.social/@rmdes/109879331795920027",
"content": {
"html": "<p>Almost done getting a <a href=\"https://mstdn.social/tags/dataviz\">#<span>dataviz</span></a> <a href=\"https://mstdn.social/tags/gephi\">#<span>gephi</span></a> academic researcher to join the open web with his own micro.blog as a starter! </p><p>Which reminds me that my blog has been down for lazy/lack of time reasons for more than a year and it's high time I fix it and give it some love and regularity! <a href=\"https://mstdn.social/tags/indieweb\">#<span>indieweb</span></a></p>",
"text": "Almost done getting a #dataviz #gephi academic researcher to join the open web with his own micro.blog as a starter! Which reminds me that my blog has been down for lazy/lack of time reasons for more than a year and it's high time I fix it and give it some love and regularity! #indieweb"
},
"published": "2023-02-17T09:19:06+00:00",
"post-type": "note",
"_id": "35214817",
"_source": "7235",
"_is_read": false
}
It's a good practice when developing user apps solo to finish and walk away fro a week or two, then come back and run it. You'll feel more like a user and less like the developer. Hopefully looking more critically at what the experience is like. Just did that for my new IG to blog export tool and found a list of things needing improvement. #indieweb#dev
{
"type": "entry",
"author": {
"name": "@meadowhawk",
"url": "https://indieweb.social/@meadowhawk",
"photo": null
},
"url": "https://indieweb.social/@meadowhawk/109878152493049923",
"content": {
"html": "<p>It's a good practice when developing user apps solo to finish and walk away fro a week or two, then come back and run it. You'll feel more like a user and less like the developer. Hopefully looking more critically at what the experience is like. Just did that for my new IG to blog export tool and found a list of things needing improvement. <a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://indieweb.social/tags/dev\">#<span>dev</span></a></p>",
"text": "It's a good practice when developing user apps solo to finish and walk away fro a week or two, then come back and run it. You'll feel more like a user and less like the developer. Hopefully looking more critically at what the experience is like. Just did that for my new IG to blog export tool and found a list of things needing improvement. #indieweb #dev"
},
"published": "2023-02-17T04:19:11+00:00",
"post-type": "note",
"_id": "35210971",
"_source": "7235",
"_is_read": false
}
Nineteen years ago last Saturday, @KevinMarks.com & I introduced¹ #microformats@OReillyMedia ETech 2004, building on “semantic (x)html”.
We’ve come a long way since, from methodologies to #microformats2, from publishing to peer-to-peer #IndieWeb use-cases.
We named #microformats only after we had established a pattern of real world examples; even our talk proposal was named RealWorldSemantics², and provided examples in that broader theme.
This exemplified important implicit values in ordering our efforts: 1. get real world things working first, not just theory 2. name them after a pattern emerges, not just solo efforts 3. grow the pattern with proposals, prototypes, iteration, evolution
The examples at that point in time: * XFN — using rel-values for blogroll semantics, and the technology that defined rel=me in v1.1³, now the standard for decentralized social media verification on Mastodon⁴, GitHub⁵, elsewhere, and the basis of RelMeAuth⁶ * XMDP — XHTML MetaData Profiles, notably using an HTML class⁷ with a particular value 'profile' to indicate presence of a specific semantic structure * XOXO — XHTML Outlines, formalizing existing usage of (X)HTML elements for outlines, also using an HTML class with a particular value 'xoxo' to express a semantic
Growing the pattern: * rel=license — solved page licensing better than before, since widespread adopted * VoteLinks — new rel values, prototyped, only one consuming implementation (since defunct)
And further brainstorming: * recommendations — initial rel="recommendation" idea eventually evolved to hReview, and today’s h-review * syndication — helped motivate HTML5 <time> element, eventually led to hAtom, and today’s h-entry * playlists — led to various ideas, proposals, & demos⁸, still not really solved today
The mid-2000s were a time of eager experimentation, when we were learning that very small bits of markup (yes, hence the name) could be used to build some very useful capabilities on top of the open web platform.
A few observations with the benefit of years of experience since we proposed “microformats”:
One: Many microformats succeeded because we solved an existing problem, with existing *complex* solutions, by providing a drastically *simpler* solution.
XFN instead of FOAF. rel=license instead of Creative Commons RDF in HTML comments.
By doing so, we skipped the often harder problem of defining & refining a problem worth solving, a use-case, or user scenario.
Two: A few microformats succeeded because they solved existing problems, re-using *existing established* open solutions in other formats, reformatted into native HTML.
hCard from vCard. hCalendar from iCalendar.
This methodology leveraged years of prior hard open standards work by numerous others across numerous organizations, and deliberately avoided the bikeshedding trap of renaming things (or any other kind of non-trivial “clean-up”) while reformatting, thus making it easy for developers of one technology to see the 1:1 mapping and use the other.
The primary downside with this approach was formats that were larger than perhaps necessary for HTML-specific use-cases.
Eventually for microformats2 vocabularies, we adopted a subset approach, looking for web publishing use-cases for each feature, making h-card smaller than hCard, and h-event smaller than hCalendar.
Three: Success in a search engine was not enough, and sometimes attracted more bad actors than good. @KevinMarks.com, myself, and others at Technorati built search engine indexing and use of rel-tag and hReview, which helped evolve their specifications. A few other small search engines indexed rel=tag markup, however none remain today. hReview was adopted by Google which led to it being heavily spammed.
This pattern repeated itself with other microformats, and eventually we shifted from: → of course search is the first obvious use-case → search is one use-case among others → we need primary use-cases outside of search for longterm ecosystem success Which leads to the fourth observation.
Four: Publishing alone is not a use-case. There must be multiple consuming code use-cases (beyond search) for a microformat to succeed longterm.
From individual features to whole microformats vocabularies, we learned that not only did there need to be sufficient content being published already, without microformats, that could benefit, but there needed to be good enough consuming code use-cases that benefited users (not just developers). The #IndieWeb community has been exceptionally helpful in both defining such use-cases and iterating on them with implementations.
We still get questions of the form: What’s the best way to mark this up?
I used to very much believe that if you could mark something up more semantically, you should spend the time & effort to do so. This drove a lot of early experiments with markup, and did provide some eventual benefits, most notably when semantic HTML elements provided good hooks for accessibility tools such as screen readers.
Now we know the answer to the question of “How should I mark-up this content?” must be accompanied by specific use-cases for consuming code of that markup.
If there is no consuming code use-case, it is not worth the time to add the mark-up (never mind the maintenance effort over time).
Sometimes one single consuming code use-case is sufficient to justify the time & effort to add more semantic mark-up. If that markup helps screenreaders, then it’s worth it. More often than not however, there must be multiple (again, beyond search) consuming code use-cases for it to be worth adding semantic markup, and certainly for developing new markup, whether microformats features or new microformats.
This focus on and repeated asking of questions like: * What is the (consuming code) use-case? * Or how does it benefit readers of this content? has helped focus our modern microformats efforts on actual benefits to humans first, and machines second (if at all).
If you think of IndieWeb use-cases for existing or new microformats, come join us in the developers chat: * https://chat.indieweb.org/dev
If you think of other use-cases or want to chat about modern microformats methodologies in general, join us in the microformats chat: * https://chat.indieweb.org/microformats
{
"type": "entry",
"published": "2023-02-16 17:01-0800",
"url": "http://tantek.com/2023/047/t1/nineteen-years-microformats",
"category": [
"microformats",
"microformats2",
"IndieWeb",
"100DaysOfIndieWeb",
"100Days"
],
"content": {
"text": "Nineteen years ago last Saturday, @KevinMarks.com & I introduced\u00b9 #microformats @OReillyMedia ETech 2004, building on \u201csemantic (x)html\u201d.\n\nWe\u2019ve come a long way since, from methodologies to #microformats2, from publishing to peer-to-peer #IndieWeb use-cases.\n\nWe named #microformats only after we had established a pattern of real world examples; even our talk proposal was named RealWorldSemantics\u00b2, and provided examples in that broader theme.\n\nThis exemplified important implicit values in ordering our efforts:\n1. get real world things working first, not just theory\n2. name them after a pattern emerges, not just solo efforts\n3. grow the pattern with proposals, prototypes, iteration, evolution\n\nThe examples at that point in time:\n* XFN \u2014 using rel-values for blogroll semantics, and the technology that defined rel=me in v1.1\u00b3, now the standard for decentralized social media verification on Mastodon\u2074, GitHub\u2075, elsewhere, and the basis of RelMeAuth\u2076\n* XMDP \u2014 XHTML MetaData Profiles, notably using an HTML class\u2077 with a particular value 'profile' to indicate presence of a specific semantic structure\n* XOXO \u2014 XHTML Outlines, formalizing existing usage of (X)HTML elements for outlines, also using an HTML class with a particular value 'xoxo' to express a semantic\n\nGrowing the pattern:\n* rel=license \u2014 solved page licensing better than before, since widespread adopted\n* VoteLinks \u2014 new rel values, prototyped, only one consuming implementation (since defunct)\n\nAnd further brainstorming:\n* recommendations \u2014 initial rel=\"recommendation\" idea eventually evolved to hReview, and today\u2019s h-review\n* syndication \u2014 helped motivate HTML5 <time> element, eventually led to hAtom, and today\u2019s h-entry\n* playlists \u2014 led to various ideas, proposals, & demos\u2078, still not really solved today\n\n\nThe mid-2000s were a time of eager experimentation, when we were learning that very small bits of markup (yes, hence the name) could be used to build some very useful capabilities on top of the open web platform.\n\nA few observations with the benefit of years of experience since we proposed \u201cmicroformats\u201d:\n\n\nOne: Many microformats succeeded because we solved an existing problem, with existing *complex* solutions, by providing a drastically *simpler* solution.\n\nXFN instead of FOAF. rel=license instead of Creative Commons RDF in HTML comments.\n\nBy doing so, we skipped the often harder problem of defining & refining a problem worth solving, a use-case, or user scenario.\n\n\nTwo: A few microformats succeeded because they solved existing problems, re-using *existing established* open solutions in other formats, reformatted into native HTML.\n\nhCard from vCard. hCalendar from iCalendar.\n\nThis methodology leveraged years of prior hard open standards work by numerous others across numerous organizations, and deliberately avoided the bikeshedding trap of renaming things (or any other kind of non-trivial \u201cclean-up\u201d) while reformatting, thus making it easy for developers of one technology to see the 1:1 mapping and use the other.\n\nThe primary downside with this approach was formats that were larger than perhaps necessary for HTML-specific use-cases.\n\nEventually for microformats2 vocabularies, we adopted a subset approach, looking for web publishing use-cases for each feature, making h-card smaller than hCard, and h-event smaller than hCalendar.\n\n\nThree: Success in a search engine was not enough, and sometimes attracted more bad actors than good. @KevinMarks.com, myself, and others at Technorati built search engine indexing and use of rel-tag and hReview, which helped evolve their specifications. A few other small search engines indexed rel=tag markup, however none remain today. hReview was adopted by Google which led to it being heavily spammed.\n\nThis pattern repeated itself with other microformats, and eventually we shifted from:\n\u2192 of course search is the first obvious use-case\n\u2192 search is one use-case among others\n\u2192 we need primary use-cases outside of search for longterm ecosystem success\nWhich leads to the fourth observation.\n\n\nFour: Publishing alone is not a use-case. There must be multiple consuming code use-cases (beyond search) for a microformat to succeed longterm.\n\nFrom individual features to whole microformats vocabularies, we learned that not only did there need to be sufficient content being published already, without microformats, that could benefit, but there needed to be good enough consuming code use-cases that benefited users (not just developers). The #IndieWeb community has been exceptionally helpful in both defining such use-cases and iterating on them with implementations.\n\nWe still get questions of the form: What\u2019s the best way to mark this up?\n\nI used to very much believe that if you could mark something up more semantically, you should spend the time & effort to do so. This drove a lot of early experiments with markup, and did provide some eventual benefits, most notably when semantic HTML elements provided good hooks for accessibility tools such as screen readers.\n\nNow we know the answer to the question of \u201cHow should I mark-up this content?\u201d must be accompanied by specific use-cases for consuming code of that markup. \n\nIf there is no consuming code use-case, it is not worth the time to add the mark-up (never mind the maintenance effort over time).\n\nSometimes one single consuming code use-case is sufficient to justify the time & effort to add more semantic mark-up. If that markup helps screenreaders, then it\u2019s worth it. More often than not however, there must be multiple (again, beyond search) consuming code use-cases for it to be worth adding semantic markup, and certainly for developing new markup, whether microformats features or new microformats.\n\n\nThis focus on and repeated asking of questions like:\n* What is the (consuming code) use-case? \n* Or how does it benefit readers of this content?\nhas helped focus our modern microformats efforts on actual benefits to humans first, and machines second (if at all).\n\n\nIf you think of IndieWeb use-cases for existing or new microformats, come join us in the developers chat:\n* https://chat.indieweb.org/dev\n\nIf you think of other use-cases or want to chat about modern microformats methodologies in general, join us in the microformats chat:\n* https://chat.indieweb.org/microformats\n\n\nThis is day 32 of #100DaysOfIndieWeb #100Days\n\n\u2190 Day 31: https://tantek.com/2023/044/t1/unified-sent-box-universal-outbox\n\u2192 \ud83d\udd2e\n\n\nPost glossary:\n\nh-card\n\u00a0https://microformats.org/wiki/h-card\nh-entry\n\u00a0https://microformats.org/wiki/h-entry\nh-event\n\u00a0https://microformats.org/wiki/h-event\nh-review\n\u00a0https://microformats.org/wiki/h-review\nhAtom\n\u00a0https://microformats.org/wiki/hatom\nhCalendar\n\u00a0https://microformats.org/wiki/hcalendar\nhCard\n\u00a0https://microformats.org/wiki/hcard\nhReview\n\u00a0https://microformats.org/wiki/hreview\nrel-license\n\u00a0https://microformats.org/wiki/rel-license\nrel-tag\n\u00a0https://microformats.org/wiki/rel-tag\nrel-values\n\u00a0https://microformats.org/wiki/existing-rel-values\nXFN\n\u00a0https://gmpg.org/xfn/\nXMDP\n\u00a0http://gmpg.org/xmdp/description\nXOXO\n\u00a0https://microformats.org/wiki/xoxo\n\n\nPreviously, previously, previously:\n* https://tantek.com/2019/044/t1/15-years-ago-introduced-microformats\n* https://tantek.com/2014/042/t2/ten-years-ago-introduced-microformats-etech\n* https://tantek.com/2011/042/t2/years-ago-presented-microformats-etech\n* https://twitter.com/t/status/701095802\n\n\nReferences:\n\u00b9 https://tantek.com/presentations/2004etech/realworldsemanticspres.html\n\u00b2 https://tantek.com/log/2004/02.html#d04t1311\n\u00b3 https://gmpg.org/xfn/11#me\n\u2074 https://docs.joinmastodon.org/user/profile/#verification\n\u2075 https://hachyderm.io/@nova/109790530971147702\n\u2076 https://tantek.com/2023/032/t1/years-relmeauth-replace-openid\n\u2077 https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors\n\u2078 http://microformats.org/wiki/events/2007-12-11-open-media-web",
"html": "Nineteen years ago last Saturday, <a href=\"https://KevinMarks.com\">@KevinMarks.com</a> & I introduced<a href=\"http://tantek.com/#t5PQ1_note-1\">\u00b9</a> #<span class=\"p-category\">microformats</span> <a class=\"h-cassis-username\" href=\"https://twitter.com/OReillyMedia\">@OReillyMedia</a> ETech 2004, building on \u201csemantic (x)html\u201d.<br /><br />We\u2019ve come a long way since, from methodologies to #<span class=\"p-category\">microformats2</span>, from publishing to peer-to-peer #<span class=\"p-category\">IndieWeb</span> use-cases.<br /><br />We named #<span class=\"p-category\">microformats</span> only after we had established a pattern of real world examples; even our talk proposal was named RealWorldSemantics<a href=\"http://tantek.com/#t5PQ1_note-2\">\u00b2</a>, and provided examples in that broader theme.<br /><br />This exemplified important implicit values in ordering our efforts:<br />1. get real world things working first, not just theory<br />2. name them after a pattern emerges, not just solo efforts<br />3. grow the pattern with proposals, prototypes, iteration, evolution<br /><br />The examples at that point in time:<br />* XFN \u2014 using rel-values for blogroll semantics, and the technology that defined rel=me in v1.1<a href=\"http://tantek.com/#t5PQ1_note-3\">\u00b3</a>, now the standard for decentralized social media verification on Mastodon<a href=\"http://tantek.com/#t5PQ1_note-4\">\u2074</a>, GitHub<a href=\"http://tantek.com/#t5PQ1_note-5\">\u2075</a>, elsewhere, and the basis of RelMeAuth<a href=\"http://tantek.com/#t5PQ1_note-6\">\u2076</a><br />* XMDP \u2014 XHTML MetaData Profiles, notably using an HTML class<a href=\"http://tantek.com/#t5PQ1_note-7\">\u2077</a> with a particular value 'profile' to indicate presence of a specific semantic structure<br />* XOXO \u2014 XHTML Outlines, formalizing existing usage of (X)HTML elements for outlines, also using an HTML class with a particular value 'xoxo' to express a semantic<br /><br />Growing the pattern:<br />* rel=license \u2014 solved page licensing better than before, since widespread adopted<br />* VoteLinks \u2014 new rel values, prototyped, only one consuming implementation (since defunct)<br /><br />And further brainstorming:<br />* recommendations \u2014 initial rel=\"recommendation\" idea eventually evolved to hReview, and today\u2019s h-review<br />* syndication \u2014 helped motivate HTML5 <time> element, eventually led to hAtom, and today\u2019s h-entry<br />* playlists \u2014 led to various ideas, proposals, & demos<a href=\"http://tantek.com/#t5PQ1_note-8\">\u2078</a>, still not really solved today<br /><br /><br />The mid-2000s were a time of eager experimentation, when we were learning that very small bits of markup (yes, hence the name) could be used to build some very useful capabilities on top of the open web platform.<br /><br />A few observations with the benefit of years of experience since we proposed \u201cmicroformats\u201d:<br /><br /><br />One: Many microformats succeeded because we solved an existing problem, with existing *complex* solutions, by providing a drastically *simpler* solution.<br /><br />XFN instead of FOAF. rel=license instead of Creative Commons RDF in HTML comments.<br /><br />By doing so, we skipped the often harder problem of defining & refining a problem worth solving, a use-case, or user scenario.<br /><br /><br />Two: A few microformats succeeded because they solved existing problems, re-using *existing established* open solutions in other formats, reformatted into native HTML.<br /><br />hCard from vCard. hCalendar from iCalendar.<br /><br />This methodology leveraged years of prior hard open standards work by numerous others across numerous organizations, and deliberately avoided the bikeshedding trap of renaming things (or any other kind of non-trivial \u201cclean-up\u201d) while reformatting, thus making it easy for developers of one technology to see the 1:1 mapping and use the other.<br /><br />The primary downside with this approach was formats that were larger than perhaps necessary for HTML-specific use-cases.<br /><br />Eventually for microformats2 vocabularies, we adopted a subset approach, looking for web publishing use-cases for each feature, making h-card smaller than hCard, and h-event smaller than hCalendar.<br /><br /><br />Three: Success in a search engine was not enough, and sometimes attracted more bad actors than good. <a href=\"https://KevinMarks.com\">@KevinMarks.com</a>, myself, and others at Technorati built search engine indexing and use of rel-tag and hReview, which helped evolve their specifications. A few other small search engines indexed rel=tag markup, however none remain today. hReview was adopted by Google which led to it being heavily spammed.<br /><br />This pattern repeated itself with other microformats, and eventually we shifted from:<br />\u2192 of course search is the first obvious use-case<br />\u2192 search is one use-case among others<br />\u2192 we need primary use-cases outside of search for longterm ecosystem success<br />Which leads to the fourth observation.<br /><br /><br />Four: Publishing alone is not a use-case. There must be multiple consuming code use-cases (beyond search) for a microformat to succeed longterm.<br /><br />From individual features to whole microformats vocabularies, we learned that not only did there need to be sufficient content being published already, without microformats, that could benefit, but there needed to be good enough consuming code use-cases that benefited users (not just developers). The #<span class=\"p-category\">IndieWeb</span> community has been exceptionally helpful in both defining such use-cases and iterating on them with implementations.<br /><br />We still get questions of the form: What\u2019s the best way to mark this up?<br /><br />I used to very much believe that if you could mark something up more semantically, you should spend the time & effort to do so. This drove a lot of early experiments with markup, and did provide some eventual benefits, most notably when semantic HTML elements provided good hooks for accessibility tools such as screen readers.<br /><br />Now we know the answer to the question of \u201cHow should I mark-up this content?\u201d must be accompanied by specific use-cases for consuming code of that markup. <br /><br />If there is no consuming code use-case, it is not worth the time to add the mark-up (never mind the maintenance effort over time).<br /><br />Sometimes one single consuming code use-case is sufficient to justify the time & effort to add more semantic mark-up. If that markup helps screenreaders, then it\u2019s worth it. More often than not however, there must be multiple (again, beyond search) consuming code use-cases for it to be worth adding semantic markup, and certainly for developing new markup, whether microformats features or new microformats.<br /><br /><br />This focus on and repeated asking of questions like:<br />* What is the (consuming code) use-case? <br />* Or how does it benefit readers of this content?<br />has helped focus our modern microformats efforts on actual benefits to humans first, and machines second (if at all).<br /><br /><br />If you think of IndieWeb use-cases for existing or new microformats, come join us in the developers chat:<br />* <a href=\"https://chat.indieweb.org/dev\">https://chat.indieweb.org/dev</a><br /><br />If you think of other use-cases or want to chat about modern microformats methodologies in general, join us in the microformats chat:<br />* <a href=\"https://chat.indieweb.org/microformats\">https://chat.indieweb.org/microformats</a><br /><br /><br />This is day 32 of #<span class=\"p-category\">100DaysOfIndieWeb</span> #<span class=\"p-category\">100Days</span><br /><br />\u2190 Day 31: <a href=\"https://tantek.com/2023/044/t1/unified-sent-box-universal-outbox\">https://tantek.com/2023/044/t1/unified-sent-box-universal-outbox</a><br />\u2192 \ud83d\udd2e<br /><br /><br />Post glossary:<br /><br />h-card<br />\u00a0<a href=\"https://microformats.org/wiki/h-card\">https://microformats.org/wiki/h-card</a><br />h-entry<br />\u00a0<a href=\"https://microformats.org/wiki/h-entry\">https://microformats.org/wiki/h-entry</a><br />h-event<br />\u00a0<a href=\"https://microformats.org/wiki/h-event\">https://microformats.org/wiki/h-event</a><br />h-review<br />\u00a0<a href=\"https://microformats.org/wiki/h-review\">https://microformats.org/wiki/h-review</a><br />hAtom<br />\u00a0<a href=\"https://microformats.org/wiki/hatom\">https://microformats.org/wiki/hatom</a><br />hCalendar<br />\u00a0<a href=\"https://microformats.org/wiki/hcalendar\">https://microformats.org/wiki/hcalendar</a><br />hCard<br />\u00a0<a href=\"https://microformats.org/wiki/hcard\">https://microformats.org/wiki/hcard</a><br />hReview<br />\u00a0<a href=\"https://microformats.org/wiki/hreview\">https://microformats.org/wiki/hreview</a><br />rel-license<br />\u00a0<a href=\"https://microformats.org/wiki/rel-license\">https://microformats.org/wiki/rel-license</a><br />rel-tag<br />\u00a0<a href=\"https://microformats.org/wiki/rel-tag\">https://microformats.org/wiki/rel-tag</a><br />rel-values<br />\u00a0<a href=\"https://microformats.org/wiki/existing-rel-values\">https://microformats.org/wiki/existing-rel-values</a><br />XFN<br />\u00a0<a href=\"https://gmpg.org/xfn/\">https://gmpg.org/xfn/</a><br />XMDP<br />\u00a0<a href=\"http://gmpg.org/xmdp/description\">http://gmpg.org/xmdp/description</a><br />XOXO<br />\u00a0<a href=\"https://microformats.org/wiki/xoxo\">https://microformats.org/wiki/xoxo</a><br /><br /><br />Previously, previously, previously:<br />* <a href=\"https://tantek.com/2019/044/t1/15-years-ago-introduced-microformats\">https://tantek.com/2019/044/t1/15-years-ago-introduced-microformats</a><br />* <a href=\"https://tantek.com/2014/042/t2/ten-years-ago-introduced-microformats-etech\">https://tantek.com/2014/042/t2/ten-years-ago-introduced-microformats-etech</a><br />* <a href=\"https://tantek.com/2011/042/t2/years-ago-presented-microformats-etech\">https://tantek.com/2011/042/t2/years-ago-presented-microformats-etech</a><br />* <a href=\"https://twitter.com/t/status/701095802\">https://twitter.com/t/status/701095802</a><br /><br /><br />References:<br /><a href=\"http://tantek.com/#t5PQ1_ref-1\">\u00b9</a> <a href=\"https://tantek.com/presentations/2004etech/realworldsemanticspres.html\">https://tantek.com/presentations/2004etech/realworldsemanticspres.html</a><br /><a href=\"http://tantek.com/#t5PQ1_ref-2\">\u00b2</a> <a href=\"https://tantek.com/log/2004/02.html#d04t1311\">https://tantek.com/log/2004/02.html#d04t1311</a><br /><a href=\"http://tantek.com/#t5PQ1_ref-3\">\u00b3</a> <a href=\"https://gmpg.org/xfn/11#me\">https://gmpg.org/xfn/11#me</a><br /><a href=\"http://tantek.com/#t5PQ1_ref-4\">\u2074</a> <a href=\"https://docs.joinmastodon.org/user/profile/#verification\">https://docs.joinmastodon.org/user/profile/#verification</a><br /><a href=\"http://tantek.com/#t5PQ1_ref-5\">\u2075</a> <a href=\"https://hachyderm.io/@nova/109790530971147702\">https://hachyderm.io/@nova/109790530971147702</a><br /><a href=\"http://tantek.com/#t5PQ1_ref-6\">\u2076</a> <a href=\"https://tantek.com/2023/032/t1/years-relmeauth-replace-openid\">https://tantek.com/2023/032/t1/years-relmeauth-replace-openid</a><br /><a href=\"http://tantek.com/#t5PQ1_ref-7\">\u2077</a> <a href=\"https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors\">https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors</a><br /><a href=\"http://tantek.com/#t5PQ1_ref-8\">\u2078</a> <a href=\"http://microformats.org/wiki/events/2007-12-11-open-media-web\">http://microformats.org/wiki/events/2007-12-11-open-media-web</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "35210323",
"_source": "1",
"_is_read": false
}
