{
    "type": "entry",
    "author": {
        "name": "@weirdwriter",
        "url": "https://tweesecake.social/@weirdwriter",
        "photo": null
    },
    "url": "https://tweesecake.social/@weirdwriter/111878390162006357",
    "content": {
        "html": "<p>Nice to see newer blogging platforms providing a blog by email option! Keep it up! <a href=\"https://posthaven.com/features\"><span>https://</span><span>posthaven.com/features</span><span></span></a> <a href=\"https://tweesecake.social/tags/Email\">#<span>Email</span></a> <a href=\"https://tweesecake.social/tags/Blog\">#<span>Blog</span></a> <a href=\"https://tweesecake.social/tags/Blogs\">#<span>Blogs</span></a> <a href=\"https://tweesecake.social/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
        "text": "Nice to see newer blogging platforms providing a blog by email option! Keep it up! https://posthaven.com/features #Email #Blog #Blogs #IndieWeb"
    },
    "published": "2024-02-05T10:25:56+00:00",
    "post-type": "note",
    "_id": "40194510",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@julian",
        "url": "https://social.synesthesia.co.uk/@julian",
        "photo": null
    },
    "url": "https://social.synesthesia.co.uk/@julian/111878232258249515",
    "content": {
        "html": "<p>Reply to 'A RSS Feed For My Mastodon Bookmarks'<br /><a href=\"https://social.synesthesia.co.uk/tags/IndieWeb\">#<span>IndieWeb</span></a><br /> An excellent idea from @ton ! Adapting it for my own context I can see two possible options - either pull the bookmarks from Mastodon into bookmark entries on this blog, or post to Diigo as new bookmarks. Probably the latter as I am fairly liberal in what I bookmark on Mastodon.<br /><a href=\"https://www.synesthesia.co.uk/stream/reply-to-a-rss-feed-for-my-mastodon-bookmarks/\"><span>https://www.</span><span>synesthesia.co.uk/stream/reply</span><span>-to-a-rss-feed-for-my-mastodon-bookmarks/</span></a></p>",
        "text": "Reply to 'A RSS Feed For My Mastodon Bookmarks'\n#IndieWeb\n An excellent idea from @ton ! Adapting it for my own context I can see two possible options - either pull the bookmarks from Mastodon into bookmark entries on this blog, or post to Diigo as new bookmarks. Probably the latter as I am fairly liberal in what I bookmark on Mastodon.\nhttps://www.synesthesia.co.uk/stream/reply-to-a-rss-feed-for-my-mastodon-bookmarks/"
    },
    "published": "2024-02-05T09:45:46+00:00",
    "post-type": "note",
    "_id": "40194375",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@weirdwriter",
        "url": "https://tweesecake.social/@weirdwriter",
        "photo": null
    },
    "url": "https://tweesecake.social/@weirdwriter/111878107409699053",
    "content": {
        "html": "<p>Reminder that I write about a lot of stuff, blindness, life stuff, my author news. I never stick to 1 topic so if you wanna follow, my RSS feed 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/Blog\">#<span>Blog</span></a> <a href=\"https://tweesecake.social/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
        "text": "Reminder that I write about a lot of stuff, blindness, life stuff, my author news. I never stick to 1 topic so if you wanna follow, my RSS feed is https://robertkingett.com/feed/ #RSS #Blog #IndieWeb"
    },
    "published": "2024-02-05T09:14:01+00:00",
    "post-type": "note",
    "_id": "40194231",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@links",
        "url": "https://social.bacardi55.io/@links",
        "photo": null
    },
    "url": "https://social.bacardi55.io/@links/statuses/01HNW874BF7MGQQVZJR9T21Q39",
    "content": {
        "html": "<p>[New Shared Link] - <a href=\"https://social.bacardi55.io/tags/indieweb\">#<span>IndieWeb</span></a> fediwall<br /><br /><a href=\"https://stream.indieweb.org/\">https://stream.indieweb.org/</a><br /><a href=\"https://social.bacardi55.io/tags/fediverse\">#<span>fediverse</span></a><br /><a href=\"https://social.bacardi55.io/tags/indieweb\">#<span>indieweb</span></a><br /><a href=\"https://social.bacardi55.io/tags/indiestream\">#<span>indiestream</span></a><br /><br />cc <span class=\"h-card\"><a class=\"u-url\" href=\"https://social.bacardi55.io/@bacardi55\">@<span>bacardi55</span></a></span></p>\n<a class=\"u-mention\" href=\"https://social.bacardi55.io/@bacardi55\"></a>",
        "text": "[New Shared Link] - #IndieWeb fediwall\n\nhttps://stream.indieweb.org/\n#fediverse\n#indieweb\n#indiestream\n\ncc @bacardi55"
    },
    "published": "2024-02-05T09:05:04+00:00",
    "post-type": "note",
    "_id": "40194232",
    "_source": "8007",
    "_is_read": false
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2024-02-04 20:08-0800",
    "url": "http://tantek.com/2024/035/t2/indiewebcamp-brighton-tickets-available",
    "category": [
        "Brighton",
        "London",
        "England",
        "Europe",
        "IndieWebCamp",
        "100PostsOfIndieWeb",
        "100Posts",
        "IndieWeb"
    ],
    "content": {
        "text": "#Brighton #London and other #England & #Europe friends:\n\n\ud83c\udfaa #IndieWebCamp Brighton tickets are available!\n\ud83c\udf9f https://ti.to/indiewebcamp/brighton-2024\n\ud83d\uddd3 2024-03-09\u202610\n\ud83c\udfe2 The Skiff, Brighton, England\n\ud83c\udf10 https://indieweb.org/2024/Brighton\n\nGrab an in-person ticket (limited capacity) then optionally add yourself to the list of participants: https://indieweb.org/2024/Brighton#In_person\n\nFor more information, see organizer @paulrobertlloyd.com (@paulrobertlloyd@mastodon.social)\u2019s post: https://paulrobertlloyd.com/2024/032/a1/indiewebcamp_brighton/\n\n\nAlso check out @ClearLeft.com (@clearleft@mastodon.social @clearleft)\u2019s \u201cPatterns Day\u201d (https://patternsday.com/) in Brighton the Thursday (2024-03-07) beforehand!\n\n\nPreviously: https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned\n\n\nThis is post 9 of #100PostsOfIndieWeb. #100Posts #IndieWeb\n\n\u2190 https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon\n\u2192 \ud83d\udd2e",
        "html": "#<span class=\"p-category\">Brighton</span> #<span class=\"p-category\">London</span> and other #<span class=\"p-category\">England</span> &amp; #<span class=\"p-category\">Europe</span> friends:<br /><br />\ud83c\udfaa #<span class=\"p-category\">IndieWebCamp</span> Brighton tickets are available!<br />\ud83c\udf9f <a href=\"https://ti.to/indiewebcamp/brighton-2024\">https://ti.to/indiewebcamp/brighton-2024</a><br />\ud83d\uddd3 2024-03-09\u202610<br />\ud83c\udfe2 The Skiff, Brighton, England<br />\ud83c\udf10 <a href=\"https://indieweb.org/2024/Brighton\">https://indieweb.org/2024/Brighton</a><br /><br />Grab an in-person ticket (limited capacity) then optionally add yourself to the list of participants: <a href=\"https://indieweb.org/2024/Brighton#In_person\">https://indieweb.org/2024/Brighton#In_person</a><br /><br />For more information, see organizer <a href=\"https://paulrobertlloyd.com\">@paulrobertlloyd.com</a> (<a href=\"https://mastodon.social/@paulrobertlloyd\">@paulrobertlloyd@mastodon.social</a>)\u2019s post: <a href=\"https://paulrobertlloyd.com/2024/032/a1/indiewebcamp_brighton/\">https://paulrobertlloyd.com/2024/032/a1/indiewebcamp_brighton/</a><br /><br /><br />Also check out <a href=\"https://ClearLeft.com\">@ClearLeft.com</a> (<a href=\"https://mastodon.social/@clearleft\">@clearleft@mastodon.social</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/clearleft\">@clearleft</a>)\u2019s \u201cPatterns Day\u201d (<a href=\"https://patternsday.com/\">https://patternsday.com/</a>) in Brighton the Thursday (2024-03-07) beforehand!<br /><br /><br />Previously: <a href=\"https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned\">https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned</a><br /><br /><br />This is post 9 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span> #<span class=\"p-category\">IndieWeb</span><br /><br />\u2190 <a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon\">https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon</a><br />\u2192 \ud83d\udd2e"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "note",
    "_id": "40194128",
    "_source": "1",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://fed.brid.gy/r/https://www.ciccarello.me/blog/2024/02/05/indiewebcamp-san-diego-2023/",
    "content": {
        "html": "<p>IndieWebCamp San Diego 2023</p><p><a href=\"https://fed.brid.gy/r/https://www.ciccarello.me/blog/2024/02/05/indiewebcamp-san-diego-2023/\"><span>https://</span><span>fed.brid.gy/r/https://www.cicc</span><span>arello.me/blog/2024/02/05/indiewebcamp-san-diego-2023/</span></a></p>",
        "text": "IndieWebCamp San Diego 2023\n\nhttps://fed.brid.gy/r/https://www.ciccarello.me/blog/2024/02/05/indiewebcamp-san-diego-2023/"
    },
    "published": "2024-02-05T07:36:58+00:00",
    "photo": [
        "https://files.mastodon.social/cache/media_attachments/files/111/877/737/115/711/642/original/9d408e961005d4ca.jpg"
    ],
    "post-type": "photo",
    "_id": "40193800",
    "_source": "8007",
    "_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/035/t2/indiewebcamp-brighton-tickets-available",
    "content": {
        "html": "<a href=\"https://indieweb.social/tags/Brighton\">#<span class=\"p-category\">Brighton</span></a> <a href=\"https://indieweb.social/tags/London\">#<span class=\"p-category\">London</span></a> and other <a href=\"https://indieweb.social/tags/England\">#<span class=\"p-category\">England</span></a> &amp; <a href=\"https://indieweb.social/tags/Europe\">#<span class=\"p-category\">Europe</span></a> friends:<br /><br />\ud83c\udfaa <a href=\"https://indieweb.social/tags/IndieWebCamp\">#<span class=\"p-category\">IndieWebCamp</span></a> Brighton tickets are available!<br />\ud83c\udf9f <a href=\"https://ti.to/indiewebcamp/brighton-2024\">https://ti.to/indiewebcamp/brighton-2024</a><br />\ud83d\uddd3 2024-03-09\u202610<br />\ud83c\udfe2 The Skiff, Brighton, England<br />\ud83c\udf10 <a href=\"https://indieweb.org/2024/Brighton\">https://indieweb.org/2024/Brighton</a><br /><br />Grab an in-person ticket (limited capacity) then optionally add yourself to the list of participants: <a href=\"https://indieweb.org/2024/Brighton#In_person\">https://indieweb.org/2024/Brighton#In_person</a><br /><br />For more information, see organizer <a href=\"https://paulrobertlloyd.com\">@paulrobertlloyd.com</a> (<a href=\"https://mastodon.social/@paulrobertlloyd\">@paulrobertlloyd@mastodon.social</a>)\u2019s post: <a href=\"https://paulrobertlloyd.com/2024/032/a1/indiewebcamp_brighton/\">https://paulrobertlloyd.com/2024/032/a1/indiewebcamp_brighton/</a><br /><br /><br />Also check out <a href=\"https://ClearLeft.com\">@ClearLeft.com</a> (<a href=\"https://mastodon.social/@clearleft\">@clearleft@mastodon.social</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/clearleft\">@clearleft</a>)\u2019s \u201cPatterns Day\u201d (<a href=\"https://patternsday.com/\">https://patternsday.com/</a>) in Brighton the Thursday (2024-03-07) beforehand!<br /><br /><br />Previously: <a href=\"https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned\">https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned</a><br /><br /><br />This is post 9 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/IndieWeb\">#<span class=\"p-category\">IndieWeb</span></a><br /><br />\u2190 <a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon\">https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon</a><br />\u2192 \ud83d\udd2e\n<a class=\"u-mention\" href=\"https://ClearLeft.com\"></a>\n<a class=\"u-mention\" href=\"https://mastodon.social/@clearleft\"></a>\n<a class=\"u-mention\" href=\"https://mastodon.social/@paulrobertlloyd\"></a>\n<a class=\"u-mention\" href=\"https://paulrobertlloyd.com\"></a>\n<a class=\"u-mention\" href=\"https://twitter.com/clearleft\"></a>",
        "text": "#Brighton #London and other #England & #Europe friends:\n\n\ud83c\udfaa #IndieWebCamp Brighton tickets are available!\n\ud83c\udf9f https://ti.to/indiewebcamp/brighton-2024\n\ud83d\uddd3 2024-03-09\u202610\n\ud83c\udfe2 The Skiff, Brighton, England\n\ud83c\udf10 https://indieweb.org/2024/Brighton\n\nGrab an in-person ticket (limited capacity) then optionally add yourself to the list of participants: https://indieweb.org/2024/Brighton#In_person\n\nFor more information, see organizer @paulrobertlloyd.com (@paulrobertlloyd@mastodon.social)\u2019s post: https://paulrobertlloyd.com/2024/032/a1/indiewebcamp_brighton/\n\n\nAlso check out @ClearLeft.com (@clearleft@mastodon.social @clearleft)\u2019s \u201cPatterns Day\u201d (https://patternsday.com/) in Brighton the Thursday (2024-03-07) beforehand!\n\n\nPreviously: https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned\n\n\nThis is post 9 of #100PostsOfIndieWeb. #100Posts #IndieWeb\n\n\u2190 https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon\n\u2192 \ud83d\udd2e"
    },
    "published": "2024-02-05T04:08:00+00:00",
    "post-type": "note",
    "_id": "40193257",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@ratika",
        "url": "https://scicomm.xyz/@ratika",
        "photo": null
    },
    "url": "https://scicomm.xyz/@ratika/111876787387827700",
    "content": {
        "html": "<p>From yesterday, one of my most favorite things I've written recently:</p><p><a href=\"https://chavanniclass.wordpress.com/2024/02/04/err-on-the-side-of-publishing/\"><span>https://</span><span>chavanniclass.wordpress.com/20</span><span>24/02/04/err-on-the-side-of-publishing/</span></a></p><p><a href=\"https://scicomm.xyz/tags/blog\">#<span>blog</span></a> <a href=\"https://scicomm.xyz/tags/blogging\">#<span>blogging</span></a> <a href=\"https://scicomm.xyz/tags/writing\">#<span>writing</span></a> <a href=\"https://scicomm.xyz/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://scicomm.xyz/tags/publishing\">#<span>publishing</span></a> <a href=\"https://scicomm.xyz/tags/WritingCommunity\">#<span>WritingCommunity</span></a> <a href=\"https://scicomm.xyz/tags/inspiration\">#<span>inspiration</span></a></p>",
        "text": "From yesterday, one of my most favorite things I've written recently:\n\nhttps://chavanniclass.wordpress.com/2024/02/04/err-on-the-side-of-publishing/\n\n#blog #blogging #writing #IndieWeb #publishing #WritingCommunity #inspiration"
    },
    "published": "2024-02-05T03:38:19+00:00",
    "post-type": "note",
    "_id": "40192746",
    "_source": "8007",
    "_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/035/t1/greshams-law-developers-users-jargon",
    "content": {
        "html": "Similar to <a href=\"https://paulgraham.com\">@paulgraham.com</a> (<a href=\"https://mas.to/@paulg\">@paulg@mas.to</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/paulg\">@paulg</a>)\u2019s 2008 observation about trolls<a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_note-1\">\u00b9</a>, there\u2019s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren\u2019t willing to use a forum with a lot of developer-speak.<br /><br />Whether such forums are email lists, chat (IRC, <a href=\"https://indieweb.social/tags/Matrix\">#<span class=\"p-category\">Matrix</span></a>, <a href=\"https://indieweb.social/tags/Slack\">#<span class=\"p-category\">Slack</span></a>, <a href=\"https://indieweb.social/tags/Discord\">#<span class=\"p-category\">Discord</span></a>), or, well, online forums (#Reddit, <a href=\"https://indieweb.social/tags/HackerNews\">#<span class=\"p-category\">HackerNews</span></a>), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.<br /><br />Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing &amp; <a href=\"https://indieweb.social/tags/jargon\">#<span class=\"p-category\">jargon</span></a>, and see such discussions as a distraction at best, and more like noise to be avoided.<br /><br />Paraphrasing Paul Graham again: once technical details, jargon, acronyms \u201ctake hold, it tends to become the dominant culture\u201d and discourages users from showing up, discussing user-centric topics, or even staying in said forum.<br /><br /><br />The <a href=\"https://indieweb.social/tags/IndieWeb\">#<span class=\"p-category\">IndieWeb</span></a> community started in 2011 as a single <a href=\"https://indieweb.social/tags/indiewebcamp\">#<span class=\"p-category\">indiewebcamp</span></a> IRC channel (no email list<a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_note-2\">\u00b2</a>) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need<a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_note-3\">\u00b3</a>, that you will use<a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_note-4\">\u2074</a> yourself. Conversations bridged real world use-cases and technical details.<br /><br />It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.<br /><br />As part of renaming the community from IndieWebCamp to IndieWeb<a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_note-5\">\u2075</a>, we created the <a href=\"https://indieweb.social/tags/indieweb-dev\">#<span class=\"p-category\">indieweb-dev</span></a> (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.<br /><br />The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main <a href=\"https://indieweb.social/tags/indieweb\">#<span class=\"p-category\">indieweb</span></a> channel who started technical conversations to continue them in the dev channel. <br /><br />Still, it was too easy for user-centric topics to veer into technical territory. It often felt more natural to continue a thread in the channel it started rather than break to another channel. There was also a need for regular community labor to nudge developer conversations to the developer chat channel.<br /><br /><br />We had already started documenting IndieWeb related jargon<a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_note-6\">\u2076</a> on the wiki and turned it into a MediaWiki Category so we could tag individual pages as jargon and have them automatically show-up in a list. Soon after, <a href=\"https://aaronparecki.com\">@aaronparecki.com</a> (<a href=\"https://aaronparecki.com/@aaronpk\">@aaronpk@aaronparecki.com</a>) added a heuristic to the friendly channel bot Loqi to recognize when people started using jargon in the main IndieWeb chat channel and nudge<a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_note-7\">\u2077</a> them to the development channel.<br /><br />Having Loqi do some of the gentle nudging has helped, though it\u2018s still quite easy for even the experienced folks in the community to get drawn into a developer conversation on main as it were.<br /><br />We\u2019ve documented both a summary and lengthier descriptions of channel purposes<a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_note-8\">\u2078</a> which help us remind each other, as well as provide a guide to newcomers.<br /><br />Both experienced community members and newcomers share much of the user-centric focus of the IndieWeb, the IndieWeb being for everyone<a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_note-9\">\u2079</a>, whether developer, hobbyist, or someone who wants an independent presence on the web without bothering with technical details. Whether some of us want to code or not, we all want to use our IndieWeb sites to express ourselves on the web, to use our sites instead of depending on social media silos. That shared purpose keeps us focused.<br /><br />It takes a village: eternal community vigilance is the price of staying user-centric and welcoming to newcomers.<br /><br />The ideas behind this post were originally shared in the IndieWeb meta chat channel.<a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_note-10\">\u00b9\u2070</a><br /><br /><br />This is post 8 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><br /><br />\u2190 <a href=\"https://tantek.com/2024/033/t1/earthquake-sanfrancisco-shifted\">https://tantek.com/2024/033/t1/earthquake-sanfrancisco-shifted</a><br />\u2192 \ud83d\udd2e<br /><br /><br />Post glossary:<br /><br />development channel (indieweb-dev)<br />\u00a0 <a href=\"https://indieweb.org/discuss#dev\">https://indieweb.org/discuss#dev</a><br />Discord<br />\u00a0 <a href=\"https://indieweb.org/Discord\">https://indieweb.org/Discord</a><br />format<br />\u00a0 <a href=\"https://indieweb.org/format\">https://indieweb.org/format</a><br />Hacker News (HN)<br />\u00a0 <a href=\"https://indieweb.org/Hacker_News\">https://indieweb.org/Hacker_News</a><br />IndieWeb<br />\u00a0 <a href=\"https://indieweb.org/IndieWeb\">https://indieweb.org/IndieWeb</a><br />IndieWebCamp<br />\u00a0 <a href=\"https://indieweb.org/IndieWebCamp\">https://indieweb.org/IndieWebCamp</a><br />IRC<br />\u00a0 <a href=\"https://indieweb.org/IRC\">https://indieweb.org/IRC</a><br />jargon<br />\u00a0 <a href=\"https://indieweb.org/jargon\">https://indieweb.org/jargon</a><br />Loqi<br />\u00a0 <a href=\"https://indieweb.org/Loqi\">https://indieweb.org/Loqi</a><br />main IndieWeb chat channel (on main)<br />\u00a0 <a href=\"https://indieweb.org/discuss#indieweb\">https://indieweb.org/discuss#indieweb</a><br />Matrix<br />\u00a0 <a href=\"https://indieweb.org/Matrix\">https://indieweb.org/Matrix</a><br />meta chat channel<br />\u00a0 <a href=\"https://indieweb.org/discuss#meta\">https://indieweb.org/discuss#meta</a><br />MediaWiki Category<br />\u00a0 <a href=\"https://www.mediawiki.org/wiki/Project:Categories\">https://www.mediawiki.org/wiki/Project:Categories</a><br />plumbing<br />\u00a0 <a href=\"https://indieweb.org/plumbing\">https://indieweb.org/plumbing</a><br />protocol<br />\u00a0 <a href=\"https://indieweb.org/protocol\">https://indieweb.org/protocol</a><br />Reddit<br />\u00a0 <a href=\"https://indieweb.org/Reddit\">https://indieweb.org/Reddit</a><br />tools<br />\u00a0 <a href=\"https://indieweb.org/tools\">https://indieweb.org/tools</a><br />Slack<br />\u00a0 <a href=\"https://indieweb.org/Slack\">https://indieweb.org/Slack</a><br />social media silos<br />\u00a0 <a href=\"https://indieweb.org/silos\">https://indieweb.org/silos</a><br /><br /><br /><a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_ref-1\">\u00b9</a> <a href=\"https://www.paulgraham.com/trolls.html\">https://www.paulgraham.com/trolls.html</a> (2008 essay, HN still succumbed to trolling)<br /><a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_ref-2\">\u00b2</a> <a href=\"https://indieweb.org/discuss#Email\">https://indieweb.org/discuss#Email</a><br /><a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_ref-3\">\u00b3</a> <a href=\"https://indieweb.org/make_what_you_need\">https://indieweb.org/make_what_you_need</a><br /><a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_ref-4\">\u2074</a> <a href=\"https://indieweb.org/use_what_you_make\">https://indieweb.org/use_what_you_make</a><br /><a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_ref-5\">\u2075</a> <a href=\"https://indieweb.org/rename_to_IndieWeb\">https://indieweb.org/rename_to_IndieWeb</a><br /><a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_ref-6\">\u2076</a> <a href=\"https://indieweb.org/jargon\">https://indieweb.org/jargon</a><br /><a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_ref-7\">\u2077</a> <a href=\"https://indieweb.org/Category:jargon#Loqi_Nudge\">https://indieweb.org/Category:jargon#Loqi_Nudge</a><br /><a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_ref-8\">\u2078</a> <a href=\"https://indieweb.org/discuss#Chat_Channels_Purposes\">https://indieweb.org/discuss#Chat_Channels_Purposes</a><br /><a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_ref-9\">\u2079</a> <a href=\"https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people\">https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people</a><br /><a href=\"https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon#t5VH1_ref-10\">\u00b9\u2070</a> <a href=\"https://chat.indieweb.org/meta/2024-01-22#t1705883690759800\">https://chat.indieweb.org/meta/2024-01-22#t1705883690759800</a>\n<a class=\"u-mention\" href=\"https://aaronparecki.com\"></a>\n<a class=\"u-mention\" href=\"https://aaronparecki.com/@aaronpk\"></a>\n<a class=\"u-mention\" href=\"https://mas.to/@paulg\"></a>\n<a class=\"u-mention\" href=\"https://paulgraham.com\"></a>\n<a class=\"u-mention\" href=\"https://twitter.com/paulg\"></a>",
        "text": "Similar to @paulgraham.com (@paulg@mas.to @paulg)\u2019s 2008 observation about trolls\u00b9, there\u2019s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren\u2019t willing to use a forum with a lot of developer-speak.\n\nWhether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.\n\nUsers in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided.\n\nParaphrasing Paul Graham again: once technical details, jargon, acronyms \u201ctake hold, it tends to become the dominant culture\u201d and discourages users from showing up, discussing user-centric topics, or even staying in said forum.\n\n\nThe #IndieWeb community started in 2011 as a single #indiewebcamp IRC channel (no email list\u00b2) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need\u00b3, that you will use\u2074 yourself. Conversations bridged real world use-cases and technical details.\n\nIt only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.\n\nAs part of renaming the community from IndieWebCamp to IndieWeb\u2075, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.\n\nThe community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started technical conversations to continue them in the dev channel. \n\nStill, it was too easy for user-centric topics to veer into technical territory. It often felt more natural to continue a thread in the channel it started rather than break to another channel. There was also a need for regular community labor to nudge developer conversations to the developer chat channel.\n\n\nWe had already started documenting IndieWeb related jargon\u2076 on the wiki and turned it into a MediaWiki Category so we could tag individual pages as jargon and have them automatically show-up in a list. Soon after, @aaronparecki.com (@aaronpk@aaronparecki.com) added a heuristic to the friendly channel bot Loqi to recognize when people started using jargon in the main IndieWeb chat channel and nudge\u2077 them to the development channel.\n\nHaving Loqi do some of the gentle nudging has helped, though it\u2018s still quite easy for even the experienced folks in the community to get drawn into a developer conversation on main as it were.\n\nWe\u2019ve documented both a summary and lengthier descriptions of channel purposes\u2078 which help us remind each other, as well as provide a guide to newcomers.\n\nBoth experienced community members and newcomers share much of the user-centric focus of the IndieWeb, the IndieWeb being for everyone\u2079, whether developer, hobbyist, or someone who wants an independent presence on the web without bothering with technical details. Whether some of us want to code or not, we all want to use our IndieWeb sites to express ourselves on the web, to use our sites instead of depending on social media silos. That shared purpose keeps us focused.\n\nIt takes a village: eternal community vigilance is the price of staying user-centric and welcoming to newcomers.\n\nThe ideas behind this post were originally shared in the IndieWeb meta chat channel.\u00b9\u2070\n\n\nThis is post 8 of #100PostsOfIndieWeb. #100Posts\n\n\u2190 https://tantek.com/2024/033/t1/earthquake-sanfrancisco-shifted\n\u2192 \ud83d\udd2e\n\n\nPost glossary:\n\ndevelopment channel (indieweb-dev)\n\u00a0 https://indieweb.org/discuss#dev\nDiscord\n\u00a0 https://indieweb.org/Discord\nformat\n\u00a0 https://indieweb.org/format\nHacker News (HN)\n\u00a0 https://indieweb.org/Hacker_News\nIndieWeb\n\u00a0 https://indieweb.org/IndieWeb\nIndieWebCamp\n\u00a0 https://indieweb.org/IndieWebCamp\nIRC\n\u00a0 https://indieweb.org/IRC\njargon\n\u00a0 https://indieweb.org/jargon\nLoqi\n\u00a0 https://indieweb.org/Loqi\nmain IndieWeb chat channel (on main)\n\u00a0 https://indieweb.org/discuss#indieweb\nMatrix\n\u00a0 https://indieweb.org/Matrix\nmeta chat channel\n\u00a0 https://indieweb.org/discuss#meta\nMediaWiki Category\n\u00a0 https://www.mediawiki.org/wiki/Project:Categories\nplumbing\n\u00a0 https://indieweb.org/plumbing\nprotocol\n\u00a0 https://indieweb.org/protocol\nReddit\n\u00a0 https://indieweb.org/Reddit\ntools\n\u00a0 https://indieweb.org/tools\nSlack\n\u00a0 https://indieweb.org/Slack\nsocial media silos\n\u00a0 https://indieweb.org/silos\n\n\n\u00b9 https://www.paulgraham.com/trolls.html (2008 essay, HN still succumbed to trolling)\n\u00b2 https://indieweb.org/discuss#Email\n\u00b3 https://indieweb.org/make_what_you_need\n\u2074 https://indieweb.org/use_what_you_make\n\u2075 https://indieweb.org/rename_to_IndieWeb\n\u2076 https://indieweb.org/jargon\n\u2077 https://indieweb.org/Category:jargon#Loqi_Nudge\n\u2078 https://indieweb.org/discuss#Chat_Channels_Purposes\n\u2079 https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people\n\u00b9\u2070 https://chat.indieweb.org/meta/2024-01-22#t1705883690759800"
    },
    "published": "2024-02-04T23:05:00+00:00",
    "post-type": "note",
    "_id": "40192747",
    "_source": "8007",
    "_is_read": false
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2024-02-04 15:05-0800",
    "url": "http://tantek.com/2024/035/t1/greshams-law-developers-users-jargon",
    "category": [
        "Matrix",
        "Slack",
        "Discord",
        "HackerNews",
        "jargon",
        "IndieWeb",
        "indiewebcamp",
        "indieweb-dev",
        "indieweb",
        "100PostsOfIndieWeb",
        "100Posts"
    ],
    "content": {
        "text": "Similar to @paulgraham.com (@paulg@mas.to @paulg)\u2019s 2008 observation about trolls\u00b9, there\u2019s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren\u2019t willing to use a forum with a lot of developer-speak.\n\nWhether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.\n\nUsers in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided.\n\nParaphrasing Paul Graham again: once technical details, jargon, acronyms \u201ctake hold, it tends to become the dominant culture\u201d and discourages users from showing up, discussing user-centric topics, or even staying in said forum.\n\n\nThe #IndieWeb community started in 2011 as a single #indiewebcamp IRC channel (no email list\u00b2) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need\u00b3, that you will use\u2074 yourself. Conversations bridged real world use-cases and technical details.\n\nIt only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.\n\nAs part of renaming the community from IndieWebCamp to IndieWeb\u2075, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.\n\nThe community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started technical conversations to continue them in the dev channel. \n\nStill, it was too easy for user-centric topics to veer into technical territory. It often felt more natural to continue a thread in the channel it started rather than break to another channel. There was also a need for regular community labor to nudge developer conversations to the developer chat channel.\n\n\nWe had already started documenting IndieWeb related jargon\u2076 on the wiki and turned it into a MediaWiki Category so we could tag individual pages as jargon and have them automatically show-up in a list. Soon after, @aaronparecki.com (@aaronpk@aaronparecki.com) added a heuristic to the friendly channel bot Loqi to recognize when people started using jargon in the main IndieWeb chat channel and nudge\u2077 them to the development channel.\n\nHaving Loqi do some of the gentle nudging has helped, though it\u2018s still quite easy for even the experienced folks in the community to get drawn into a developer conversation on main as it were.\n\nWe\u2019ve documented both a summary and lengthier descriptions of channel purposes\u2078 which help us remind each other, as well as provide a guide to newcomers.\n\nBoth experienced community members and newcomers share much of the user-centric focus of the IndieWeb, the IndieWeb being for everyone\u2079, whether developer, hobbyist, or someone who wants an independent presence on the web without bothering with technical details. Whether some of us want to code or not, we all want to use our IndieWeb sites to express ourselves on the web, to use our sites instead of depending on social media silos. That shared purpose keeps us focused.\n\nIt takes a village: eternal community vigilance is the price of staying user-centric and welcoming to newcomers.\n\nThe ideas behind this post were originally shared in the IndieWeb meta chat channel.\u00b9\u2070\n\n\nThis is post 8 of #100PostsOfIndieWeb. #100Posts\n\n\u2190 https://tantek.com/2024/033/t1/earthquake-sanfrancisco-shifted\n\u2192 \ud83d\udd2e\n\n\nPost glossary:\n\ndevelopment channel (indieweb-dev)\n\u00a0 https://indieweb.org/discuss#dev\nDiscord\n\u00a0 https://indieweb.org/Discord\nformat\n\u00a0 https://indieweb.org/format\nHacker News (HN)\n\u00a0 https://indieweb.org/Hacker_News\nIndieWeb\n\u00a0 https://indieweb.org/IndieWeb\nIndieWebCamp\n\u00a0 https://indieweb.org/IndieWebCamp\nIRC\n\u00a0 https://indieweb.org/IRC\njargon\n\u00a0 https://indieweb.org/jargon\nLoqi\n\u00a0 https://indieweb.org/Loqi\nmain IndieWeb chat channel (on main)\n\u00a0 https://indieweb.org/discuss#indieweb\nMatrix\n\u00a0 https://indieweb.org/Matrix\nmeta chat channel\n\u00a0 https://indieweb.org/discuss#meta\nMediaWiki Category\n\u00a0 https://www.mediawiki.org/wiki/Project:Categories\nplumbing\n\u00a0 https://indieweb.org/plumbing\nprotocol\n\u00a0 https://indieweb.org/protocol\nReddit\n\u00a0 https://indieweb.org/Reddit\ntools\n\u00a0 https://indieweb.org/tools\nSlack\n\u00a0 https://indieweb.org/Slack\nsocial media silos\n\u00a0 https://indieweb.org/silos\n\n\n\u00b9 https://www.paulgraham.com/trolls.html (2008 essay, HN still succumbed to trolling)\n\u00b2 https://indieweb.org/discuss#Email\n\u00b3 https://indieweb.org/make_what_you_need\n\u2074 https://indieweb.org/use_what_you_make\n\u2075 https://indieweb.org/rename_to_IndieWeb\n\u2076 https://indieweb.org/jargon\n\u2077 https://indieweb.org/Category:jargon#Loqi_Nudge\n\u2078 https://indieweb.org/discuss#Chat_Channels_Purposes\n\u2079 https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people\n\u00b9\u2070 https://chat.indieweb.org/meta/2024-01-22#t1705883690759800",
        "html": "Similar to <a href=\"https://paulgraham.com\">@paulgraham.com</a> (<a href=\"https://mas.to/@paulg\">@paulg@mas.to</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/paulg\">@paulg</a>)\u2019s 2008 observation about trolls<a href=\"http://tantek.com/#t5VH1_note-1\">\u00b9</a>, there\u2019s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren\u2019t willing to use a forum with a lot of developer-speak.<br /><br />Whether such forums are email lists, chat (IRC, #<span class=\"p-category\">Matrix</span>, #<span class=\"p-category\">Slack</span>, #<span class=\"p-category\">Discord</span>), or, well, online forums (#Reddit, #<span class=\"p-category\">HackerNews</span>), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.<br /><br />Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing &amp; #<span class=\"p-category\">jargon</span>, and see such discussions as a distraction at best, and more like noise to be avoided.<br /><br />Paraphrasing Paul Graham again: once technical details, jargon, acronyms \u201ctake hold, it tends to become the dominant culture\u201d and discourages users from showing up, discussing user-centric topics, or even staying in said forum.<br /><br /><br />The #<span class=\"p-category\">IndieWeb</span> community started in 2011 as a single #<span class=\"p-category\">indiewebcamp</span> IRC channel (no email list<a href=\"http://tantek.com/#t5VH1_note-2\">\u00b2</a>) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need<a href=\"http://tantek.com/#t5VH1_note-3\">\u00b3</a>, that you will use<a href=\"http://tantek.com/#t5VH1_note-4\">\u2074</a> yourself. Conversations bridged real world use-cases and technical details.<br /><br />It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.<br /><br />As part of renaming the community from IndieWebCamp to IndieWeb<a href=\"http://tantek.com/#t5VH1_note-5\">\u2075</a>, we created the #<span class=\"p-category\">indieweb-dev</span> (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.<br /><br />The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #<span class=\"p-category\">indieweb</span> channel who started technical conversations to continue them in the dev channel. <br /><br />Still, it was too easy for user-centric topics to veer into technical territory. It often felt more natural to continue a thread in the channel it started rather than break to another channel. There was also a need for regular community labor to nudge developer conversations to the developer chat channel.<br /><br /><br />We had already started documenting IndieWeb related jargon<a href=\"http://tantek.com/#t5VH1_note-6\">\u2076</a> on the wiki and turned it into a MediaWiki Category so we could tag individual pages as jargon and have them automatically show-up in a list. Soon after, <a href=\"https://aaronparecki.com\">@aaronparecki.com</a> (<a href=\"https://aaronparecki.com/@aaronpk\">@aaronpk@aaronparecki.com</a>) added a heuristic to the friendly channel bot Loqi to recognize when people started using jargon in the main IndieWeb chat channel and nudge<a href=\"http://tantek.com/#t5VH1_note-7\">\u2077</a> them to the development channel.<br /><br />Having Loqi do some of the gentle nudging has helped, though it\u2018s still quite easy for even the experienced folks in the community to get drawn into a developer conversation on main as it were.<br /><br />We\u2019ve documented both a summary and lengthier descriptions of channel purposes<a href=\"http://tantek.com/#t5VH1_note-8\">\u2078</a> which help us remind each other, as well as provide a guide to newcomers.<br /><br />Both experienced community members and newcomers share much of the user-centric focus of the IndieWeb, the IndieWeb being for everyone<a href=\"http://tantek.com/#t5VH1_note-9\">\u2079</a>, whether developer, hobbyist, or someone who wants an independent presence on the web without bothering with technical details. Whether some of us want to code or not, we all want to use our IndieWeb sites to express ourselves on the web, to use our sites instead of depending on social media silos. That shared purpose keeps us focused.<br /><br />It takes a village: eternal community vigilance is the price of staying user-centric and welcoming to newcomers.<br /><br />The ideas behind this post were originally shared in the IndieWeb meta chat channel.<a href=\"http://tantek.com/#t5VH1_note-10\">\u00b9\u2070</a><br /><br /><br />This is post 8 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span><br /><br />\u2190 <a href=\"https://tantek.com/2024/033/t1/earthquake-sanfrancisco-shifted\">https://tantek.com/2024/033/t1/earthquake-sanfrancisco-shifted</a><br />\u2192 \ud83d\udd2e<br /><br /><br />Post glossary:<br /><br />development channel (indieweb-dev)<br />\u00a0 <a href=\"https://indieweb.org/discuss#dev\">https://indieweb.org/discuss#dev</a><br />Discord<br />\u00a0 <a href=\"https://indieweb.org/Discord\">https://indieweb.org/Discord</a><br />format<br />\u00a0 <a href=\"https://indieweb.org/format\">https://indieweb.org/format</a><br />Hacker News (HN)<br />\u00a0 <a href=\"https://indieweb.org/Hacker_News\">https://indieweb.org/Hacker_News</a><br />IndieWeb<br />\u00a0 <a href=\"https://indieweb.org/IndieWeb\">https://indieweb.org/IndieWeb</a><br />IndieWebCamp<br />\u00a0 <a href=\"https://indieweb.org/IndieWebCamp\">https://indieweb.org/IndieWebCamp</a><br />IRC<br />\u00a0 <a href=\"https://indieweb.org/IRC\">https://indieweb.org/IRC</a><br />jargon<br />\u00a0 <a href=\"https://indieweb.org/jargon\">https://indieweb.org/jargon</a><br />Loqi<br />\u00a0 <a href=\"https://indieweb.org/Loqi\">https://indieweb.org/Loqi</a><br />main IndieWeb chat channel (on main)<br />\u00a0 <a href=\"https://indieweb.org/discuss#indieweb\">https://indieweb.org/discuss#indieweb</a><br />Matrix<br />\u00a0 <a href=\"https://indieweb.org/Matrix\">https://indieweb.org/Matrix</a><br />meta chat channel<br />\u00a0 <a href=\"https://indieweb.org/discuss#meta\">https://indieweb.org/discuss#meta</a><br />MediaWiki Category<br />\u00a0 <a href=\"https://www.mediawiki.org/wiki/Project:Categories\">https://www.mediawiki.org/wiki/Project:Categories</a><br />plumbing<br />\u00a0 <a href=\"https://indieweb.org/plumbing\">https://indieweb.org/plumbing</a><br />protocol<br />\u00a0 <a href=\"https://indieweb.org/protocol\">https://indieweb.org/protocol</a><br />Reddit<br />\u00a0 <a href=\"https://indieweb.org/Reddit\">https://indieweb.org/Reddit</a><br />tools<br />\u00a0 <a href=\"https://indieweb.org/tools\">https://indieweb.org/tools</a><br />Slack<br />\u00a0 <a href=\"https://indieweb.org/Slack\">https://indieweb.org/Slack</a><br />social media silos<br />\u00a0 <a href=\"https://indieweb.org/silos\">https://indieweb.org/silos</a><br /><br /><br /><a href=\"http://tantek.com/#t5VH1_ref-1\">\u00b9</a> <a href=\"https://www.paulgraham.com/trolls.html\">https://www.paulgraham.com/trolls.html</a> (2008 essay, HN still succumbed to trolling)<br /><a href=\"http://tantek.com/#t5VH1_ref-2\">\u00b2</a> <a href=\"https://indieweb.org/discuss#Email\">https://indieweb.org/discuss#Email</a><br /><a href=\"http://tantek.com/#t5VH1_ref-3\">\u00b3</a> <a href=\"https://indieweb.org/make_what_you_need\">https://indieweb.org/make_what_you_need</a><br /><a href=\"http://tantek.com/#t5VH1_ref-4\">\u2074</a> <a href=\"https://indieweb.org/use_what_you_make\">https://indieweb.org/use_what_you_make</a><br /><a href=\"http://tantek.com/#t5VH1_ref-5\">\u2075</a> <a href=\"https://indieweb.org/rename_to_IndieWeb\">https://indieweb.org/rename_to_IndieWeb</a><br /><a href=\"http://tantek.com/#t5VH1_ref-6\">\u2076</a> <a href=\"https://indieweb.org/jargon\">https://indieweb.org/jargon</a><br /><a href=\"http://tantek.com/#t5VH1_ref-7\">\u2077</a> <a href=\"https://indieweb.org/Category:jargon#Loqi_Nudge\">https://indieweb.org/Category:jargon#Loqi_Nudge</a><br /><a href=\"http://tantek.com/#t5VH1_ref-8\">\u2078</a> <a href=\"https://indieweb.org/discuss#Chat_Channels_Purposes\">https://indieweb.org/discuss#Chat_Channels_Purposes</a><br /><a href=\"http://tantek.com/#t5VH1_ref-9\">\u2079</a> <a href=\"https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people\">https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people</a><br /><a href=\"http://tantek.com/#t5VH1_ref-10\">\u00b9\u2070</a> <a href=\"https://chat.indieweb.org/meta/2024-01-22#t1705883690759800\">https://chat.indieweb.org/meta/2024-01-22#t1705883690759800</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": "40192569",
    "_source": "1",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@nejimaki",
        "url": "https://famichiki.jp/@nejimaki",
        "photo": null
    },
    "url": "https://famichiki.jp/@nejimaki/111875754369429548",
    "content": {
        "html": "<p><a href=\"https://onezero.medium.com/why-the-weird-internet-of-the-geocities-era-had-to-die-383f2870662c\"><span>https://</span><span>onezero.medium.com/why-the-wei</span><span>rd-internet-of-the-geocities-era-had-to-die-383f2870662c</span></a> <a href=\"https://famichiki.jp/tags/web\">#<span>web</span></a> <a href=\"https://famichiki.jp/tags/Internet\">#<span>Internet</span></a> <a href=\"https://famichiki.jp/tags/indieweb\">#<span>indieweb</span></a></p>",
        "text": "https://onezero.medium.com/why-the-weird-internet-of-the-geocities-era-had-to-die-383f2870662c #web #Internet #indieweb"
    },
    "published": "2024-02-04T23:15:37+00:00",
    "post-type": "note",
    "_id": "40191274",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@jcrabapple",
        "url": "https://dmv.community/@jcrabapple",
        "photo": null
    },
    "url": "https://dmv.community/@jcrabapple/111875503752695503",
    "content": {
        "html": "<p>New blog post!</p><p>How I Got Started In Tech - Cool As Heck</p><p><a href=\"https://cool-as-heck.blog/posts/how-i-got-started-in-tech\"><span>https://</span><span>cool-as-heck.blog/posts/how-i-</span><span>got-started-in-tech</span></a></p><p><a href=\"https://dmv.community/tags/indieweb\">#<span>indieweb</span></a></p>",
        "text": "New blog post!\n\nHow I Got Started In Tech - Cool As Heck\n\nhttps://cool-as-heck.blog/posts/how-i-got-started-in-tech\n\n#indieweb"
    },
    "published": "2024-02-04T22:11:53+00:00",
    "post-type": "note",
    "_id": "40190936",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@hamatti",
        "url": "https://mastodon.world/@hamatti",
        "photo": null
    },
    "url": "https://mastodon.world/@hamatti/111875193224479331",
    "content": {
        "html": "<p>I'm finding myself way overthinking this month's <a href=\"https://mastodon.world/tags/IndieWeb\">#<span>IndieWeb</span></a> Carnival post. I love the topic and I have now written two versions of my blog post but for some reason, it doesn't feel good. The post just doesn't flow in a way I want it to flow.</p><p>I'm being way more critical about it than any of my regular blog posts for some reason.</p><p><a href=\"https://mastodon.world/tags/blogging\">#<span>blogging</span></a> <a href=\"https://mastodon.world/tags/writing\">#<span>writing</span></a> </p><p>(IndieWeb Carnival is a monthly blogging thing, see <a href=\"https://indieweb.org/indieweb-carnival\"><span>https://</span><span>indieweb.org/indieweb-carnival</span><span></span></a> for general info and <a href=\"https://manuelmoreale.com/indieweb-carnival-digital-relationships\"><span>https://</span><span>manuelmoreale.com/indieweb-car</span><span>nival-digital-relationships</span></a> for this month's theme)</p>",
        "text": "I'm finding myself way overthinking this month's #IndieWeb Carnival post. I love the topic and I have now written two versions of my blog post but for some reason, it doesn't feel good. The post just doesn't flow in a way I want it to flow.\n\nI'm being way more critical about it than any of my regular blog posts for some reason.\n\n#blogging #writing \n\n(IndieWeb Carnival is a monthly blogging thing, see https://indieweb.org/indieweb-carnival for general info and https://manuelmoreale.com/indieweb-carnival-digital-relationships for this month's theme)"
    },
    "published": "2024-02-04T20:52:54+00:00",
    "post-type": "note",
    "_id": "40190460",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@karen",
        "url": "https://m.chronosaur.us/@karen",
        "photo": null
    },
    "url": "https://m.chronosaur.us/@karen/111874903340739038",
    "content": {
        "html": "<p>Got a <a href=\"https://m.chronosaur.us/tags/blog\">#<span>blog</span></a> ?  Let me know, I'll read it.</p><p><a href=\"https://m.chronosaur.us/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://m.chronosaur.us/tags/wordpress\">#<span>wordpress</span></a> <a href=\"https://m.chronosaur.us/tags/website\">#<span>website</span></a> <a href=\"https://m.chronosaur.us/tags/personalsites\">#<span>personalsites</span></a> <a href=\"https://m.chronosaur.us/tags/illreadit\">#<span>illreadit</span></a> </p><p><a href=\"https://chronosaur.us/2024/02/04/ill-read-it/\"><span>https://</span><span>chronosaur.us/2024/02/04/ill-r</span><span>ead-it/</span></a></p>",
        "text": "Got a #blog ?  Let me know, I'll read it.\n\n#indieweb #wordpress #website #personalsites #illreadit \n\nhttps://chronosaur.us/2024/02/04/ill-read-it/"
    },
    "published": "2024-02-04T19:39:11+00:00",
    "post-type": "note",
    "_id": "40190155",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@lars",
        "url": "https://mastodon.social/@lars",
        "photo": null
    },
    "url": "https://mastodon.social/@lars/111874899795836774",
    "content": {
        "html": "<p>ICYMI: Mechanical watches and Apple Watch-es, WordPress and HTML &amp; CSS (and a bit of <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> to spruce it up) all featured in my newest blog post: </p><p><a href=\"https://lars-christian.com/craftsmanship-and-compulsion/\"><span>https://</span><span>lars-christian.com/craftsmansh</span><span>ip-and-compulsion/</span></a></p><p>It's the latest outcome of my newly formed daily writing habit. The morning I wrote the first half of this was, by far, my best writing experience so far.</p>",
        "text": "ICYMI: Mechanical watches and Apple Watch-es, WordPress and HTML & CSS (and a bit of #indieweb to spruce it up) all featured in my newest blog post: \n\nhttps://lars-christian.com/craftsmanship-and-compulsion/\n\nIt's the latest outcome of my newly formed daily writing habit. The morning I wrote the first half of this was, by far, my best writing experience so far."
    },
    "published": "2024-02-04T19:38:17+00:00",
    "post-type": "note",
    "_id": "40190156",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@mikehaynes",
        "url": "https://social.lol/@mikehaynes",
        "photo": null
    },
    "url": "https://social.lol/@mikehaynes/111874586908311706",
    "content": {
        "html": "<p>I have this idea banging around in my head of an IndieWeb search engine, combined with a Fraidycat-style website feed/update tracker (that links directly to the site/post, not to a reader view), combined with a webring-style persistent navigation keeping it all together and I need someone to either help me make it or tell me I'm crazy. Maybe both. <a href=\"https://social.lol/tags/Design\">#<span>Design</span></a> <a href=\"https://social.lol/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
        "text": "I have this idea banging around in my head of an IndieWeb search engine, combined with a Fraidycat-style website feed/update tracker (that links directly to the site/post, not to a reader view), combined with a webring-style persistent navigation keeping it all together and I need someone to either help me make it or tell me I'm crazy. Maybe both. #Design #IndieWeb"
    },
    "published": "2024-02-04T18:18:43+00:00",
    "post-type": "note",
    "_id": "40189734",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@lazcorp",
        "url": "https://thegoblin.market/@lazcorp",
        "photo": null
    },
    "url": "https://thegoblin.market/@lazcorp/111873684653307284",
    "content": {
        "html": "<p>A new blog post by me: Think global, act localhost</p><p><a href=\"https://www.lazaruscorporation.co.uk/blogs/artists-notebook/posts/think-global-act-localhost\"><span>https://www.</span><span>lazaruscorporation.co.uk/blogs</span><span>/artists-notebook/posts/think-global-act-localhost</span></a></p><p><a href=\"https://thegoblin.market/tags/enshittification\">#<span>enshittification</span></a> <a href=\"https://thegoblin.market/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
        "text": "A new blog post by me: Think global, act localhost\n\nhttps://www.lazaruscorporation.co.uk/blogs/artists-notebook/posts/think-global-act-localhost\n\n#enshittification #IndieWeb"
    },
    "published": "2024-02-04T14:29:15+00:00",
    "post-type": "note",
    "_id": "40187961",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@jake4480",
        "url": "https://c.im/@jake4480",
        "photo": null
    },
    "url": "https://c.im/@jake4480/111872075251010948",
    "content": {
        "html": "<p>Making good progress the last couple days going through and organizing links. I threw a bunch on a spreadsheet and have been sorting and filtering. My wife has really helped with some great ideas along the way. (she's GENIUS with data stuff). </p><p>Sorting links is tedious and time consuming but it's something I've needed to do for a long time. It was also something I needed to do BEFORE I finish writing the couple blog posts I'm in the middle of - great to dig up some of this stuff for resources. </p><p>Lots of great indie web stuff, etc. \ud83d\udd25</p><p><a href=\"https://c.im/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://c.im/tags/WebDev\">#<span>WebDev</span></a> <a href=\"https://c.im/tags/WeirdWeb\">#<span>WeirdWeb</span></a></p>",
        "text": "Making good progress the last couple days going through and organizing links. I threw a bunch on a spreadsheet and have been sorting and filtering. My wife has really helped with some great ideas along the way. (she's GENIUS with data stuff). \n\nSorting links is tedious and time consuming but it's something I've needed to do for a long time. It was also something I needed to do BEFORE I finish writing the couple blog posts I'm in the middle of - great to dig up some of this stuff for resources. \n\nLots of great indie web stuff, etc. \ud83d\udd25\n\n#IndieWeb #WebDev #WeirdWeb"
    },
    "published": "2024-02-04T07:39:58+00:00",
    "post-type": "note",
    "_id": "40185880",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@hiz",
        "url": "https://indieweb.social/@hiz",
        "photo": null
    },
    "url": "https://indieweb.social/@hiz/111870866939190949",
    "content": {
        "html": "<p>This is a post in which the author describes the steps he took to make his JamStack configuration blog Fediverse compliant.<br />Bridgy Fed is used, plus the Webmention display is implemented.<br />JA: <a href=\"https://blog.tyage.net/post/2023/2023-07-17-bridgy-fed/\"><span>https://</span><span>blog.tyage.net/post/2023/2023-</span><span>07-17-bridgy-fed/</span></a><br /><a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a></p>",
        "text": "This is a post in which the author describes the steps he took to make his JamStack configuration blog Fediverse compliant.\nBridgy Fed is used, plus the Webmention display is implemented.\nJA: https://blog.tyage.net/post/2023/2023-07-17-bridgy-fed/\n#indieweb"
    },
    "published": "2024-02-04T02:32:40+00:00",
    "post-type": "note",
    "_id": "40184785",
    "_source": "8007",
    "_is_read": false
}

Ben Werdmuller werd.io/profile/benwerd

The four phases

{
    "type": "entry",
    "published": "2024-02-03T22:35:28+00:00",
    "url": "https://werd.io/2024/the-four-phases",
    "name": "The four phases",
    "content": {
        "text": "This post is part of February\u2019s\u00a0IndieWeb Carnival, in which Manuel Moreale prompts us to think about the various facets of digital relationships.\n\nOur relationship to digital technology has been through a few different phases.\n\nOne: the census\n\nIn the first, computers were the realm of government and big business: vast databases that might be about us, but that we could never own or interrogate ourselves. Companies like IBM manufactured room-sized (and then cabinet-sized) machines that took a team of specialized technicians to operate. They were rare and a symbol of top-down power.\n\nPunch cards were invented in the 1880s, and were machine-sortable even then, although not by anything we would recognize as a computer today. In the 1930s, a company called Dehomag, which was a 90%-owned subsidiary of IBM, used its punch card census technology to help the German Nazi party ethnically identify and sort the population. (Thomas Watson, IBM\u2019s CEO at the time, even came to Germany to oversee the operation.)\n\nThe first general-purpose digital computer, ENIAC, was first put to use to determine the feasibility of the H bomb. Other mainframe computers were used by the US Navy for codebreaking, and by the US census bureau. By the sixties and seventies, though, they were commonplace in larger corporate offices and in universities for non-military, non-governmental applications.\n\nTwo: the desk\n\nPersonal computers decentralized computing power and put it in everybody\u2019s hands. There was no overarching, always-on communications network for them to connect to, so every computer had its own copy of software that ran locally on it. There was no phoning home; no surveillance of our data; there were no ad-supported models. If you were lucky enough to have the not-insignificant sum of money needed to buy a computer, you could have one in your home. If you were lucky enough to have money left over for software, you could even do things with it.\n\nThe government and large institutions didn\u2019t have a monopoly on computing power; theoretically, anyone could have it. Anyone could write a program, too, and (if you had yet more money to buy a modem) distribute it on bulletin board systems and online services. Your hardware was yours; your software was yours; once you\u2019d paid your money, your relationship with the vendor was over.\n\nFor a while, you had a few options to connect with other people:Prodigy, an online service operated as a joint venture between CBS, IBM, and Sears\nCompuServe, which was owned and run by H&R Block\nAmerica Online, which was originally a way for Atari 2600 owners to download new games and store high scores\nIndependent bulletin boards, which were usually a single computer connected to a handful of direct phone lines for modems to connect to, run by an enthusiast\n(My first after-school job was as a BBS system operator for Daily Information, a local information and classifieds sheet in my hometown.)\n\nIn 1992, in addition to bulletin board systems and online services, the internet was made commercially available. Whereas BBSes, AOL, etc were distinct walled gardens, any service that was connected to the internet could reach any other service. It changed everything. (In 1995, my BBS job expanded to running what became one of the first classifieds websites.)\n\nBut for a while, the decentralized, private nature of personal computing remained. For most private individuals, connecting to the internet was like visiting a PO box: you\u2019d dial in, would upload and download any email you had pending, browse any websites you needed to, and then log off again. There was no way to constantly monitor people because internet users spent 23 hours of the day disconnected from the network.\n\nThree: the cloud\n\nBroadband, the iPhone, and wifi changed everything. Before the advent of broadband, most people needed to dial in to go online using their phone line. Before the iPhone, cell connections weren\u2019t metered for data, and there was very little bandwidth to go around. Before wifi, a computer needed to physically be connected with a cable to go online.\n\nWith broadband and wifi, computers could be connected to the internet 24/7. With the iPhone, everyone had a computer in their pocket, that was permanently connected and could be constantly sending data back to online services \u2014 including your location and who was in your address book.\n\nIt was incredibly convenient and changed the world in hundreds of ways. The web in particular is a modern marvel; the iPhone is a feat of design and engineering. But what we lost was the decentralized self-ownership of our digital worlds. More than that, we lost an ability to be private that we\u2019d had since the beginning of human civilization. It used to be that nobody needed to know where you were or what you were thinking about; that fundamental truth has gone the way of the dinosaur.\n\nAlmost immediately, our relationship to software changed in a few key ways:We could access all of our data from anywhere, on any device.\nInstead of buying a software package once, we were asked to subscribe to it.\nInstead of downloading or installing software, the main bulk of it could be run in a server farm somewhere.\nEvery facet of our data was stored in one of these server farms.\nMore data was produced about us as we used our devices \u2014 or even as we walked through our cities, shopped at stores, and met with other people \u2014 than we created intentionally ourselves.\nWhile computing became infinitely easier to use and the internet became a force that changed global society in ways that I still believe are a net positive, surveilling us also became infinitely easier. Companies wanted to know exactly what we were likely to buy; politicians wanted to know how we might vote; law enforcement wanted to know if we were dangerous. All paid online services to build profiles about us that could be used to sell advertising, could be mined by the right buyer, and could even be used to influence elections.\n\nFour: the farm\n\nOur relationship is now changing again.\n\nWhereas in the cloud era we were surveilled in order to profile us, our data is now being gathered for another set of reasons. We\u2019re used to online services ingesting our words and actions in order to predict our behaviors and influence us in certain directions. We\u2019re used to Target, for example, wanting to know if we\u2019re pregnant so they can be the first to sell us baby gear. We\u2019re not used to those services ingesting our words and actions in order to learn how to be us.\n\nIn our new relationship, software isn\u2019t just set up to surveil us to report on us; it\u2019s also set up to be able to do our work. GitHub Copilot learns from software we write so that it can write software automatically. Midjourney builds stunning illustrations and near-photorealistic images. Facebook is learning from the text and photos we upload so it can create its own text and realistic imagery (unlike many models, from data it actually has the license to). Far more than us being profiled, our modes of human expression are now being farmed for the benefit of people who hope to no longer have to hire us for our unique skills.\n\nIn the first era, technology was here to catalogue us.\n\nIn the second, it was here to empower us.\n\nIn the third, it was here to observe us.\n\nIn the fourth, it is here to replace us.\n\nWe had a very brief window, somewhere between the inception of the homebrew computer club and the introduction of the iPhone, where digital technology heralded distributed empowerment. Even then, empowerment was hardly evenly distributed, and any return to decentralization must be far more equitable than it ever was. But we find ourselves in a world where our true relationship is with power.\n\nOf course, it\u2019s a matter of degrees, and everything is a spectrum: there are plenty of services that don\u2019tuse your data to train generative AI models, and there are plenty that don\u2019t surveil you at all. There are also lots of applications and organizations that are actively designed to protect us from being watched and subjugated. New regulations are being proposed all the time that would guarantee our right to privacy and our right to not be included in training data.\n\nThose might seem like technical decisions, but they\u2019re really about preserving our ownership and autonomy, and returning those things to us when they\u2019ve already been lost. They\u2019re human, democratic decisions that seek to enforce a relationship where we\u2019re in charge. They\u2019re becoming more and more important every day.",
        "html": "<p><img src=\"https://werd.io/file/65bebfa64fe90519e004b292/thumb.jpg\" alt=\"A fictional mainframe\" width=\"1024\" height=\"683\" /></p><p><em>This post is part of February\u2019s\u00a0<a href=\"https://indieweb.org/indieweb-carnival\">IndieWeb Carnival</a>, in which <a href=\"https://manuelmoreale.com/indieweb-carnival-digital-relationships\">Manuel Moreale prompts us to think about the various facets of digital relationships</a>.</em></p><p>Our relationship to digital technology has been through a few different phases.</p><p><strong>One: the census</strong></p><p>In the first, computers were the realm of government and big business: vast databases that might be <em>about</em> us, but that we could never own or interrogate ourselves. Companies like IBM manufactured room-sized (and then cabinet-sized) machines that took a team of specialized technicians to operate. They were rare and a symbol of top-down power.</p><p>Punch cards were invented in the 1880s, and were machine-sortable even then, although not by anything we would recognize as a computer today. In the 1930s, a company called Dehomag, which was a 90%-owned subsidiary of IBM, used its punch card census technology to help the <a href=\"https://www.jewishvirtuallibrary.org/ibm-and-quot-death-s-calculator-quot-2\">German Nazi party ethnically identify and sort the population</a>. (Thomas Watson, IBM\u2019s CEO at the time, even came to Germany to oversee the operation.)</p><p>The first general-purpose digital computer, ENIAC, <a href=\"https://en.wikipedia.org/wiki/ENIAC\">was first put to use to determine the feasibility of the H bomb</a>. Other mainframe computers were used by the US Navy for codebreaking, and by the US census bureau. By the sixties and seventies, though, they were commonplace in larger corporate offices and in universities for non-military, non-governmental applications.</p><p><strong>Two: the desk</strong></p><p>Personal computers decentralized computing power and put it in everybody\u2019s hands. There was no overarching, always-on communications network for them to connect to, so every computer had its own copy of software that ran locally on it. There was no phoning home; no surveillance of our data; there were no ad-supported models. If you were lucky enough to have the not-insignificant sum of money needed to buy a computer, you could have one in your home. If you were lucky enough to have money left over for software, you could even do things with it.</p><p>The government and large institutions didn\u2019t have a monopoly on computing power; theoretically, anyone could have it. Anyone could <em>write</em> a program, too, and (if you had yet more money to buy a modem) distribute it on bulletin board systems and online services. Your hardware was yours; your software was yours; once you\u2019d paid your money, your relationship with the vendor was over.</p><p>For a while, you had a few options to connect with other people:</p><ul><li>Prodigy, an online service operated as a joint venture between CBS, IBM, and Sears</li>\n<li>CompuServe, which was owned and run by H&amp;R Block</li>\n<li>America Online, which was originally a way for Atari 2600 owners to download new games and store high scores</li>\n<li>Independent bulletin boards, which were usually a single computer connected to a handful of direct phone lines for modems to connect to, run by an enthusiast</li>\n</ul><p>(My first after-school job was as a BBS system operator for <a href=\"https://dailyinfo.co.uk\">Daily Information</a>, a local information and classifieds sheet in my hometown.)</p><p>In 1992, in addition to bulletin board systems and online services, the internet was made commercially available. Whereas BBSes, AOL, etc were distinct walled gardens, any service that was connected to the internet could reach any other service. It changed everything. (In 1995, my BBS job expanded to running what became one of the first classifieds websites.)</p><p>But for a while, the decentralized, private nature of personal computing remained. For most private individuals, connecting to the internet was like visiting a PO box: you\u2019d dial in, would upload and download any email you had pending, browse any websites you needed to, and then log off again. There was no way to constantly monitor people because internet users spent 23 hours of the day disconnected from the network.</p><p><strong>Three: the cloud</strong></p><p>Broadband, the iPhone, and wifi changed everything. Before the advent of broadband, most people needed to dial in to go online using their phone line. Before the iPhone, cell connections weren\u2019t metered for data, and there was very little bandwidth to go around. Before wifi, a computer needed to physically be connected with a cable to go online.</p><p>With broadband and wifi, computers could be connected to the internet 24/7. With the iPhone, everyone had a computer in their pocket, that was permanently connected and could be constantly sending data back to online services \u2014 including your location and who was in your address book.</p><p>It was incredibly convenient and changed the world in hundreds of ways. The web in particular is a modern marvel; the iPhone is a feat of design and engineering. But what we lost was the decentralized self-ownership of our digital worlds. More than that, we lost an ability to be private that we\u2019d had since the beginning of human civilization. It used to be that nobody needed to know where you were or what you were thinking about; that fundamental truth has gone the way of the dinosaur.</p><p>Almost immediately, our relationship to software changed in a few key ways:</p><ul><li>We could access all of our data from anywhere, on any device.</li>\n<li>Instead of buying a software package once, we were asked to subscribe to it.</li>\n<li>Instead of <em>downloading</em> or <em>installing</em> software, the main bulk of it could be run in a server farm somewhere.</li>\n<li>Every facet of our data was stored in one of these server farms.</li>\n<li>More data was produced <em>about</em> us as we used our devices \u2014 or even as we walked through our cities, shopped at stores, and met with other people \u2014 than we created intentionally ourselves.</li>\n</ul><p>While computing became infinitely easier to use and the internet became a force that changed global society in ways that I still believe are a net positive, surveilling us also became infinitely easier. Companies wanted to know exactly what we were likely to buy; politicians wanted to know how we might vote; law enforcement wanted to know if we were dangerous. All paid online services to build profiles about us that could be used to sell advertising, could be mined by the right buyer, and could even be used to influence elections.</p><p><strong>Four: the farm</strong></p><p>Our relationship is now changing again.</p><p>Whereas in the cloud era we were surveilled in order to profile us, our data is now being gathered for another set of reasons. We\u2019re used to online services ingesting our words and actions in order to predict our behaviors and influence us in certain directions. We\u2019re used to Target, for example, <a href=\"https://www.forbes.com/sites/kashmirhill/2012/02/16/how-target-figured-out-a-teen-girl-was-pregnant-before-her-father-did/\">wanting to know if we\u2019re pregnant so they can be the first to sell us baby gear</a>. We\u2019re <em>not</em> used to those services ingesting our words and actions in order to learn how to <em>be</em> us.</p><p>In our new relationship, software isn\u2019t just set up to surveil us to report on us; it\u2019s also set up to be able to do our work. GitHub Copilot learns from software we write so that it can write software automatically. Midjourney builds stunning illustrations and near-photorealistic images. Facebook is learning from the text and photos we upload so it can create its own text and realistic imagery (unlike many models, from data it actually has the license to). Far more than us being profiled, our modes of human expression are now being farmed for the benefit of people who hope to no longer have to hire us for our unique skills.</p><p>In the first era, technology was here to catalogue us.</p><p>In the second, it was here to empower us.</p><p>In the third, it was here to observe us.</p><p>In the fourth, it is here to replace us.</p><p>We had a very brief window, somewhere between the inception of <a href=\"https://en.wikipedia.org/wiki/Homebrew_Computer_Club\">the homebrew computer club</a> and the introduction of the iPhone, where digital technology heralded distributed empowerment. Even then, empowerment was hardly <em>evenly</em> distributed, and any return to decentralization must be far more equitable than it ever was. But we find ourselves in a world where our true relationship is with power.</p><p>Of course, it\u2019s a matter of degrees, and everything is a spectrum: there are plenty of services that <em>don\u2019t</em>use your data to train generative AI models, and there are plenty that don\u2019t surveil you at all. There are also lots of applications and organizations that are actively designed to protect us from being watched and subjugated. New regulations are being proposed all the time that would guarantee our right to privacy and our right to not be included in training data.</p><p>Those might seem like technical decisions, but they\u2019re really about preserving our ownership and autonomy, and returning those things to us when they\u2019ve already been lost. They\u2019re human, democratic decisions that seek to enforce a relationship where we\u2019re in charge. They\u2019re becoming more and more important every day.</p>"
    },
    "author": {
        "type": "card",
        "name": "Ben Werdmuller",
        "url": "https://werd.io/profile/benwerd",
        "photo": "https://werd.io/file/5d388c5fb16ea14aac640912/thumb.jpg"
    },
    "post-type": "article",
    "_id": "40184734",
    "_source": "191",
    "_is_read": false
}