Nostr, love at first sight

{
    "type": "entry",
    "author": {
        "name": null,
        "url": "https://dri.es/",
        "photo": null
    },
    "url": "https://dri.es/nostr-love-at-first-sight",
    "published": "2023-02-15T17:22:33-05:00",
    "content": {
        "html": "<img src=\"https://dri.es/files/images/blog/nostr.jpg\" alt=\"This is an old film roll featuring an ostrich running in every frame. The ostrich is purple in color, which represents the mascot of Nostr.\" title=\"Nostr\" /><p>I recently discovered <a href=\"https://github.com/nostr-protocol/nostr\">Nostr</a>, a decentralized social network that I find exciting and promising.</p>\n\n<p>Technically, Nostr is a protocol, not a social network. However, developers can use the Nostr protocol to create a variety of applications, including social networks.</p>\n \n<p>Nostr has been around a few years, but in December 2022, <a href=\"https://en.wikipedia.org/wiki/Jack_Dorsey\">Jack Dorsey</a>, the co-founder and former CEO of Twitter, announced that he had made <a href=\"https://twitter.com/jack/status/1603381913485541376\">a donation of 14 bitcoins</a>, valued at approximately $250,000. The donation was made to <code><a href=\"https://fiatjaf.com/\">@fiatjaf</a></code>, the anonymous founder of Nostr.</p>\n\n<p>Nostr stands for Notes and Other Stuff Transmitted by Relays. At its core, it is a system to exchange signed messages. The basic architecture can be explained in three bullets:</p>\n<ul><li>Every Nostr user is identified by a public key.</li>\n <li>Users send and retrieve messages to servers. These servers are called relays.</li>\n <li>Messages are called events.  Users sign events with a private key.  Events can be social media posts, private messages <a href=\"https://github.com/jesterui/jesterui\">chess moves</a>, etc.</li>\n</ul><p>I reviewed the Nostr protocol and found it to be straightforward to understand. The core protocol seems simple enough to implement in a day. This is a quality I appreciate in protocols. It is why I love RSS, for example.</p>\n\n<p>While the core Nostr protocol is simple, it is very extensible. It is extended using <a href=\"https://github.com/nostr-protocol/nips\">NIPs</a>, which stands for Nostr Implementation Possibilities. NIPs can add new fields and features to Nostr messages or events. For example, <a href=\"https://github.com/nostr-protocol/nips/blob/master/02.md\">NIP-2</a> adds usernames and contact lists (followers), <a href=\"https://github.com/nostr-protocol/nips/blob/master/08.md\">NIP-8</a> adds mentions, <a href=\"https://github.com/nostr-protocol/nips/blob/master/36.md\">NIP-36</a> adds support for content warnings, etc.</p>\n\n<h3>Joining the Nostr social network</h3>\n\n<p>Despite Nostr being just a few years old, there are a <a href=\"https://github.com/aljazceru/awesome-nostr\">number of clients</a>. I decided on <a href=\"https://github.com/damus-io/damus\">Damus</a>, a Twitter-like Nostr client for iOS. (Nostr's Damus is a clever pun on Nostradamus, the French astrologer.)</p>\n\n<p>You don't need to create a traditional account to sign up. You just use a public and private key. You can use these keys to use the platform anonymously. Unlike with proprietary social networks, you don't need an email address or phone number to register.</p>\n\n<p>If you want, you can choose to verify your identity. Verifying your identity links your public key to a public profile. I verified my identity using <a href=\"https://github.com/nostr-protocol/nips/blob/master/05.md\">NIP-05</a>, though different options exist. The NIP-05 verification process involved creating a static file on my website, available at <a href=\"https://dri.es/well-known/nostr.json\">https://dri.es/well-known/nostr.json</a>. It verifies that I'm the owner of the name <code>Dries</code>, the public key <code>npub176xpl3dl0agjt7vjeccw6v5grlx8f9mhc75aazwvvqfjvq5al8uszj5asu</code> and <a href=\"https://dri.es/\">https://dri.es</a>.</p>\n\n<h3>Nostr versus ActivityPub</h3>\n\n<p>Recently, Elon Musk became the world's richest troll and many people have left Twitter for <a href=\"https://en.wikipedia.org/wiki/Mastodon_(social_network)\">Mastodon</a>.  Mastodon is a decentralized social media platform built on the <a href=\"https://en.wikipedia.org/wiki/ActivityPub\">ActivityPub protocol</a>. I wanted to compare ActivityPub with Nostr, as Nostr offers many of the same promises.</p>\n\n<p>Before I do, I want to stress that I am not an expert in either ActivityPub or Nostr. I have read both specifications, but I have not implemented a client myself. However, I do have a basic understanding of the differences between the two.</p>\n\n<p>I also want to emphasize that both Nostr and ActivityPub are commendable for their efforts in addressing the problems encountered by traditional centralized social media platforms. I'm grateful for both.</p>\n\n<p>ActivityPub has been around for longer, and is more mature, but by comparison, there is a lot more to like about Nostr:</p>\n\n<ul><li><strong>Nostr is more decentralized</strong> \u2014 Nostr employs hash-based identification for users, while ActivityPub utilizes a more conventional user account system. ActivityPub user accounts are based on domain names, which can be controlled by third-party entities. Nostr's hash-based identification system is more decentralized, as it does not rely on domain names controlled by outside parties.</li>\n <li><strong>Nostr is easier to use</strong> \u2014 Decentralized networks are notoriously tough to use. To gain mass adoption, the user experience of decentralized social networks needs to match and exceed that of proprietary social networks. Both Nostr and Mastodon have user experience problems that stem from being decentralized applications. That said, I found Nostr easier to use, and I believe it is because the Nostr architecture is simpler.\n  <ul><li>Migrating to a different Mastodon server can be challenging, as your username is tied to the domain name of the current Mastodon server. However, this is not a problem in Nostr, as users are identified using a unique hash rather than a domain name.</li>\n      <li>Nostr doesn't currently offer the ability to edit or delete messages easily. While there is an API available to delete a message from a relay, it requires contacting each relay that holds a copy of your message to request its deletion, which can be challenging in practice.</li>\n  </ul></li>\n  <li><strong>Nostr is easier to develop for</strong> \u2014 The Nostr protocol is easier to implement than the ActivityPub protocol, and appears more extensible.</li>\n  <li><strong>Nostr can support different content policies</strong> \u2014 In ActivityPub, Mastodon server owners have the power to ban users and ban content. In Nostr, users and content can't be banned. However, each Nostr relay can have its own content policy, and users can choose which relays they want to use. For example, you could have a relay that only lets verified users publish, does not allow content that has anything to do with violence, and conforms the local laws of Belgium. It means that each user can choose the relay that they align with, rather than being subject to a Mastodon server owner's rules. It also means that policy development and maintenance can be distributed based on beliefs, geographic location, and more.</li>\n  <li><strong>Nostr has Zaps, which is potentially game-changing</strong> \u2014 ActivityPub lacks an equivalent of Zaps, which could make it harder to address funding issues and combat spam. More on that in the next section.</li>\n</ul><p>Lastly, both protocols likely suffer from problems unique to decentralized architectures. For example, when you post a link to your site, most clients will try to render a preview card of that link. That preview card can contain an image, the title of the page, and a description.  To create preview cards, the page is fetched and its HTML is parsed, looking for <a href=\"https://ogp.me/\">Open Graph tags</a>. Because of the distributed nature of both Nostr and Mastodon this <a href=\"https://odd.blog/2023/01/02/the-mastodon-onslaught-on-your-blog/\">can cause a site to get hammered with requests</a>.</p>\n\n<h3>Zaps</h3>\n\n<p>Social networks are overrun with spam and bots. Ads are everywhere. Platform owners profit from content creators, and content creators themselves don't make money. The world needs some breakthrough in this regard, and Nostr's Zap-support might offer solutions.</p>\n\n<p>A Zap is essentially a micropayment made using Bitcoin's Lightning network. Although Nostr itself does not use blockchain technology, it enables each message or event to contain a \"Zap request\" or \"Zap invoice\" (receipt). In other words, Nostr has optional blockchain integration for micropayment support.</p>\n\n<p>The implementation of this protocol extension can be found in <a href=\"https://github.com/nostr-protocol/nips/blob/master/57.md\">NIP-57</a>, which was finalized last week. As a brand new development, the potential of Zap-support has yet to be fully explored.  But it is not hard to see how micropayments could be used to reward content creators, fund relay upkeep, or decrease spam on social media platforms. With micropayments supported at the protocol level, trying out and implementing new solutions has become simpler than ever before.</p>\n\n<p>One potential solution is for receivers to require 200 satoshi (approximately $0.05) to receive a message from someone outside of their network. This would make spamming less economically attractive to marketers. Another option is for relays to charge their users a monthly fee, which could be used to maintain a block-list or content policy.</p>\n\n<p>Personally, I am a big fan of rewarding content creators, financing contributions, and implementing anti-spam techniques. It aligns with my interest in <a href=\"https://dri.es/balancing-makers-and-takers-to-scale-and-sustain-open-source\">public good governance and sustainability</a>.</p>\n\n<p>For the record, I have mixed feelings about blockchains.  I've <a href=\"https://dri.es/i-bought-some-bitcoin-and-here-is-why\">HODL'd Bitcoin since 2013</a> and Ethereum since 2017.  On one hand, I appreciate the opportunities and innovation they offer, but on the other hand, I am deeply concerned about their energy consumption and contribution to climate change.</p>\n\n<p>It's worth noting that the Lightning network is much more energy efficient than Bitcoin. Lightning operates on top of the Bitcoin network. The main Bitcoin blockchain, known as a layer 1 blockchain, is very energy inefficient and can only handle fewer than 10 transactions per second. In contrast, the <a href=\"https://en.wikipedia.org/wiki/Lightning_Network\">Lightning Network</a>, known as a layer 2 network, uses a lot less energy and has the potential to handle millions of transactions per second on top of the Bitcoin network.</p>\n\n<p>So, yes, Zap support is an important development to pay attention to. Even though it's brand new, I believe that in five years, we'll look back and agree that Zap support was a game-changer.</p>\n\n<h3>Conclusions</h3>\n\n<p>\"Notes and Other Stuff, Transmitted by Relays\" seems like a promising idea, even at this early stage. It is definitely something to keep an eye on. While for me it was love at first sight, I'm not sure how it will evolve. I am interested in exploring it further, and if time permits, I plan to create some basic integration with my own Drupal site.</p>\n\n<p><a href=\"https://news.indieweb.org/en\">Also posted on IndieNews</a>.</p>",
        "text": "I recently discovered Nostr, a decentralized social network that I find exciting and promising.\n\nTechnically, Nostr is a protocol, not a social network. However, developers can use the Nostr protocol to create a variety of applications, including social networks.\n \nNostr has been around a few years, but in December 2022, Jack Dorsey, the co-founder and former CEO of Twitter, announced that he had made a donation of 14 bitcoins, valued at approximately $250,000. The donation was made to @fiatjaf, the anonymous founder of Nostr.\n\nNostr stands for Notes and Other Stuff Transmitted by Relays. At its core, it is a system to exchange signed messages. The basic architecture can be explained in three bullets:\nEvery Nostr user is identified by a public key.\n Users send and retrieve messages to servers. These servers are called relays.\n Messages are called events.  Users sign events with a private key.  Events can be social media posts, private messages chess moves, etc.\nI reviewed the Nostr protocol and found it to be straightforward to understand. The core protocol seems simple enough to implement in a day. This is a quality I appreciate in protocols. It is why I love RSS, for example.\n\nWhile the core Nostr protocol is simple, it is very extensible. It is extended using NIPs, which stands for Nostr Implementation Possibilities. NIPs can add new fields and features to Nostr messages or events. For example, NIP-2 adds usernames and contact lists (followers), NIP-8 adds mentions, NIP-36 adds support for content warnings, etc.\n\nJoining the Nostr social network\n\nDespite Nostr being just a few years old, there are a number of clients. I decided on Damus, a Twitter-like Nostr client for iOS. (Nostr's Damus is a clever pun on Nostradamus, the French astrologer.)\n\nYou don't need to create a traditional account to sign up. You just use a public and private key. You can use these keys to use the platform anonymously. Unlike with proprietary social networks, you don't need an email address or phone number to register.\n\nIf you want, you can choose to verify your identity. Verifying your identity links your public key to a public profile. I verified my identity using NIP-05, though different options exist. The NIP-05 verification process involved creating a static file on my website, available at https://dri.es/well-known/nostr.json. It verifies that I'm the owner of the name Dries, the public key npub176xpl3dl0agjt7vjeccw6v5grlx8f9mhc75aazwvvqfjvq5al8uszj5asu and https://dri.es.\n\nNostr versus ActivityPub\n\nRecently, Elon Musk became the world's richest troll and many people have left Twitter for Mastodon.  Mastodon is a decentralized social media platform built on the ActivityPub protocol. I wanted to compare ActivityPub with Nostr, as Nostr offers many of the same promises.\n\nBefore I do, I want to stress that I am not an expert in either ActivityPub or Nostr. I have read both specifications, but I have not implemented a client myself. However, I do have a basic understanding of the differences between the two.\n\nI also want to emphasize that both Nostr and ActivityPub are commendable for their efforts in addressing the problems encountered by traditional centralized social media platforms. I'm grateful for both.\n\nActivityPub has been around for longer, and is more mature, but by comparison, there is a lot more to like about Nostr:\n\nNostr is more decentralized \u2014 Nostr employs hash-based identification for users, while ActivityPub utilizes a more conventional user account system. ActivityPub user accounts are based on domain names, which can be controlled by third-party entities. Nostr's hash-based identification system is more decentralized, as it does not rely on domain names controlled by outside parties.\n Nostr is easier to use \u2014 Decentralized networks are notoriously tough to use. To gain mass adoption, the user experience of decentralized social networks needs to match and exceed that of proprietary social networks. Both Nostr and Mastodon have user experience problems that stem from being decentralized applications. That said, I found Nostr easier to use, and I believe it is because the Nostr architecture is simpler.\n  Migrating to a different Mastodon server can be challenging, as your username is tied to the domain name of the current Mastodon server. However, this is not a problem in Nostr, as users are identified using a unique hash rather than a domain name.\n      Nostr doesn't currently offer the ability to edit or delete messages easily. While there is an API available to delete a message from a relay, it requires contacting each relay that holds a copy of your message to request its deletion, which can be challenging in practice.\n  \n  Nostr is easier to develop for \u2014 The Nostr protocol is easier to implement than the ActivityPub protocol, and appears more extensible.\n  Nostr can support different content policies \u2014 In ActivityPub, Mastodon server owners have the power to ban users and ban content. In Nostr, users and content can't be banned. However, each Nostr relay can have its own content policy, and users can choose which relays they want to use. For example, you could have a relay that only lets verified users publish, does not allow content that has anything to do with violence, and conforms the local laws of Belgium. It means that each user can choose the relay that they align with, rather than being subject to a Mastodon server owner's rules. It also means that policy development and maintenance can be distributed based on beliefs, geographic location, and more.\n  Nostr has Zaps, which is potentially game-changing \u2014 ActivityPub lacks an equivalent of Zaps, which could make it harder to address funding issues and combat spam. More on that in the next section.\nLastly, both protocols likely suffer from problems unique to decentralized architectures. For example, when you post a link to your site, most clients will try to render a preview card of that link. That preview card can contain an image, the title of the page, and a description.  To create preview cards, the page is fetched and its HTML is parsed, looking for Open Graph tags. Because of the distributed nature of both Nostr and Mastodon this can cause a site to get hammered with requests.\n\nZaps\n\nSocial networks are overrun with spam and bots. Ads are everywhere. Platform owners profit from content creators, and content creators themselves don't make money. The world needs some breakthrough in this regard, and Nostr's Zap-support might offer solutions.\n\nA Zap is essentially a micropayment made using Bitcoin's Lightning network. Although Nostr itself does not use blockchain technology, it enables each message or event to contain a \"Zap request\" or \"Zap invoice\" (receipt). In other words, Nostr has optional blockchain integration for micropayment support.\n\nThe implementation of this protocol extension can be found in NIP-57, which was finalized last week. As a brand new development, the potential of Zap-support has yet to be fully explored.  But it is not hard to see how micropayments could be used to reward content creators, fund relay upkeep, or decrease spam on social media platforms. With micropayments supported at the protocol level, trying out and implementing new solutions has become simpler than ever before.\n\nOne potential solution is for receivers to require 200 satoshi (approximately $0.05) to receive a message from someone outside of their network. This would make spamming less economically attractive to marketers. Another option is for relays to charge their users a monthly fee, which could be used to maintain a block-list or content policy.\n\nPersonally, I am a big fan of rewarding content creators, financing contributions, and implementing anti-spam techniques. It aligns with my interest in public good governance and sustainability.\n\nFor the record, I have mixed feelings about blockchains.  I've HODL'd Bitcoin since 2013 and Ethereum since 2017.  On one hand, I appreciate the opportunities and innovation they offer, but on the other hand, I am deeply concerned about their energy consumption and contribution to climate change.\n\nIt's worth noting that the Lightning network is much more energy efficient than Bitcoin. Lightning operates on top of the Bitcoin network. The main Bitcoin blockchain, known as a layer 1 blockchain, is very energy inefficient and can only handle fewer than 10 transactions per second. In contrast, the Lightning Network, known as a layer 2 network, uses a lot less energy and has the potential to handle millions of transactions per second on top of the Bitcoin network.\n\nSo, yes, Zap support is an important development to pay attention to. Even though it's brand new, I believe that in five years, we'll look back and agree that Zap support was a game-changer.\n\nConclusions\n\n\"Notes and Other Stuff, Transmitted by Relays\" seems like a promising idea, even at this early stage. It is definitely something to keep an eye on. While for me it was love at first sight, I'm not sure how it will evolve. I am interested in exploring it further, and if time permits, I plan to create some basic integration with my own Drupal site.\n\nAlso posted on IndieNews."
    },
    "name": "Nostr, love at first sight",
    "post-type": "article",
    "_id": "35184916",
    "_source": "238",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@rasterweb",
        "url": "https://mastodon.social/@rasterweb",
        "photo": null
    },
    "url": "https://mastodon.social/@rasterweb/109872172749606378",
    "content": {
        "html": "<p>Since I mentioned blogging, I forgot to ask for the URL to your blog so I can subscribe to it! Gimme those RSS feeds!</p><p><a href=\"https://mastodon.social/tags/rss\">#<span>rss</span></a> <a href=\"https://mastodon.social/tags/indieWeb\">#<span>indieWeb</span></a> <a href=\"https://mastodon.social/tags/blogging\">#<span>blogging</span></a> <a href=\"https://mastodon.social/tags/blog\">#<span>blog</span></a></p>",
        "text": "Since I mentioned blogging, I forgot to ask for the URL to your blog so I can subscribe to it! Gimme those RSS feeds!#rss #indieWeb #blogging #blog"
    },
    "published": "2023-02-16T02:58:27+00:00",
    "post-type": "note",
    "_id": "35183418",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@sketchee",
        "url": "https://socel.net/@sketchee",
        "photo": null
    },
    "url": "https://socel.net/@sketchee/109872158882380863",
    "content": {
        "html": "<p>You Should Check Out the Indie Web <a href=\"https://youtube.com/watch?v=rTSEr0cRJY8&amp;feature=share\"><span>https://</span><span>youtube.com/watch?v=rTSEr0cRJY</span><span>8&amp;feature=share</span></a></p><p>\"In this ramble video, I talk about the indie web - also known as the small web or old web - how it's better than web3, and why I think you should make a website\" </p><p><a href=\"https://socel.net/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://socel.net/tags/web3\">#<span>web3</span></a></p>",
        "text": "You Should Check Out the Indie Web https://youtube.com/watch?v=rTSEr0cRJY8&feature=share\"In this ramble video, I talk about the indie web - also known as the small web or old web - how it's better than web3, and why I think you should make a website\" #indieweb #web3"
    },
    "published": "2023-02-16T02:54:56+00:00",
    "post-type": "note",
    "_id": "35183419",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@asuh",
        "url": "https://mastodon.social/@asuh",
        "photo": null
    },
    "url": "https://mastodon.social/@asuh/109872056887757201",
    "content": {
        "html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://manton.org/activitypub/manton\">@<span>manton</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.au/@lime_juice_cube\">@<span>lime_juice_cube</span></a></span> I couldn't remember the discussion on <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> IRC so I'm glad you corrected me! I should have performed a quick search to verify before typing \ud83d\ude05</p>",
        "text": "@manton @lime_juice_cube I couldn't remember the discussion on #indieweb IRC so I'm glad you corrected me! I should have performed a quick search to verify before typing \ud83d\ude05"
    },
    "published": "2023-02-16T02:28:59+00:00",
    "post-type": "note",
    "_id": "35183167",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@asuh",
        "url": "https://mastodon.social/@asuh",
        "photo": null
    },
    "url": "https://mastodon.social/@asuh/109871862444367419",
    "content": {
        "html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.au/@lime_juice_cube\">@<span>lime_juice_cube</span></a></span> I always hear great things about <a href=\"https://micro.blog/\"><span>https://</span><span>micro.blog/</span><span></span></a> for <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> support and easy to use platform. <span class=\"h-card\"><a class=\"u-url\" href=\"https://manton.org/activitypub/manton\">@<span>manton</span></a></span> is very receptive to feedback and has a great platform for turnkey site.</p>",
        "text": "@lime_juice_cube I always hear great things about https://micro.blog/ for #indieweb support and easy to use platform. @manton is very receptive to feedback and has a great platform for turnkey site."
    },
    "published": "2023-02-16T01:39:32+00:00",
    "post-type": "note",
    "_id": "35182393",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@lime_juice_cube",
        "url": "https://mastodon.au/@lime_juice_cube",
        "photo": null
    },
    "url": "https://mastodon.au/@lime_juice_cube/109871775879059099",
    "content": {
        "html": "<p>Hey <a href=\"https://mastodon.au/tags/blogging\">#<span>blogging</span></a> <a href=\"https://mastodon.au/tags/mastodon\">#<span>mastodon</span></a> and <a href=\"https://mastodon.au/tags/fediverse\">#<span>fediverse</span></a> <a href=\"https://mastodon.au/tags/indieweb\">#<span>indieweb</span></a> users. Looking for a new blog framework that isn't just awful and locked-in. Very tired of <a href=\"https://mastodon.au/tags/wordpress\">#<span>wordpress</span></a> bloat. And <a href=\"https://mastodon.au/tags/ghostblog\">#<span>ghostblog</span></a> just doesn't work without Node JS. So, maybe <a href=\"https://mastodon.au/tags/writefreely\">#<span>writefreely</span></a>? But if I go self-hosted then I'm either asking my web host to support it or I'm having to learn about running my own virtualised server. At that point, I might as well just use WP! Any recommendations?</p>",
        "text": "Hey #blogging #mastodon and #fediverse #indieweb users. Looking for a new blog framework that isn't just awful and locked-in. Very tired of #wordpress bloat. And #ghostblog just doesn't work without Node JS. So, maybe #writefreely? But if I go self-hosted then I'm either asking my web host to support it or I'm having to learn about running my own virtualised server. At that point, I might as well just use WP! Any recommendations?"
    },
    "published": "2023-02-16T01:17:32+00:00",
    "post-type": "note",
    "_id": "35182394",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@ProgGrrl",
        "url": "https://bbq.snoot.com/@ProgGrrl",
        "photo": null
    },
    "url": "https://bbq.snoot.com/@ProgGrrl/109870982456661926",
    "content": {
        "html": "<p>It\u2019s really made my life better to see <a href=\"https://bbq.snoot.com/tags/TwitterDown\">#<span>TwitterDown</span></a> and not have a care\u2026 </p><p><a href=\"https://bbq.snoot.com/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
        "text": "It\u2019s really made my life better to see #TwitterDown and not have a care\u2026 #IndieWeb"
    },
    "published": "2023-02-15T21:55:45+00:00",
    "post-type": "note",
    "_id": "35179038",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@antranigv",
        "url": "https://sigin.fo/@antranigv",
        "photo": null
    },
    "url": "https://sigin.fo/@antranigv/109870343205502520",
    "content": {
        "html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://hachyderm.io/@KatherineInCode\">@<span>KatherineInCode</span></a></span> Personally, never even heard of 11ty, Jekyll and Hugo, on the other hand, it's like `pkg install jekyll/hugo` and then just `jekyll/hugo new` and it\u2019s good to go!</p><p>Please share you blog's link after you publish! :)</p><p><a href=\"https://sigin.fo/tags/indieweb\">#<span>indieweb</span></a></p>",
        "text": "@KatherineInCode Personally, never even heard of 11ty, Jekyll and Hugo, on the other hand, it's like `pkg install jekyll/hugo` and then just `jekyll/hugo new` and it\u2019s good to go!Please share you blog's link after you publish! :)#indieweb"
    },
    "published": "2023-02-15T19:13:11+00:00",
    "post-type": "note",
    "_id": "35174910",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@asuh",
        "url": "https://mastodon.social/@asuh",
        "photo": null
    },
    "url": "https://mastodon.social/@asuh/109870322090654126",
    "content": {
        "html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://me.dm/@anildash\">@<span>anildash</span></a></span> If we were able to align even 1% of that kind of workforce on <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> projects as a compliment to Mastodon and ActivityPub development, we could have a comprehensive alternative to anything mainstream social media could provide.</p>",
        "text": "@anildash If we were able to align even 1% of that kind of workforce on #indieweb projects as a compliment to Mastodon and ActivityPub development, we could have a comprehensive alternative to anything mainstream social media could provide."
    },
    "published": "2023-02-15T19:07:49+00:00",
    "post-type": "note",
    "_id": "35174911",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@leonp",
        "url": "https://fosstodon.org/@leonp",
        "photo": null
    },
    "url": "https://fosstodon.org/@leonp/109867631087582961",
    "content": {
        "html": "<p>When you\u2019re using an RSS feed to trigger outbound webmentions, remember to validate that feed. The very useful Github Webmentions integration won\u2019t work with an invalid feed.</p><p>          <br /><br />           \ud83c\udff7 <a href=\"https://fosstodon.org/tags/Indieweb\">#<span>Indieweb</span></a> <a href=\"https://fosstodon.org/tags/Netlify\">#<span>Netlify</span></a> <a href=\"https://fosstodon.org/tags/RSS\">#<span>RSS</span></a> <a href=\"https://fosstodon.org/tags/Webmentions\">#<span>Webmentions</span></a><br /><a href=\"https://www.thisdaysportion.com/notes/validate-yer-feeds\"><span>https://www.</span><span>thisdaysportion.com/notes/vali</span><span>date-yer-feeds</span></a></p>",
        "text": "When you\u2019re using an RSS feed to trigger outbound webmentions, remember to validate that feed. The very useful Github Webmentions integration won\u2019t work with an invalid feed.          \n\n           \ud83c\udff7 #Indieweb #Netlify #RSS #Webmentions\nhttps://www.thisdaysportion.com/notes/validate-yer-feeds"
    },
    "published": "2023-02-15T07:43:27+00:00",
    "post-type": "note",
    "_id": "35159789",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@box464",
        "url": "https://mastodon.social/@box464",
        "photo": null
    },
    "url": "https://mastodon.social/@box464/109866943443958598",
    "content": {
        "html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://social.faebornnetworks.org/@katmmoss\">@<span>katmmoss</span></a></span> <a href=\"https://mastodon.social/tags/DotNet\">#<span>DotNet</span></a> and <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> merged together sounds like an interesting \"you got your peanut butter in my chocolate\" type match. Strange, but it just might work!</p><p>I'm a .NET developer by trade (now a manager) but spend my hobby coding time with other technologies.</p>",
        "text": "@katmmoss #DotNet and #IndieWeb merged together sounds like an interesting \"you got your peanut butter in my chocolate\" type match. Strange, but it just might work!I'm a .NET developer by trade (now a manager) but spend my hobby coding time with other technologies."
    },
    "published": "2023-02-15T04:48:34+00:00",
    "post-type": "note",
    "_id": "35157789",
    "_source": "7235",
    "_is_read": false
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2023-02-13 22:33-0800",
    "url": "http://tantek.com/2023/044/t1/unified-sent-box-universal-outbox",
    "category": [
        "IndieWeb",
        "100DaysOfIndieWeb",
        "100Days"
    ],
    "content": {
        "text": "11 days ago I suggested\u00b9 a unified Sent box of everything sent/reacji\u2019d to all Slacks logged-in with the same email. Beyond Slack though, everything you write & send anywhere: txt, chat, email, web. A Universal Outbox of all content you create, including responses. A flat time ordered list of output across mediums. And a source of material to blog.\n\nThe phrase \u201cUniversal Outbox\u201d seemed obvious to describe such a feature, parallel to the idea of a universal inbox that I remember first learning of as a concept from Apple\u2019s AOCE project\u00b2 in the early 1990s, but called a \u201csingle universal mailbox\u201d.\n\nFiguring someone must have come up with the idea, I did a web search, and found a minimal wiki page from 2011:\n\nhttp://webseitz.fluxent.com/wiki/UniversalOutbox\n\nwhich did vaguely describe the idea: \n\u00a0\u201ca single hub where someone can find all your outbound LifeStreams?\u201d\n\nExcept I don\u2019t want \u201cwhere someone can\u201d, but rather \u201cwhere I can\u201d, which is an important distinction, because it would explicitly include things you send to a single person or other limited audience.\n\nAnd yes, \u201ccan find\u201d, with full personal search.\n\nAside: the \u201cwhere someone can\u201d use-case of the presumably more public \u201call your outbound LifeStreams\u201d is essentially what an #IndieWeb site is for. One place to publish all you want, any way you want, in a composite stream.\n\nHow many times have you texted, IM\u2019d, Slacked, or emailed nearly the same thing, maybe to different people, retyped from memory, that you could have searched, and copy & pasted instead?\n\nOr how many times have you written similar public posts, replies, or emails, on the same topic, where you said the same thing just slightly differently?\n\nWhat if you could publish such common ideas, concepts, points once, with a permalink, and then cite that permalink rather than retyping the same thing repeatedly?\n\nThe idea of a Universal Outbox feels like a logical extension of many IndieWeb practices such as owning your data\u00b3.\n\nWhile all the things you post on your personal site are a part of your Universal Outbox, they are only a subset. Even if you include everything you can PESOS from other sites, that still leaves services and sites without API access, or with APIs you may not have permission to use.\n\nAnother approach that may work well is a browser add-on, which would at least be able to collect everything you type into websites. Such an add-on would be more useful than a keylogger, because a browser add-on would have a much better understanding of and access to the context of where you are entering information. An add-on could keep track of permalinks to each statement, e.g. each statement in Slack has a permalink (viewable only with login).\n\nA modest prototype add-on could start with my initial suggestion, a universal sent box that aggregated everything you said across all Slack instances you use in that browser. This would be particularly useful for keeping a personal log of your statements across free Slack instances where everything you say disappears in 90 days.\n\nFor now, perhaps the manual-until-it-hurts answer is to periodically check the \u201cDrafts & sent\u201d folder in free Slacks (from the bottom upwards, since Slack\u2019s web UI lacks the ability to sort or reverse the order of your Drafts & sent folder), one instance at a time, blogging or otherwise copy/pasting anything you want to cite, save, or remember.\n\n\nThis is day 31 of #100DaysOfIndieWeb #100Days\n\n\u2190 Day 30: https://tantek.com/2023/043/t1/footnotes-unicode-links\n\u2192 \ud83d\udd2e\n\n\nPost Glossary:\n\ncomposite stream\n\u00a0https://indieweb.org/composite_stream\nmanual-until-it-hurts\n\u00a0https://indieweb.org/manual_until_it_hurts\npermalink\n\u00a0https://indieweb.org/permalink\nPESOS\n\u00a0https://indieweb.org/PESOS\nreacji\n\u00a0https://indieweb.org/reacji\nresponses\n\u00a0https://indieweb.org/responses\n\u00a0\n\n\u00b9 https://chat.indieweb.org/2023-02-02#t1675370124338700\n\u00b2 https://en.wikipedia.org/wiki/Apple_Open_Collaboration_Environment\n\u00b3 https://indieweb.org/own_your_data",
        "html": "11 days ago I suggested<a href=\"http://tantek.com/#t5PM1_note-1\">\u00b9</a> a unified Sent box of everything sent/reacji\u2019d to all Slacks logged-in with the same email. Beyond Slack though, everything you write &amp; send anywhere: txt, chat, email, web. A Universal Outbox of all content you create, including responses. A flat time ordered list of output across mediums. And a source of material to blog.<br /><br />The phrase \u201cUniversal Outbox\u201d seemed obvious to describe such a feature, parallel to the idea of a universal inbox that I remember first learning of as a concept from Apple\u2019s AOCE project<a href=\"http://tantek.com/#t5PM1_note-2\">\u00b2</a> in the early 1990s, but called a \u201csingle universal mailbox\u201d.<br /><br />Figuring someone must have come up with the idea, I did a web search, and found a minimal wiki page from 2011:<br /><br /><a href=\"http://webseitz.fluxent.com/wiki/UniversalOutbox\">http://webseitz.fluxent.com/wiki/UniversalOutbox</a><br /><br />which did vaguely describe the idea: <br />\u00a0\u201ca single hub where someone can find all your outbound LifeStreams?\u201d<br /><br />Except I don\u2019t want \u201cwhere someone can\u201d, but rather \u201cwhere I can\u201d, which is an important distinction, because it would explicitly include things you send to a single person or other limited audience.<br /><br />And yes, \u201ccan find\u201d, with full personal search.<br /><br />Aside: the \u201cwhere someone can\u201d use-case of the presumably more public \u201call your outbound LifeStreams\u201d is essentially what an #<span class=\"p-category\">IndieWeb</span> site is for. One place to publish all you want, any way you want, in a composite stream.<br /><br />How many times have you texted, IM\u2019d, Slacked, or emailed nearly the same thing, maybe to different people, retyped from memory, that you could have searched, and copy &amp; pasted instead?<br /><br />Or how many times have you written similar public posts, replies, or emails, on the same topic, where you said the same thing just slightly differently?<br /><br />What if you could publish such common ideas, concepts, points once, with a permalink, and then cite that permalink rather than retyping the same thing repeatedly?<br /><br />The idea of a Universal Outbox feels like a logical extension of many IndieWeb practices such as owning your data<a href=\"http://tantek.com/#t5PM1_note-3\">\u00b3</a>.<br /><br />While all the things you post on your personal site are a part of your Universal Outbox, they are only a subset. Even if you include everything you can PESOS from other sites, that still leaves services and sites without API access, or with APIs you may not have permission to use.<br /><br />Another approach that may work well is a browser add-on, which would at least be able to collect everything you type into websites. Such an add-on would be more useful than a keylogger, because a browser add-on would have a much better understanding of and access to the context of where you are entering information. An add-on could keep track of permalinks to each statement, e.g. each statement in Slack has a permalink (viewable only with login).<br /><br />A modest prototype add-on could start with my initial suggestion, a universal sent box that aggregated everything you said across all Slack instances you use in that browser. This would be particularly useful for keeping a personal log of your statements across free Slack instances where everything you say disappears in 90 days.<br /><br />For now, perhaps the manual-until-it-hurts answer is to periodically check the \u201cDrafts &amp; sent\u201d folder in free Slacks (from the bottom upwards, since Slack\u2019s web UI lacks the ability to sort or reverse the order of your Drafts &amp; sent folder), one instance at a time, blogging or otherwise copy/pasting anything you want to cite, save, or remember.<br /><br /><br />This is day 31 of #<span class=\"p-category\">100DaysOfIndieWeb</span> #<span class=\"p-category\">100Days</span><br /><br />\u2190 Day 30: <a href=\"https://tantek.com/2023/043/t1/footnotes-unicode-links\">https://tantek.com/2023/043/t1/footnotes-unicode-links</a><br />\u2192 \ud83d\udd2e<br /><br /><br />Post Glossary:<br /><br />composite stream<br />\u00a0<a href=\"https://indieweb.org/composite_stream\">https://indieweb.org/composite_stream</a><br />manual-until-it-hurts<br />\u00a0<a href=\"https://indieweb.org/manual_until_it_hurts\">https://indieweb.org/manual_until_it_hurts</a><br />permalink<br />\u00a0<a href=\"https://indieweb.org/permalink\">https://indieweb.org/permalink</a><br />PESOS<br />\u00a0<a href=\"https://indieweb.org/PESOS\">https://indieweb.org/PESOS</a><br />reacji<br />\u00a0<a href=\"https://indieweb.org/reacji\">https://indieweb.org/reacji</a><br />responses<br />\u00a0<a href=\"https://indieweb.org/responses\">https://indieweb.org/responses</a><br />\u00a0<br /><br /><a href=\"http://tantek.com/#t5PM1_ref-1\">\u00b9</a> <a href=\"https://chat.indieweb.org/2023-02-02#t1675370124338700\">https://chat.indieweb.org/2023-02-02#t1675370124338700</a><br /><a href=\"http://tantek.com/#t5PM1_ref-2\">\u00b2</a> <a href=\"https://en.wikipedia.org/wiki/Apple_Open_Collaboration_Environment\">https://en.wikipedia.org/wiki/Apple_Open_Collaboration_Environment</a><br /><a href=\"http://tantek.com/#t5PM1_ref-3\">\u00b3</a> <a href=\"https://indieweb.org/own_your_data\">https://indieweb.org/own_your_data</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": "35156884",
    "_source": "1",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@katmmoss",
        "url": "https://social.faebornnetworks.org/@katmmoss",
        "photo": null
    },
    "url": "https://social.faebornnetworks.org/@katmmoss/109866536635474403",
    "content": {
        "html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@box464\">@<span>box464</span></a></span> There's where the <a href=\"https://social.faebornnetworks.org/tags/IndieWeb\">#<span>IndieWeb</span></a> needs to eventually meet <a href=\"https://social.faebornnetworks.org/tags/Dotnet\">#<span>Dotnet</span></a>. Don't worry. I'm learning the C# language for that reason.</p>",
        "text": "@box464 There's where the #IndieWeb needs to eventually meet #Dotnet. Don't worry. I'm learning the C# language for that reason."
    },
    "published": "2023-02-15T03:05:07+00:00",
    "post-type": "note",
    "_id": "35156506",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@rasterweb",
        "url": "https://mastodon.social/@rasterweb",
        "photo": null
    },
    "url": "https://mastodon.social/@rasterweb/109866254221865437",
    "content": {
        "html": "<p>Psst. Hey you, remember that blog of yours? I looked at it. You last updated it in 2018 or maybe 2015. I dunno. it's been a while.</p><p>Things have changed since then\u2026</p><p>We\u2019re (re)building the Open Web. </p><p>Join us.</p><p>Publish a blog post. </p><p>Don\u2019t post things on Twitter, Facebook, or Instagram.</p><p>Fuck that corporate shit and write it in your own home!</p><p><a href=\"https://mastodon.social/tags/mastodon\">#<span>mastodon</span></a> <a href=\"https://mastodon.social/tags/fediverse\">#<span>fediverse</span></a> <a href=\"https://mastodon.social/tags/indieWeb\">#<span>indieWeb</span></a> <a href=\"https://mastodon.social/tags/rss\">#<span>rss</span></a> <a href=\"https://mastodon.social/tags/open\">#<span>open</span></a></p>",
        "text": "Psst. Hey you, remember that blog of yours? I looked at it. You last updated it in 2018 or maybe 2015. I dunno. it's been a while.Things have changed since then\u2026We\u2019re (re)building the Open Web. Join us.Publish a blog post. Don\u2019t post things on Twitter, Facebook, or Instagram.Fuck that corporate shit and write it in your own home!#mastodon #fediverse #indieWeb #rss #open"
    },
    "published": "2023-02-15T01:53:18+00:00",
    "post-type": "note",
    "_id": "35155854",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@syam",
        "url": "https://aana.site/@syam",
        "photo": null
    },
    "url": "https://aana.site/@syam/109864842105208919",
    "content": {
        "html": "<p>Finally! I discovered a simple <a href=\"https://aana.site/tags/indieweb\">#<span>indieweb</span></a> CMS! That too in <a href=\"https://aana.site/tags/PHP\">#<span>PHP</span></a> </p><p><a href=\"https://github.com/neopublished/neopub\"><span>https://</span><span>github.com/neopublished/neopub</span><span></span></a></p>",
        "text": "Finally! I discovered a simple #indieweb CMS! That too in #PHP https://github.com/neopublished/neopub"
    },
    "published": "2023-02-14T19:54:11+00:00",
    "post-type": "note",
    "_id": "35149072",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@accordionpolar",
        "url": "https://indieweb.social/@accordionpolar",
        "photo": null
    },
    "url": "https://indieweb.social/@accordionpolar/109864300568053717",
    "content": {
        "html": "<p>~ <a href=\"https://indieweb.social/tags/webrings\">#<span>webrings</span></a> watch ~<br />Posting a new way to connect with the indie web every day!</p><p>Day #12: Cuddler Webring <br /><a href=\"https://cuddler-webring.netlify.app/\"><span>https://</span><span>cuddler-webring.netlify.app/</span><span></span></a></p><p><a href=\"https://indieweb.social/tags/happyvalentinesday\">#<span>happyvalentinesday</span></a>  \ud83d\udc9e mincerafter42 has the perfect <a href=\"https://indieweb.social/tags/webring\">#<span>webring</span></a> for YOU! If you love cuddles, sign up! Show it some <a href=\"https://indieweb.social/tags/love\">#<span>love</span></a> </p><p><a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://indieweb.social/tags/website\">#<span>website</span></a> <a href=\"https://indieweb.social/tags/yesterweb\">#<span>yesterweb</span></a> <a href=\"https://indieweb.social/tags/web\">#<span>web</span></a> <a href=\"https://indieweb.social/tags/webdev\">#<span>webdev</span></a> <a href=\"https://indieweb.social/tags/smallweb\">#<span>smallweb</span></a> <a href=\"https://indieweb.social/tags/valentinesday\">#<span>valentinesday</span></a> <a href=\"https://indieweb.social/tags/valentines\">#<span>valentines</span></a></p>",
        "text": "~ #webrings watch ~\nPosting a new way to connect with the indie web every day!Day #12: Cuddler Webring \nhttps://cuddler-webring.netlify.app/#happyvalentinesday  \ud83d\udc9e mincerafter42 has the perfect #webring for YOU! If you love cuddles, sign up! Show it some #love #indieweb #website #yesterweb #web #webdev #smallweb #valentinesday #valentines"
    },
    "published": "2023-02-14T17:36:27+00:00",
    "post-type": "note",
    "_id": "35146662",
    "_source": "7235",
    "_is_read": false
}

iamjaco iamja.co

{
    "type": "entry",
    "author": {
        "name": "iamjaco",
        "url": "https://iamja.co",
        "photo": "https://www.gravatar.com/avatar/5e1905f7be027b59639edf49b72bd5ec?s=96&d=https%3A%2F%2Fmicro.blog%2Fimages%2Fblank_avatar.png"
    },
    "url": "https://www.iamja.co/2023/02/14/discover-the-indieweb.html",
    "content": {
        "html": "<p><a href=\"https://indieblog.page/\">Discover the IndieWeb, one blog post at a time.</a></p>",
        "text": "Discover the IndieWeb, one blog post at a time."
    },
    "published": "2023-02-14T12:25:40+00:00",
    "post-type": "note",
    "_id": "35143120",
    "_source": "7224",
    "_is_read": false
}

Jeremy Keith adactio.com

{
    "type": "entry",
    "published": "2023-02-14T08:07:28Z",
    "url": "https://adactio.com/links/19900",
    "category": [
        "mastodon",
        "twitter",
        "fediverse",
        "portable",
        "social",
        "networks",
        "portability",
        "babel",
        "genesis",
        "bible"
    ],
    "bookmark-of": [
        "https://www.wired.com/story/god-did-us-a-favor-by-destroying-twitter/"
    ],
    "content": {
        "text": "God Did the World a Favor by Destroying Twitter | WIRED\n\n\n\n\n  Our smarter, richer betters (in Babel times, the king\u2019s name was Nimrod) often preach the idea of a town square, a marketplace of ideas, a centralized hub of discourse and entertainment\u2014and we listen. But when I go back and read Genesis, I hear God saying: \u201cMy children, I designed your brains to scale to 150 stable relationships. Anything beyond that is overclocking. You should all try Mastodon.\u201d\n\n\nSo many gems in this piece by Paul Ford:\n\n\n  The Fediverse apps are all built on a set of rules called the ActivityPub standard, which is a little like HTML had sex with a calendar invite. It\u2019s a content polycule. The questions it evokes are the same as with any polycule: What are the rules? How big can this get? Who will create the chore chart?",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.wired.com/story/god-did-us-a-favor-by-destroying-twitter/\">\nGod Did the World a Favor by Destroying Twitter | WIRED\n</a>\n</h3>\n\n<blockquote>\n  <p>Our smarter, richer betters (in Babel times, the king\u2019s name was Nimrod) often preach the idea of a town square, a marketplace of ideas, a centralized hub of discourse and entertainment\u2014and we listen. But when I go back and read Genesis, I hear God saying: \u201cMy children, I designed your brains to scale to 150 stable relationships. Anything beyond that is overclocking. You should all try Mastodon.\u201d</p>\n</blockquote>\n\n<p>So many gems in this piece by Paul Ford:</p>\n\n<blockquote>\n  <p>The Fediverse apps are all built on a set of rules called the ActivityPub standard, which is a little like HTML had sex with a calendar invite. It\u2019s a content polycule. The questions it evokes are the same as with any polycule: What are the rules? How big can this get? Who will create the chore chart?</p>\n</blockquote>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Keith",
        "url": "https://adactio.com/",
        "photo": "https://adactio.com/images/photo-150.jpg"
    },
    "post-type": "bookmark",
    "_id": "35136104",
    "_source": "2",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@jlgatewood",
        "url": "https://mastodon.cloud/@jlgatewood",
        "photo": null
    },
    "url": "https://mastodon.cloud/@jlgatewood/109861536686030771",
    "content": {
        "html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://starrwulfe.xyz\">@<span>starrwulfe</span></a></span><br />I feel especially called out on the <a href=\"https://mastodon.cloud/tags/indieweb\">#<span>indieweb</span></a> one. I'm on my 3rd prototype architecture in as many months trying to find a decent blog home. \ud83d\ude3f</p>",
        "text": "@starrwulfe\nI feel especially called out on the #indieweb one. I'm on my 3rd prototype architecture in as many months trying to find a decent blog home. \ud83d\ude3f"
    },
    "published": "2023-02-14T05:53:34+00:00",
    "post-type": "note",
    "_id": "35131752",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@phil",
        "url": "https://wrestling.social/@phil",
        "photo": null
    },
    "url": "https://wrestling.social/@phil/109859033015652939",
    "content": {
        "html": "<p>This Saturday night is RetroStrange Movie Night! Watch some 1950s Hot Rod movies w/ us. No ads, no sign-in, no bullshit. RSMN is community-supported by our Patreon. <a href=\"https://retrostrange.com/2023/retrostrange-movie-night-is-february-18th/\"><span>https://</span><span>retrostrange.com/2023/retrostr</span><span>ange-movie-night-is-february-18th/</span></a> <a href=\"https://wrestling.social/tags/Movies\">#<span>Movies</span></a> <a href=\"https://wrestling.social/tags/Streaming\">#<span>Streaming</span></a> <a href=\"https://wrestling.social/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
        "text": "This Saturday night is RetroStrange Movie Night! Watch some 1950s Hot Rod movies w/ us. No ads, no sign-in, no bullshit. RSMN is community-supported by our Patreon. https://retrostrange.com/2023/retrostrange-movie-night-is-february-18th/ #Movies #Streaming #IndieWeb"
    },
    "published": "2023-02-13T19:16:51+00:00",
    "post-type": "note",
    "_id": "35120645",
    "_source": "7235",
    "_is_read": false
}