{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://jeremy.hu/thanking-my-rss-readers/",
    "content": {
        "html": "<p><strong>Thanking my RSS readers</strong></p><p>Found a cool message on Kev\u2019s blog about appreciating RSS readers, so I decided to add something similar to mine. This WordPress snippet displays a random welcome messages to all RSS readers.</p><p><a href=\"https://jeremy.hu/thanking-my-rss-readers/\">https://jeremy.hu/thanking-my-rss-readers/</a></p><p><a class=\"u-tag u-category\" href=\"https://jeremy.hu/tag/en/\">#EN</a> <a class=\"u-tag u-category\" href=\"https://jeremy.hu/tag/indieweb/\">#IndieWeb</a> <a class=\"u-tag u-category\" href=\"https://jeremy.hu/tag/plugin/\">#plugin</a> <a class=\"u-tag u-category\" href=\"https://jeremy.hu/tag/rss/\">#RSS</a> <a class=\"u-tag u-category\" href=\"https://jeremy.hu/tag/tutorial/\">#Tutorial</a> <a class=\"u-tag u-category\" href=\"https://jeremy.hu/tag/wordpress/\">#WordPress</a></p>",
        "text": "Thanking my RSS readers\n\nFound a cool message on Kev\u2019s blog about appreciating RSS readers, so I decided to add something similar to mine. This WordPress snippet displays a random welcome messages to all RSS readers.\n\nhttps://jeremy.hu/thanking-my-rss-readers/\n\n#EN #IndieWeb #plugin #RSS #Tutorial #WordPress"
    },
    "published": "2024-09-06T16:08:20+00:00",
    "photo": [
        "https://files.mastodon.social/cache/media_attachments/files/113/091/471/129/482/352/original/d85968af5ce7e532.png"
    ],
    "post-type": "photo",
    "_id": "42158181",
    "_source": "8007",
    "_is_read": false
}

Manton Reece www.manton.org

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://micro.blog/manton/avatar.jpg"
    },
    "url": "https://www.manton.org/2024/09/06/taking-a-short.html",
    "content": {
        "html": "<p>Taking a short break from Threads and Bluesky. Nothing against those services, but I started over-thinking the post length differences. I need to focus on work and blogging first. Because my blog natively uses ActivityPub, Mastodon folks will still see my posts.</p>",
        "text": "Taking a short break from Threads and Bluesky. Nothing against those services, but I started over-thinking the post length differences. I need to focus on work and blogging first. Because my blog natively uses ActivityPub, Mastodon folks will still see my posts."
    },
    "published": "2024-09-06T08:56:05-05:00",
    "post-type": "note",
    "_id": "42157032",
    "_source": "12",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://todon.eu/@alexture/113090997084266810",
    "content": {
        "html": "<p>static website with rss</p><p>WordPress is way too ambitious for a very simple website that lists cool blogs like blogroll.fr and I'd like to turn the current website into a static website, using ideally only HTML and CSS, or a tiny bit of something else if really needed.</p><p>The only thing that really worries me is that I would like to keep an RSS feed so that it's easy to follow when blogs are added (an</p><p><a href=\"https://alexsirac.com/static-website-with-rss/\"><span>https://</span><span>alexsirac.com/static-website-w</span><span>ith-rss/</span></a></p><p><a href=\"https://todon.eu/tags/en\">#<span>en</span></a> <a href=\"https://todon.eu/tags/HelpMe\">#<span>HelpMe</span></a> <a href=\"https://todon.eu/tags/indieWeb\">#<span>indieWeb</span></a> <a href=\"https://todon.eu/tags/WebDevelopment\">#<span>WebDevelopment</span></a></p>",
        "text": "static website with rss\n\nWordPress is way too ambitious for a very simple website that lists cool blogs like blogroll.fr and I'd like to turn the current website into a static website, using ideally only HTML and CSS, or a tiny bit of something else if really needed.\n\nThe only thing that really worries me is that I would like to keep an RSS feed so that it's easy to follow when blogs are added (an\n\nhttps://alexsirac.com/static-website-with-rss/\n\n#en #HelpMe #indieWeb #WebDevelopment"
    },
    "published": "2024-09-06T14:07:49+00:00",
    "post-type": "note",
    "_id": "42156803",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://mastodon.social/@john_fisherman/113089033853761176",
    "content": {
        "html": "<p>Hosting your own content is the core of the <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a>, says <span class=\"h-card\"><a class=\"u-url\" href=\"https://shellsharks.social/@shellsharks\">@<span>shellsharks</span></a></span> </p><p>\"f you are reading this, or you have a personal site, you are already part of it. Full stop. You don\u2019t need to be shy. You have things to say and people WANT to listen, they want to read, they want to connect. You don\u2019t have to be an \u201cinfluencer\u201d or have a big following. Your writing doesn\u2019t need to be AMAZING. You don\u2019t need to write to an audience. Write for yourself. Then share it. \"</p><p><a href=\"https://shellsharks.com/notes/2024/05/14/one-of-us\"><span>https://</span><span>shellsharks.com/notes/2024/05/</span><span>14/one-of-us</span></a></p>\n<a class=\"u-mention\" href=\"https://shellsharks.social/@shellsharks\"></a>",
        "text": "Hosting your own content is the core of the #indieweb, says @shellsharks \n\n\"f you are reading this, or you have a personal site, you are already part of it. Full stop. You don\u2019t need to be shy. You have things to say and people WANT to listen, they want to read, they want to connect. You don\u2019t have to be an \u201cinfluencer\u201d or have a big following. Your writing doesn\u2019t need to be AMAZING. You don\u2019t need to write to an audience. Write for yourself. Then share it. \"\n\nhttps://shellsharks.com/notes/2024/05/14/one-of-us"
    },
    "published": "2024-09-06T05:48:32+00:00",
    "post-type": "note",
    "_id": "42152969",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://mastodon.social/@readbeanicecream/113087857356232594",
    "content": {
        "html": "<p>Brasil's Twitter/X ban shows once more an over centralized system</p><p><a href=\"https://www.locked.de/brasils-twitter-x-ban-shows-once-more-an-over-centralized-system/\"><span>https://www.</span><span>locked.de/brasils-twitter-x-ba</span><span>n-shows-once-more-an-over-centralized-system/</span></a></p><p><a href=\"https://mastodon.social/tags/tech\">#<span>tech</span></a> <a href=\"https://mastodon.social/tags/technology\">#<span>technology</span></a> <a href=\"https://mastodon.social/tags/socialmedia\">#<span>socialmedia</span></a> <a href=\"https://mastodon.social/tags/x\">#<span>x</span></a> <a href=\"https://mastodon.social/tags/xitter\">#<span>xitter</span></a> <a href=\"https://mastodon.social/tags/twitter\">#<span>twitter</span></a> <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodon.social/tags/fediverse\">#<span>fediverse</span></a></p>",
        "text": "Brasil's Twitter/X ban shows once more an over centralized system\n\nhttps://www.locked.de/brasils-twitter-x-ban-shows-once-more-an-over-centralized-system/\n\n#tech #technology #socialmedia #x #xitter #twitter #indieweb #fediverse"
    },
    "published": "2024-09-06T00:49:21+00:00",
    "post-type": "note",
    "_id": "42151571",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://rrier.fr/@pc/statuses/01J7257PZGKET1GWDES4J9HSJ9",
    "content": {
        "html": "<p>Posted <a href=\"https://nothing.pcarrier.com/posts/fediverse-bust/\">Owning your Fediverse identity falls short</a>. Would love to hear your thoughts.</p><p><a href=\"https://rrier.fr/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://rrier.fr/tags/fediverse\">#<span>fediverse</span></a></p>",
        "text": "Posted Owning your Fediverse identity falls short. Would love to hear your thoughts.\n\n#indieweb #fediverse"
    },
    "published": "2024-09-05T22:35:15+00:00",
    "post-type": "note",
    "_id": "42150880",
    "_source": "8007",
    "_is_read": false
}

Fediverse is a bust on tiny instances

{
    "type": "entry",
    "author": {
        "name": "A blog about nothing",
        "url": "https://nothing.pcarrier.com",
        "photo": null
    },
    "url": "https://nothing.pcarrier.com/posts/fediverse-bust/",
    "name": "Fediverse is a bust on tiny instances",
    "content": {
        "html": "<p>I enjoy using my own domains \u2014 though I own a few too many! One of them, <code>rrier.fr</code> was originally purchased solely so I could use <a href=\"mailto:pc@rrier.fr\">pc@rrier.fr</a> as my E-mail address.</p>\n<p>Naturally, I wanted to also be known as <a href=\"https://rrier.fr/@pc\">@pc@rrier.fr</a> on the fediverse, as part of owning my online identity. Unfortunately, this turned out more challenging that I expected. Here are a few approaches I tried and what I learned along the way.</p>\n<h2>Forwarding WebFinger</h2>\n<p>My first approach, documented during <a href=\"https://xmit.dev/posts/pcarrier-com/\">my migration to xmit.co</a>, was to set up a WebFinger redirect. <a href=\"https://rrier.fr/.well-known/webfinger\">https://rrier.fr/.well-known/webfinger</a> redirected to <a href=\"https://mastodon.social/.well-known/webfinger?resource=acct%3Apcarrier%40mastodon.social\">https://mastodon.social/.well-known/webfinger?resource=acct%3Apcarrier%40mastodon.social</a>, the WebFinger URL for <a href=\"https://mastodon.social/@pcarrier\">@pcarrier@mastodon.social</a>.</p>\n<p>This let people search for <code>@pc@rrier.fr</code> and find an account. Unfortunately, that indirection would be resolved right there and then: they would then see and follow the <a href=\"https://mastodon.social\">mastodon.social</a> account. I couldn't move providers without breakage.</p>\n<p>I wanted more control over where my content is hosted and stored authoritatively. Onto what seemed like the natural solution.</p>\n<h2>Running <a href=\"https://joinmastodon.org/\">Mastodon</a></h2>\n<p>In my opinion, for a single customer, a server requires too much setup and maintenance work, and too many resources. I gave up a few steps into an installation when I realized the amount of memory my VPS would probably need, so I can't say much more.</p>\n<p>I looked around, and found what I think is a better solution for my needs:</p>\n<h2>Running <a href=\"https://gotosocial.org/\">GoToSocial</a></h2>\n<p>Setup was a breeze. Everything is lightweight and fast. I have minor complaints, notably lack of edit capability (already on the <a href=\"https://github.com/superseriousbusiness/gotosocial/blob/main/ROADMAP.md\">roadmap</a>), but it's a fantastic piece of software.</p>\n<p>It does, however, suffer from what appear to be limitations inherent to the design of the fediverse:</p>\n<ul><li>\n<p>My server is federated with over 2000 other instances, but I don't see their content when looking up or following a hashtag. My server only finds stuff that already appeared in the timeline of my lone user\u2026 Makes following hashtags pointless, something that I found super valuable when I was on a big instance.</p>\n</li>\n<li>\n<p>I can't boost or reply to toots of people I don't already follow, unless they were boosted by the accounts my server follows\u2026 Following them doesn't backfill their history on my server, so the existing toot remains out of reach.</p>\n</li>\n</ul><p>I'd love to learn that those issues can be addressed without protocol changes, or that such protocol changes are underway. In the meantime, I've learnt to live with those grievances.</p>",
        "text": "I enjoy using my own domains \u2014 though I own a few too many! One of them, rrier.fr was originally purchased solely so I could use pc@rrier.fr as my E-mail address.\nNaturally, I wanted to also be known as @pc@rrier.fr on the fediverse, as part of owning my online identity. Unfortunately, this turned out more challenging that I expected. Here are a few approaches I tried and what I learned along the way.\nForwarding WebFinger\nMy first approach, documented during my migration to xmit.co, was to set up a WebFinger redirect. https://rrier.fr/.well-known/webfinger redirected to https://mastodon.social/.well-known/webfinger?resource=acct%3Apcarrier%40mastodon.social, the WebFinger URL for @pcarrier@mastodon.social.\nThis let people search for @pc@rrier.fr and find an account. Unfortunately, that indirection would be resolved right there and then: they would then see and follow the mastodon.social account. I couldn't move providers without breakage.\nI wanted more control over where my content is hosted and stored authoritatively. Onto what seemed like the natural solution.\nRunning Mastodon\nIn my opinion, for a single customer, a server requires too much setup and maintenance work, and too many resources. I gave up a few steps into an installation when I realized the amount of memory my VPS would probably need, so I can't say much more.\nI looked around, and found what I think is a better solution for my needs:\nRunning GoToSocial\nSetup was a breeze. Everything is lightweight and fast. I have minor complaints, notably lack of edit capability (already on the roadmap), but it's a fantastic piece of software.\nIt does, however, suffer from what appear to be limitations inherent to the design of the fediverse:\n\nMy server is federated with over 2000 other instances, but I don't see their content when looking up or following a hashtag. My server only finds stuff that already appeared in the timeline of my lone user\u2026 Makes following hashtags pointless, something that I found super valuable when I was on a big instance.\n\n\nI can't boost or reply to toots of people I don't already follow, unless they were boosted by the accounts my server follows\u2026 Following them doesn't backfill their history on my server, so the existing toot remains out of reach.\n\nI'd love to learn that those issues can be addressed without protocol changes, or that such protocol changes are underway. In the meantime, I've learnt to live with those grievances."
    },
    "published": "2024-09-06T00:00:00.000Z",
    "post-type": "article",
    "_id": "42150728",
    "_source": "8335",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://mastodon.social/@rodmoi/113086106489592326",
    "content": {
        "html": "<p>If even long-time production-tested complex systems frequently fail, why do some people still maintain the illusion that a newly developed complex system, with each component created by a different developer, will function flawlessly when its parts assemble in production for the first time within the expected deadline?</p><p><a href=\"https://rm-o.dev/notes/complex-systems/\"><span>https://</span><span>rm-o.dev/notes/complex-systems</span><span>/</span></a></p><p><a href=\"https://mastodon.social/tags/agile\">#<span>agile</span></a> <a href=\"https://mastodon.social/tags/complexity\">#<span>complexity</span></a> <a href=\"https://mastodon.social/tags/development\">#<span>development</span></a> <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodon.social/tags/note\">#<span>note</span></a> <a href=\"https://mastodon.social/tags/system\">#<span>system</span></a></p>",
        "text": "If even long-time production-tested complex systems frequently fail, why do some people still maintain the illusion that a newly developed complex system, with each component created by a different developer, will function flawlessly when its parts assemble in production for the first time within the expected deadline?\n\nhttps://rm-o.dev/notes/complex-systems/\n\n#agile #complexity #development #indieweb #note #system"
    },
    "published": "2024-09-05T17:24:04+00:00",
    "post-type": "note",
    "_id": "42148039",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://corteximplant.com/@Bit_form/113085722344958668",
    "content": {
        "html": "<p>Thinking again on learning enough HTML to pass making a neocities site has been pretty rewarding so far, but I cannot stress enough that I have to be in \"focus and problem solving\" mode, which is sometimes not easy to be in, or stay in. (ADHD WOOOO)</p><p><a href=\"https://www.w3schools.com/html\"><span>https://www.</span><span>w3schools.com/html</span><span></span></a><br />, and the neocities reddit have been great wells of knowledge for things that I know are simple, but still struggling with so far. </p><p>That being said. I fixed all the links from opening new tabs, THEN I set up a comment for myself in the future so I don't make the same mistake!</p><p>I'm liking this a lot so far, and even if I did have to rebuild my artist website, it suddenly doesn't feel so out of reach....</p><p><a href=\"https://corteximplant.com/tags/HonestSelfHostingMeta\">#<span>HonestSelfHostingMeta</span></a>  <a href=\"https://corteximplant.com/tags/HTML\">#<span>HTML</span></a> <a href=\"https://corteximplant.com/tags/CodeNewbie\">#<span>CodeNewbie</span></a> <a href=\"https://corteximplant.com/tags/neocities\">#<span>neocities</span></a> <a href=\"https://corteximplant.com/tags/indieweb\">#<span>indieweb</span></a></p>",
        "text": "Thinking again on learning enough HTML to pass making a neocities site has been pretty rewarding so far, but I cannot stress enough that I have to be in \"focus and problem solving\" mode, which is sometimes not easy to be in, or stay in. (ADHD WOOOO)\n\nhttps://www.w3schools.com/html\n, and the neocities reddit have been great wells of knowledge for things that I know are simple, but still struggling with so far. \n\nThat being said. I fixed all the links from opening new tabs, THEN I set up a comment for myself in the future so I don't make the same mistake!\n\nI'm liking this a lot so far, and even if I did have to rebuild my artist website, it suddenly doesn't feel so out of reach....\n\n#HonestSelfHostingMeta  #HTML #CodeNewbie #neocities #indieweb"
    },
    "published": "2024-09-05T15:46:23+00:00",
    "post-type": "note",
    "_id": "42147105",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://mastodon.online/@mauricerenck/113085583161795041",
    "content": {
        "html": "<p>Bei Heise-Online (und in der c\u2019t) kann man diesen sch\u00f6nen Artikel \u00fcber Kirby und das IndieWeb lesen (heise+). Jo Bager beschreibt in der Reihe, wie man Kirby Schritt f\u00fcr Schritt ans IndieWeb anschlie\u00dft. Im aktuellen Teil geht's um die Installation von Kirby und meinem Komments Plugin. Sp\u00e4ter soll es dann mit dem IndieConnector weitergehen.<br />Freut mich sehr!</p><p><a href=\"https://www.heise.de/select/ct/2024/19/2420713435195546878\"><span>https://www.</span><span>heise.de/select/ct/2024/19/242</span><span>0713435195546878</span></a></p><p><a href=\"https://mastodon.online/tags/kirby\">#<span>kirby</span></a> <a href=\"https://mastodon.online/tags/kirbycms\">#<span>kirbycms</span></a> <a href=\"https://mastodon.online/tags/komments\">#<span>komments</span></a> <a href=\"https://mastodon.online/tags/indieconnector\">#<span>indieconnector</span></a> <a href=\"https://mastodon.online/tags/indieweb\">#<span>indieweb</span></a></p>",
        "text": "Bei Heise-Online (und in der c\u2019t) kann man diesen sch\u00f6nen Artikel \u00fcber Kirby und das IndieWeb lesen (heise+). Jo Bager beschreibt in der Reihe, wie man Kirby Schritt f\u00fcr Schritt ans IndieWeb anschlie\u00dft. Im aktuellen Teil geht's um die Installation von Kirby und meinem Komments Plugin. Sp\u00e4ter soll es dann mit dem IndieConnector weitergehen.\nFreut mich sehr!\n\nhttps://www.heise.de/select/ct/2024/19/2420713435195546878\n\n#kirby #kirbycms #komments #indieconnector #indieweb"
    },
    "published": "2024-09-05T15:10:59+00:00",
    "post-type": "note",
    "_id": "42146453",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://indieweb.social/@barrd/113085245453838353",
    "content": {
        "html": "<p>BPJ: Orchard Inn Blues Night</p><p>Brissle Proper Job series issue #5 Orchard Inn Blues Night, a venue on Spike Island at a 190 year old pub with great music on a Monday night. \u2026</p><p><a href=\"https://barrd.net/bpj-orchard-inn-blues-night/\"><span>https://</span><span>barrd.net/bpj-orchard-inn-blue</span><span>s-night/</span></a></p><p><a href=\"https://indieweb.social/tags/BrissleProperJob\">#<span>BrissleProperJob</span></a> <a href=\"https://indieweb.social/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
        "text": "BPJ: Orchard Inn Blues Night\n\nBrissle Proper Job series issue #5 Orchard Inn Blues Night, a venue on Spike Island at a 190 year old pub with great music on a Monday night. \u2026\n\nhttps://barrd.net/bpj-orchard-inn-blues-night/\n\n#BrissleProperJob #IndieWeb"
    },
    "published": "2024-09-05T13:45:06+00:00",
    "post-type": "note",
    "_id": "42145750",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://aus.social/@AuntyRed/113084610539834655",
    "content": {
        "html": "<p>I'm talking about Aliens! But why aren't they talking back? </p><p>Read my blog summarizing a really cool hypothesis to the Fermi Paradox that was shared on the ArXiv last month.</p><p><a href=\"https://caffeineandlasers.neocities.org/blogs/Aliens\"><span>https://</span><span>caffeineandlasers.neocities.or</span><span>g/blogs/Aliens</span></a></p><p><a href=\"https://aus.social/tags/Astrodon\">#<span>Astrodon</span></a> <a href=\"https://aus.social/tags/astronomy\">#<span>astronomy</span></a> <a href=\"https://aus.social/tags/scifi\">#<span>scifi</span></a> <a href=\"https://aus.social/tags/alien\">#<span>alien</span></a> <a href=\"https://aus.social/tags/SmallWeb\">#<span>SmallWeb</span></a> <a href=\"https://aus.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://aus.social/tags/blog\">#<span>blog</span></a></p>",
        "text": "I'm talking about Aliens! But why aren't they talking back? \n\nRead my blog summarizing a really cool hypothesis to the Fermi Paradox that was shared on the ArXiv last month.\n\nhttps://caffeineandlasers.neocities.org/blogs/Aliens\n\n#Astrodon #astronomy #scifi #alien #SmallWeb #IndieWeb #blog"
    },
    "published": "2024-09-05T11:03:38+00:00",
    "post-type": "note",
    "_id": "42144021",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://tweesecake.social/@weirdwriter/113083471703642306",
    "content": {
        "html": "<p>If you liked Trunk Writing my feed URL is <a href=\"https://robertkingett.com/feed/\"><span>https://</span><span>robertkingett.com/feed/</span><span></span></a> <a href=\"https://tweesecake.social/tags/RSS\">#<span>RSS</span></a> <a href=\"https://tweesecake.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://tweesecake.social/tags/SmallWeb\">#<span>SmallWeb</span></a></p>",
        "text": "If you liked Trunk Writing my feed URL is https://robertkingett.com/feed/ #RSS #IndieWeb #SmallWeb"
    },
    "published": "2024-09-05T06:14:01+00:00",
    "post-type": "note",
    "_id": "42142107",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://botsin.space/@thzinc/113083156679968064",
    "content": {
        "html": "<p>I made a neat image annotation widget for my blog using OpenSeadragon and Annotorious: <a href=\"https://thzinc.com/2024/09/04/a-bike-tool-roll-made-from-a-canvas-bag.html\"><span>https://</span><span>thzinc.com/2024/09/04/a-bike-t</span><span>ool-roll-made-from-a-canvas-bag.html</span></a></p><p>I tried to ensure this was still usable with a screen reader\u2013I think I did okay?</p><p><a href=\"https://botsin.space/tags/maker\">#<span>maker</span></a> <a href=\"https://botsin.space/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://botsin.space/tags/a11y\">#<span>a11y</span></a></p>",
        "text": "I made a neat image annotation widget for my blog using OpenSeadragon and Annotorious: https://thzinc.com/2024/09/04/a-bike-tool-roll-made-from-a-canvas-bag.html\n\nI tried to ensure this was still usable with a screen reader\u2013I think I did okay?\n\n#maker #indieweb #a11y"
    },
    "published": "2024-09-05T04:53:54+00:00",
    "post-type": "note",
    "_id": "42141619",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://mastodon.social/@RyanParsley/113082555966252676",
    "content": {
        "html": "<p>If I link to my own post that has webmentions wired up like <a href=\"https://ryanparsley.com/note/webmentions/\"><span>https://</span><span>ryanparsley.com/note/webmentio</span><span>ns/</span></a>, does that show up in my webmention list? I'm still trying to wrap my head around how this works. <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
        "text": "If I link to my own post that has webmentions wired up like https://ryanparsley.com/note/webmentions/, does that show up in my webmention list? I'm still trying to wrap my head around how this works. #IndieWeb"
    },
    "published": "2024-09-05T02:21:08+00:00",
    "post-type": "note",
    "_id": "42140837",
    "_source": "8007",
    "_is_read": false
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2024-09-01 14:51-0700",
    "url": "http://tantek.com/2024/245/t1/read-write-suggest-edit-update-web",
    "category": [
        "IndieWebCamp",
        "Mastodon",
        "ActivityPub",
        "IndieWeb",
        "readWriteWeb",
        "editableWeb",
        "suggestEdit",
        "acceptEdit",
        "100PostsOfIndieWeb",
        "100Posts"
    ],
    "content": {
        "text": "\u270f\ufe0f I want the Read Write Suggest-Edit Accept-Edit Update Web.\n\nThe consumer Infinite Scroll Web leaves us feeling empty.\n\nToo few of us participate in the Read Write Web, whether with personal sites or Wikipedia.\n\nA week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos\u00b9, I noticed a few errors, typos or miscaptures, and pointed them out in-person.\n\nKevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon\u2019s post editing feature and its support of #ActivityPub Updates. But this shouldn\u2019t require being in the same room, whether IRL or chat.\n\nWe should be able to suggest edits to each other\u2019s posts, as easily as we can reply and add a comment.\n\n13 years ago I wrote\u00b2:\n\n\u00a0\u201cThe Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.\u201d\n\nNow I want the Read Write Suggest-Edit Accept-Edit Update Web.\n\nThe \u21aa Reply button is fairly ubiquitous in modern post user interfaces (UIs).\n\nWhy not also a \u270f\ufe0f Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid \"performative\" suggested edits.\n\nIf the author\u2019s posts provide revision histories, when a suggested edit is accepted, a post\u2019s history could show the contributor of the edit.\n\nInstead of asking Kevin in-person, what if I could have posted special \"Suggested Edit\" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?\n\nTo enable such UIs and interactions across servers and implementations, we may need a new type of response\u00b3, perhaps with a special property (or more) to convey the edits being suggested.\n\nThere is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:\n* https://indieweb.org/edit\n\nOur interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.\n\nFor now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:\n\n\u270f\ufe0f Suggest Edit\n\nand link it to an edit URL for the static file for the post.\n\nI don\u2019t use GitHub static files myself for posts, but here\u2019s an example of such an edit link for one of my projects:\n\nhttps://tantek.com/github/cassis/edit/main/README.md\n\nThis will start the process of creating a \u201cpull request\u201d, GitHub\u2019s jargon\u2074 for a \u201csuggested edit\u201d.\n\nAfter completing GitHub\u2019s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said \u201cpull request\u201d, it\u2019ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub\u2019s jargon-filled ceremonies to \u201cMerge\u201d or \u201cSquash & Merge\u201d, \u201cDelete fork\u201d, etc. to accept the edit.\n\nIt\u2019s an awkward interaction\u2075, however useful for at least prototyping a \u270f\ufe0f Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.\n\nWe can start with the shortest path to getting something working, then learn, iterate, improve, repeat.\n\n#readWriteWeb #editableWeb #suggestEdit #acceptEdit\n\nReferences:\n\n\u00b9 https://indieweb.social/@kevinmarks/113025295600067213\n\u00b2 https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11\n\u00b3 https://indieweb.org/responses\n\u2074 The phrase \u201cpull request\u201d was derived from the git command: \u201cgit request-pull\u201d according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/\n\u2075 \u201cedits\u201d in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to \u201cEdit\u201d and \u201cSave\u201d. We should aspire to Wikipedia\u2019s simplicity, not GitHub\u2019s ceremonies.\n\nThis is post 20 of #100PostsOfIndieWeb. #100Posts\n\n\u2190 https://tantek.com/2024/242/t1/indiewebcamp-portland\n\u2192 https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed",
        "html": "\u270f\ufe0f I want the Read Write Suggest-Edit Accept-Edit Update Web.<br /><br />The consumer Infinite Scroll Web leaves us feeling empty.<br /><br />Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.<br /><br />A week ago when we wrapped up #<span class=\"p-category\">IndieWebCamp</span> Portland and I was reading Kevin Marks (<a href=\"https://indieweb.social/@kevinmarks\">@kevinmarks@indieweb.social</a>) live-tooting of the demos<a href=\"http://tantek.com/#t5Yn1_note-1\">\u00b9</a>, I noticed a few errors, typos or miscaptures, and pointed them out in-person.<br /><br />Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #<span class=\"p-category\">Mastodon</span>\u2019s post editing feature and its support of #<span class=\"p-category\">ActivityPub</span> Updates. But this shouldn\u2019t require being in the same room, whether IRL or chat.<br /><br />We should be able to suggest edits to each other\u2019s posts, as easily as we can reply and add a comment.<br /><br />13 years ago I wrote<a href=\"http://tantek.com/#t5Yn1_note-2\">\u00b2</a>:<br /><br />\u00a0\u201cThe Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.\u201d<br /><br />Now I want the Read Write Suggest-Edit Accept-Edit Update Web.<br /><br />The \u21aa Reply button is fairly ubiquitous in modern post user interfaces (UIs).<br /><br />Why not also a \u270f\ufe0f Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid \"performative\" suggested edits.<br /><br />If the author\u2019s posts provide revision histories, when a suggested edit is accepted, a post\u2019s history could show the contributor of the edit.<br /><br />Instead of asking Kevin in-person, what if I could have posted special \"Suggested Edit\" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?<br /><br />To enable such UIs and interactions across servers and implementations, we may need a new type of response<a href=\"http://tantek.com/#t5Yn1_note-3\">\u00b3</a>, perhaps with a special property (or more) to convey the edits being suggested.<br /><br />There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #<span class=\"p-category\">IndieWeb</span> wiki:<br />* <a href=\"https://indieweb.org/edit\">https://indieweb.org/edit</a><br /><br />Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.<br /><br />For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:<br /><br />\u270f\ufe0f Suggest Edit<br /><br />and link it to an edit URL for the static file for the post.<br /><br />I don\u2019t use GitHub static files myself for posts, but here\u2019s an example of such an edit link for one of my projects:<br /><br /><a href=\"https://tantek.com/github/cassis/edit/main/README.md\">https://tantek.com/github/cassis/edit/main/README.md</a><br /><br />This will start the process of creating a \u201cpull request\u201d, GitHub\u2019s jargon<a href=\"http://tantek.com/#t5Yn1_note-4\">\u2074</a> for a \u201csuggested edit\u201d.<br /><br />After completing GitHub\u2019s ceremony of entering multiple text fields (summary &amp; description), and multiple clicks to create said \u201cpull request\u201d, it\u2019ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub\u2019s jargon-filled ceremonies to \u201cMerge\u201d or \u201cSquash &amp; Merge\u201d, \u201cDelete fork\u201d, etc. to accept the edit.<br /><br />It\u2019s an awkward interaction<a href=\"http://tantek.com/#t5Yn1_note-5\">\u2075</a>, however useful for at least prototyping a \u270f\ufe0f Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.<br /><br />We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.<br /><br />#<span class=\"p-category\">readWriteWeb</span> #<span class=\"p-category\">editableWeb</span> #<span class=\"p-category\">suggestEdit</span> #<span class=\"p-category\">acceptEdit</span><br /><br />References:<br /><br /><a href=\"http://tantek.com/#t5Yn1_ref-1\">\u00b9</a> <a href=\"https://indieweb.social/@kevinmarks/113025295600067213\">https://indieweb.social/@kevinmarks/113025295600067213</a><br /><a href=\"http://tantek.com/#t5Yn1_ref-2\">\u00b2</a> <a href=\"https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11\">https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11</a><br /><a href=\"http://tantek.com/#t5Yn1_ref-3\">\u00b3</a> <a href=\"https://indieweb.org/responses\">https://indieweb.org/responses</a><br /><a href=\"http://tantek.com/#t5Yn1_ref-4\">\u2074</a> The phrase \u201cpull request\u201d was derived from the git command: \u201cgit request-pull\u201d according to <a href=\"https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/\">https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/</a><br /><a href=\"http://tantek.com/#t5Yn1_ref-5\">\u2075</a> \u201cedits\u201d in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to \u201cEdit\u201d and \u201cSave\u201d. We should aspire to Wikipedia\u2019s simplicity, not GitHub\u2019s ceremonies.<br /><br />This is post 20 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span><br /><br />\u2190 <a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland\">https://tantek.com/2024/242/t1/indiewebcamp-portland</a><br />\u2192 <a href=\"https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed\">https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed</a>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "https://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "note",
    "_id": "42140618",
    "_source": "1",
    "_is_read": false
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2024-08-29 21:09-0700",
    "url": "http://tantek.com/2024/242/t1/indiewebcamp-portland-10",
    "category": [
        "IndieWebCamp",
        "IndieWeb",
        "100PostsOfIndieWeb",
        "100Posts",
        "2024_238"
    ],
    "content": {
        "text": "Had a great time at IndieWebCamp Portland 2024 this past Sunday \u2014 our 10th IndieWebCamp in Portland!\n\nhttps://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k\n\nBeing a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions.\n\nNearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve.\n* https://indieweb.org/2024/Portland/Intros\n\nThere were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.\n\nWe wrapped up with our usual Create Day\u00b9 Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!\n* https://indieweb.org/2024/Portland/Demos\n\nGroup photo and lots more about IndieWebCamp Portland 2024 at the event\u2019s wiki page:\n* https://indieweb.org/2024/Portland\n\nThanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos.\n\nThe experience definitely raised our hopes and confidence for returning to Portland in 2025.\u00b2\n\n\nReferences:\n\n\u00b9 https://indieweb.org/Create_Day\n\u00b2 https://indieweb.org/Planning#Portland\n\nThis is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238\n\n\u2190 https://tantek.com/2024/238/t3/indiewebcamp-auto-linking\n\u2192 https://tantek.com/2024/245/t1/read-write-suggest-edit-web",
        "html": "Had a great time at IndieWebCamp Portland 2024 this past Sunday \u2014 our 10th IndieWebCamp in Portland!<br /><br /><a href=\"https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k\">https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k</a><br /><br />Being a one day #<span class=\"p-category\">IndieWebCamp</span>, we focused more on making, hacking, and creating, than on formal discussion sessions.<br /><br />Nearly everyone gave a brief personal site intro with a summary of how they use their #<span class=\"p-category\">IndieWeb</span> site and what they would like to add, remove, or improve.<br />* <a href=\"https://indieweb.org/2024/Portland/Intros\">https://indieweb.org/2024/Portland/Intros</a><br /><br />There were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.<br /><br />We wrapped up with our usual Create Day<a href=\"http://tantek.com/#t5Yj1_note-1\">\u00b9</a> Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!<br />* <a href=\"https://indieweb.org/2024/Portland/Demos\">https://indieweb.org/2024/Portland/Demos</a><br /><br />Group photo and lots more about IndieWebCamp Portland 2024 at the event\u2019s wiki page:<br />* <a href=\"https://indieweb.org/2024/Portland\">https://indieweb.org/2024/Portland</a><br /><br />Thanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (<a href=\"https://martymcgui.re\">@martymcgui.re</a>) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (<a href=\"https://indieweb.social/@kevinmarks\">@kevinmarks@indieweb.social</a> <a href=\"https://xoxo.zone/@kevinmarks\">@kevinmarks@xoxo.zone</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/kevinmarks\">@kevinmarks</a>) for the IndieWebCamp live-tooting, and Ryan Barrett (<a href=\"https://snarfed.org\">@snarfed.org</a>) for amazing breakfast pastries from Dos Hermanos.<br /><br />The experience definitely raised our hopes and confidence for returning to Portland in 2025.<a href=\"http://tantek.com/#t5Yj1_note-2\">\u00b2</a><br /><br /><br />References:<br /><br /><a href=\"http://tantek.com/#t5Yj1_ref-1\">\u00b9</a> <a href=\"https://indieweb.org/Create_Day\">https://indieweb.org/Create_Day</a><br /><a href=\"http://tantek.com/#t5Yj1_ref-2\">\u00b2</a> <a href=\"https://indieweb.org/Planning#Portland\">https://indieweb.org/Planning#Portland</a><br /><br />This is post 19 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span> #<span class=\"p-category\">2024_238</span><br /><br />\u2190 <a href=\"https://tantek.com/2024/238/t3/indiewebcamp-auto-linking\">https://tantek.com/2024/238/t3/indiewebcamp-auto-linking</a><br />\u2192 <a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-web\">https://tantek.com/2024/245/t1/read-write-suggest-edit-web</a>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "https://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "note",
    "_id": "42140619",
    "_source": "1",
    "_is_read": false
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2024-08-25 16:00-0700",
    "url": "http://tantek.com/2024/238/t3/indiewebcamp-auto-link",
    "category": [
        "IndieWebCamp",
        "IndieWeb",
        "autoLink",
        "hashtag",
        "hashtags",
        "footnote",
        "footnotes",
        "100PostsOfIndieWeb",
        "100Posts"
    ],
    "content": {
        "text": "Nice #IndieWebCamp discussion session with Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) on the topic of auto-linking\u00b9.\n\nI\u2019ve implemented an auto_link function\u00b2 that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).\n\nMuch of it is based on what I\u2019ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.\n\nIt may be time for me to write-up an auto-link specification based on the algorithms I\u2019ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.\n\nI have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.\n\n* URLs, @-s, and @-@-s\n* # hashtags\n* ^ footnotes\n\n#IndieWeb #autoLink #hashtag #hashtags #footnote #footnotes\n\nPreviously, previously, previously:\n\n* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases\n* https://tantek.com/2023/100/t1/auto-linked-hashtags-federated\n* https://tantek.com/2023/043/t1/footnotes-unicode-links\n* https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo\n\n\nReferences:\n\n\u00b9 https://indieweb.org/autolink\n\u00b2 https://github.com/tantek/cassis/blob/main/cassis.js\n\n\nThis is post 18 of #100PostsOfIndieWeb. #100Posts\n\n\u2190 https://tantek.com/2024/238/t1/indiewebcamp-portland\n\u2192 https://tantek.com/2024/242/t1/indiewebcamp-portland",
        "html": "Nice #<span class=\"p-category\">IndieWebCamp</span> discussion session with Kevin Marks (<a href=\"https://indieweb.social/@kevinmarks\">@kevinmarks@indieweb.social</a> <a href=\"https://xoxo.zone/@kevinmarks\">@kevinmarks@xoxo.zone</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/kevinmarks\">@kevinmarks</a>) on the topic of auto-linking<a href=\"http://tantek.com/#t5Yf3_note-1\">\u00b9</a>.<br /><br />I\u2019ve implemented an auto_link function<a href=\"http://tantek.com/#t5Yf3_note-2\">\u00b2</a> that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).<br /><br />Much of it is based on what I\u2019ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.<br /><br />It may be time for me to write-up an auto-link specification based on the algorithms I\u2019ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.<br /><br />I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.<br /><br />* URLs, @-s, and @-@-s<br />* # hashtags<br />* ^ footnotes<br /><br />#<span class=\"p-category\">IndieWeb</span> #<span class=\"p-category\">autoLink</span> #<span class=\"p-category\">hashtag</span> #<span class=\"p-category\">hashtags</span> #<span class=\"p-category\">footnote</span> #<span class=\"p-category\">footnotes</span><br /><br />Previously, previously, previously:<br /><br />* <a href=\"https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases\">https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases</a><br />* <a href=\"https://tantek.com/2023/100/t1/auto-linked-hashtags-federated\">https://tantek.com/2023/100/t1/auto-linked-hashtags-federated</a><br />* <a href=\"https://tantek.com/2023/043/t1/footnotes-unicode-links\">https://tantek.com/2023/043/t1/footnotes-unicode-links</a><br />* <a href=\"https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo\">https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo</a><br /><br /><br />References:<br /><br /><a href=\"http://tantek.com/#t5Yf3_ref-1\">\u00b9</a> <a href=\"https://indieweb.org/autolink\">https://indieweb.org/autolink</a><br /><a href=\"http://tantek.com/#t5Yf3_ref-2\">\u00b2</a> <a href=\"https://github.com/tantek/cassis/blob/main/cassis.js\">https://github.com/tantek/cassis/blob/main/cassis.js</a><br /><br /><br />This is post 18 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span><br /><br />\u2190 <a href=\"https://tantek.com/2024/238/t1/indiewebcamp-portland\">https://tantek.com/2024/238/t1/indiewebcamp-portland</a><br />\u2192 <a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland\">https://tantek.com/2024/242/t1/indiewebcamp-portland</a>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "https://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "note",
    "_id": "42140620",
    "_source": "1",
    "_is_read": false
}

Vika fireburn.ru

Bowl for Kittybox 1.0

{
    "type": "entry",
    "published": "2024-09-04T22:46:37.102817764+03:00",
    "url": "https://fireburn.ru/posts/byypbyN",
    "category": [
        "Bowl",
        "Kittybox",
        "IndieWeb",
        "Micropub",
        "https://news.indieweb.org/en"
    ],
    "name": "Bowl for Kittybox 1.0",
    "content": {
        "text": "This is a submission for IndieNews, the IndieWeb news aggregator.\nBowl for Kittybox, a new Micropub client, is now released!\nWhat is this?\nThis is meant to fill the niche of native desktop Micropub clients for those who prefer old-fashioned native applications instead of web apps or web apps packaged in a shrink-wrapped Google Chrome shell.\nIt's also a testing ground for my UX experiments. I believe Micropub provides a single well-oiled joint for blog posting, and that any user experience enhancements or additional features can simply live on top of it. The media endpoint standard is actually one of such enhancements \u2014 the Micropub endpoint does not strictly need to know about its existence, it can just understand links that the media endpoint gives to the client to insert into the post.\nOne of these experiments is Smart Summary \u2014 an optional summarization feature powered by a large language model. Hitting the Smart Summary button with a blog post in the editor pastes the post into an LLM and tells it to produce a one-sentence-summary. I rarely if ever filled the p-summary field, but now I guess I have no excuse.\nI also plan to make Kittybox collapse long posts in the feed that have summaries, and make an optional query parameter to provide un-collapsed posts (for MF2 feeds?), and helping produce summaries ties nicely into this feature.\nOf course, LLMs are not intelligent, cannot understand what they ingest and produce, and most importantly, have no conscience to feel guilty if they lie or mislead their user. So I recommend carefully proof-reading these summaries. Bowl will also under no circumstances support having LLMs write actual post content.\nI don't want this!\nThis can be disabled when building, pass -Dllm=false to Meson when configuring. When disabled, all LLM integration code is completely purged from the binary, leaving it completely unaware of this technology's existence. (The settings schema, however, is unaffected. I may fix that in the future.)\nWhat are the next steps?\nWhen I add media support, I will also try to make another LLM integration, Alt Text Vision, that could quickly draft an alt-text for an image you upload. (Of course, the user will be given the opportunity to review the output.)\nI also am thinking of creating a Microsub client that could summon Bowl to interact with posts. That may require Bowl to become D-Bus activatable and potentially support displaying several windows at once.\nI am also thinking about offline support, being able to draft posts while offline and send them once internet connection is available. Micropub also has some extensions for working with drafts, and I can use that to allow syncing the drafts to your own website.\nP.S.: When generating the summary for this post using Smart Summary, the LLM confused Bowl and Kittybox, and thought Kittybox is actually the Micropub client. This is a reminder to always double-check the text LLMs write for you.",
        "html": "<p><i>This is a submission for <a href=\"https://news.indieweb.org/en\" class=\"u-category\">IndieNews</a>, the IndieWeb news aggregator.</i></p>\n<p><a href=\"https://kittybox.fireburn.ru/bowl/\">Bowl for Kittybox</a>, a new Micropub client, is now released!</p>\n<h2>What is this?</h2>\n<p>This is meant to fill the niche of native desktop Micropub clients for those who prefer old-fashioned native applications instead of web apps or web apps packaged in a shrink-wrapped Google Chrome shell.</p>\n<p>It's also a testing ground for my UX experiments. I believe Micropub provides a <em>single well-oiled joint</em> for blog posting, and that any user experience enhancements or additional features can simply live on top of it. The media endpoint standard is actually one of such enhancements \u2014 the Micropub endpoint does not strictly need to know about its existence, it can just understand links that the media endpoint gives to the client to insert into the post.</p>\n<p>One of these experiments is <strong>Smart Summary</strong> \u2014 an optional summarization feature powered by a large language model. Hitting the Smart Summary button with a blog post in the editor pastes the post into an LLM and tells it to produce a one-sentence-summary. I rarely if ever filled the <code>p-summary</code> field, but now I guess I have no excuse.</p>\n<p>I also plan to make Kittybox collapse long posts in the feed that have summaries, and make an optional query parameter to provide un-collapsed posts (for MF2 feeds?), and helping produce summaries ties nicely into this feature.</p>\n<p>Of course, LLMs are not intelligent, cannot understand what they ingest and produce, and <em>most importantly</em>, have no conscience to feel guilty if they lie or mislead their user. So I recommend carefully proof-reading these summaries. Bowl will also under no circumstances support having LLMs write actual post content.</p>\n<h2>I don't want this!</h2>\n<p>This can be disabled when building, pass <code>-Dllm=false</code> to Meson when configuring. When disabled, all LLM integration code is completely purged from the binary, leaving it completely unaware of this technology's existence. (The settings schema, however, is unaffected. I may fix that in the future.)</p>\n<h2>What are the next steps?</h2>\n<p>When I add media support, I will also try to make another LLM integration, <strong>Alt Text Vision</strong>, that could quickly draft an alt-text for an image you upload. (Of course, the user will be given the opportunity to review the output.)</p>\n<p>I also am thinking of creating a Microsub client that could summon Bowl to interact with posts. That may require Bowl to become D-Bus activatable and potentially support displaying several windows at once.</p>\n<p>I am also thinking about offline support, being able to draft posts while offline and send them once internet connection is available. Micropub also has some extensions for working with drafts, and I can use that to allow syncing the drafts to your own website.</p>\n<p><strong>P.S.</strong>: When generating the summary for this post using <strong>Smart Summary</strong>, the LLM confused Bowl and Kittybox, and thought Kittybox is actually the Micropub client. This is a reminder to always double-check the text LLMs write for you.</p>"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://fireburn.ru/.kittybox/media/uploads/fe/ad/f8/76/e94e284444605135ad468b1563070dac3d2ad642c366b1e180f6eb65"
    },
    "post-type": "article",
    "_id": "42140392",
    "_source": "1371",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://fed.brid.gy/r/https://tantek.com/2024/242/t1/indiewebcamp-portland-10",
    "content": {
        "html": "<p>Had a great time at IndieWebCamp Portland 2024 this past Sunday \u2014 our 10th IndieWebCamp in Portland!<br /><br /><a href=\"https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k\">https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k</a><br /><br />Being a one day <a href=\"https://indieweb.social/tags/IndieWebCamp\">#<span class=\"p-category\">IndieWebCamp</span></a>, we focused more on making, hacking, and creating, than on formal discussion sessions.<br /><br />Nearly everyone gave a brief personal site intro with a summary of how they use their <a href=\"https://indieweb.social/tags/IndieWeb\">#<span class=\"p-category\">IndieWeb</span></a> site and what they would like to add, remove, or improve.<br />* <a href=\"https://indieweb.org/2024/Portland/Intros\">https://indieweb.org/2024/Portland/Intros</a><br /><br />There were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.<br /><br />We wrapped up with our usual Create Day<a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland-10#t5Yj1_note-1\">\u00b9</a> Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!<br />* <a href=\"https://indieweb.org/2024/Portland/Demos\">https://indieweb.org/2024/Portland/Demos</a><br /><br />Group photo and lots more about IndieWebCamp Portland 2024 at the event\u2019s wiki page:<br />* <a href=\"https://indieweb.org/2024/Portland\">https://indieweb.org/2024/Portland</a><br /><br />Thanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (<a href=\"https://martymcgui.re\">@martymcgui.re</a>) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (<a href=\"https://indieweb.social/@kevinmarks\">@kevinmarks@indieweb.social</a> <a href=\"https://xoxo.zone/@kevinmarks\">@kevinmarks@xoxo.zone</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/kevinmarks\">@kevinmarks</a>) for the IndieWebCamp live-tooting, and Ryan Barrett (<a href=\"https://snarfed.org\">@snarfed.org</a>) for amazing breakfast pastries from Dos Hermanos.<br /><br />The experience definitely raised our hopes and confidence for returning to Portland in 2025.<a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland-10#t5Yj1_note-2\">\u00b2</a><br /><br /><br />References:<br /><br /><a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland-10#t5Yj1_ref-1\">\u00b9</a> <a href=\"https://indieweb.org/Create_Day\">https://indieweb.org/Create_Day</a><br /><a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland-10#t5Yj1_ref-2\">\u00b2</a> <a href=\"https://indieweb.org/Planning#Portland\">https://indieweb.org/Planning#Portland</a><br /><br />This is post 19 of <a href=\"https://indieweb.social/tags/100PostsOfIndieWeb\">#<span class=\"p-category\">100PostsOfIndieWeb</span></a>. <a href=\"https://indieweb.social/tags/100Posts\">#<span class=\"p-category\">100Posts</span></a> <a href=\"https://indieweb.social/tags/2024_238\">#<span class=\"p-category\">2024_238</span></a><br /><br />\u2190 <a href=\"https://tantek.com/2024/238/t3/indiewebcamp-auto-linking\">https://tantek.com/2024/238/t3/indiewebcamp-auto-linking</a><br />\u2192 <a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-web\">https://tantek.com/2024/245/t1/read-write-suggest-edit-web</a></p>\n<a class=\"u-mention\" href=\"https://indieweb.social/@kevinmarks\"></a>\n<a class=\"u-mention\" href=\"https://martymcgui.re\"></a>\n<a class=\"u-mention\" href=\"https://snarfed.org\"></a>\n<a class=\"u-mention\" href=\"https://twitter.com/kevinmarks\"></a>\n<a class=\"u-mention\" href=\"https://xoxo.zone/@kevinmarks\"></a>",
        "text": "Had a great time at IndieWebCamp Portland 2024 this past Sunday \u2014 our 10th IndieWebCamp in Portland!\n\nhttps://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k\n\nBeing a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions.\n\nNearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve.\n* https://indieweb.org/2024/Portland/Intros\n\nThere were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.\n\nWe wrapped up with our usual Create Day\u00b9 Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!\n* https://indieweb.org/2024/Portland/Demos\n\nGroup photo and lots more about IndieWebCamp Portland 2024 at the event\u2019s wiki page:\n* https://indieweb.org/2024/Portland\n\nThanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos.\n\nThe experience definitely raised our hopes and confidence for returning to Portland in 2025.\u00b2\n\n\nReferences:\n\n\u00b9 https://indieweb.org/Create_Day\n\u00b2 https://indieweb.org/Planning#Portland\n\nThis is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238\n\n\u2190 https://tantek.com/2024/238/t3/indiewebcamp-auto-linking\n\u2192 https://tantek.com/2024/245/t1/read-write-suggest-edit-web"
    },
    "published": "2024-08-30T04:09:00+00:00",
    "post-type": "note",
    "_id": "42140354",
    "_source": "8007",
    "_is_read": false
}