{
"type": "entry",
"author": {
"name": "@manifold",
"url": "https://plural.cafe/@manifold",
"photo": null
},
"url": "https://plural.cafe/@manifold/110470476962137283",
"content": {
"html": "<p>question about warnings/content notices when entering sites</p><p>i'm working on a static site which i also need to tell people upfront will have the Spicy Content (nudes, sexual topics, etc) in</p><p>would you find it better when visiting, to view</p><p>a homepage that prompts you and gives you a link to go forward, basically what i'm currently doing at <a href=\"https://mindmesh.link/\"><span>https://</span><span>mindmesh.link/</span><span></span></a></p><p>or</p><p>a javascript alert or MAYBE a more complicated popup, ideally only showing up once per device (i'll just, yk, use browser storage or something)</p><p>i'd kind of prefer to do the latter because it gives me more room to link to specific things, is the thing</p><p>(alternate suggestions or implementation ideas that are simple and work well on static sites welcome also)</p><p>(edit, i guess <a href=\"https://plural.cafe/tags/indieweb\">#<span>indieweb</span></a> is an appropriate tag here?)</p>",
"text": "question about warnings/content notices when entering sitesi'm working on a static site which i also need to tell people upfront will have the Spicy Content (nudes, sexual topics, etc) inwould you find it better when visiting, to viewa homepage that prompts you and gives you a link to go forward, basically what i'm currently doing at https://mindmesh.link/ora javascript alert or MAYBE a more complicated popup, ideally only showing up once per device (i'll just, yk, use browser storage or something)i'd kind of prefer to do the latter because it gives me more room to link to specific things, is the thing(alternate suggestions or implementation ideas that are simple and work well on static sites welcome also)(edit, i guess #indieweb is an appropriate tag here?)"
},
"published": "2023-06-01T18:55:05+00:00",
"post-type": "note",
"_id": "37631966",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@brianjesse",
"url": "https://mastodon.social/@brianjesse",
"photo": null
},
"url": "https://mastodon.social/@brianjesse/110471211703412591",
"content": {
"html": "<p>\"there was a time when the leading feed reader app required posts to have titles, and the leading microblogging site said they couldn't have them. That meant not only didn't they share data, they couldn't.\" <a href=\"http://textcasting.org/\"><span>http://</span><span>textcasting.org/</span><span></span></a> <a href=\"https://mastodon.social/tags/rss\">#<span>rss</span></a> <a href=\"https://mastodon.social/tags/activitypub\">#<span>activitypub</span></a> <a href=\"https://mastodon.social/tags/nostr\">#<span>nostr</span></a> <a href=\"https://mastodon.social/tags/bluesky\">#<span>bluesky</span></a> <a href=\"https://mastodon.social/tags/microblogging\">#<span>microblogging</span></a> <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodon.social/tags/webmention\">#<span>webmention</span></a> <a href=\"https://mastodon.social/tags/identica\">#<span>identica</span></a> <a href=\"https://mastodon.social/tags/ostatus\">#<span>ostatus</span></a> <a href=\"https://mastodon.social/tags/statusnet\">#<span>statusnet</span></a> <a href=\"https://mastodon.social/tags/appdotnet\">#<span>appdotnet</span></a></p>",
"text": "\"there was a time when the leading feed reader app required posts to have titles, and the leading microblogging site said they couldn't have them. That meant not only didn't they share data, they couldn't.\" http://textcasting.org/ #rss #activitypub #nostr #bluesky #microblogging #indieweb #webmention #identica #ostatus #statusnet #appdotnet"
},
"published": "2023-06-01T22:01:56+00:00",
"post-type": "note",
"_id": "37628855",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"published": "2023-05-31T17:53:48+00:00",
"url": "https://werd.io/2023/extinguishing-the-fediverse",
"category": [
"fediverse",
"NomadicIdentity"
],
"name": "Extinguishing the fediverse",
"content": {
"text": "I\u2019m soliciting prompts for discussion. This piece is a part of that series.\u00a0Erlend Sogge Heggen asks:There\u2019s legitimate reason to be worried about Meta\u2019s P92 project being part of a EEE play against the fediverse.How might the fediverse community counteract this, perhaps with its own EEE strategy?We know Meta will attempt an EEE play, but what if we play the reverse UNO card and EE(E) them instead?Embrace: Carefully federate in a minimum-viable fashion that doesn\u2019t overrun the existing #fediverse.Extend: Make #NomadicIdentity a reality, so accounts can be moved effortlessly.Extinguish: In case of misconduct, defederate and provide mass-migration assistance.First, some quick definitions!P92 is the codename for Meta / Facebook\u2019s new app that will support the same ActivityPub protocol as Mastodon and its cousins. Users will be able to log in with their Instagram credentials, and one can potentially (but not definitely) imagine it being folded into the mainline Instagram app.Embrace, Extend, Extinguish was a phrase coined internally inside Microsoft to describe its strategy with respect to the web. The idea was that the company would embrace open protocols, extend them with its own proprietary extensions, and then use its control over those extensions to extinguish competition. In particular, its plan was to do this with HTML in order to cement Internet Explorer as the web browser.Finally, the fediverse, of course, is the community of small, independently-owned, largely non-profit social networks that interoperate using shared protocols, on which Mastodon is the largest platform.There is legitimate concern that a company like Meta might attempt to control the fediverse. This is particularly true if they are allowed to create a uni-polar world: one where Meta is the only large company embracing these standards. In that world, Meta can throw hundreds of millions of users at the protocol, and it will instantly become its largest user.I think it\u2019s helpful to look at how Microsoft\u2019s EEE strategy failed. There were arguably two main factors: antitrust risk and competition.The Department of Justice sued Microsoft for monopolistic business practices, ultimately leading to a settlement where Microsoft capitulated to changing some of its approach in return for the DOJ dropping its desire to break up the company. It\u2019s not clear to me that this kind of case would or could take place with respect to Meta extinguishing the fediverse; while I\u2019m not a lawyer, I think the argument would probably be that many other social networks are available.The other thing that hurt Microsoft\u2019s dominance was Firefox. It was a good browser backed by a good community, but that wasn\u2019t the deciding factor; Firefox gained market share because Google pushed it at every possible opportunity. Because Internet Explorer\u2019s dominance was a business risk to Google, and because Firefox was built by a non-profit that was non-competitive with Google\u2019s business, it made financial sense to try and break Microsoft\u2019s stranglehold. Mozilla\u2019s model was stronger than its predecessor Netscape\u2019s had been: whereas Netscape needed to sell licenses, Mozilla\u2019s deal with Google meant it made money every time someone used Firefox to search for something on the web. There was almost no friction to its growth strategy.This activity led to a resurgence in a healthy ecosystem of standards-based web browsers for years \u2014 until Google decided to re-use the technique it had used on Firefox to push its own web browser. Even then, Chrome is a far better standards player than Internet Explorer ever was.There won\u2019t be hard evidence that Meta is adopting ActivityPub until we see its app in the wild. But if it is, that likely means that it sees the protocol as at least worth experimenting with, and maybe even as a potential threat. That\u2019s a sign of great progress, and everyone involved in building the fediverse should feel good about it.If Meta wants to own the fediverse, this isn\u2019t a battle that will be primarily won with features or technology. Easy-to-use platforms, nomadic identity that easily lets you move your presence from one provider to another, and assistance will all be essential, but they\u2019ll be table stakes. (If Meta is working on the platform today, it\u2019s probably also too late for truly nomadic identity to make a difference.) To really stand a chance, the fediverse will need the kind of marketing and go-to-market support that Firefox enjoyed back in the day. Which may mean support from another large player that considers Meta\u2019s ownership of the standard to be an existential risk.It\u2019s hard to see who that might be. Twitter is now the incompetence wing of the incompetence party. It\u2019s highly unlikely that networks like Pinterest care. Microsoft\u2019s platforms are tightly bound to its ecosystem, with access control at their core; I don\u2019t see LinkedIn joining the fediverse any time soon. Google has fallen on its face every time it\u2019s tried to build a social network, and runs YouTube as a separate entity that strongly benefits from closed ads. Salesforce might consider it a risk, as it provides social tools for businesses, which are easier to build and sell on an open social networking standard. Some of these entities might consider the fediverse to be worth exploring \u2014 but there\u2019s no clear technology backer. Cloudflare actually did provide its own Mastodon-compatible platform that runs on its CDN, but it hasn\u2019t seen anything like wide use. Medium has embraced Mastodon but has not deeply built support into its existing platform.Perhaps media companies, who generally live and die on the size of their audiences, and have often been beholden to the large social networks, might find themselves interested in embracing a social networking federation where they have more say and control. The rise of the fediverse certainly is a de-risking of their business models. But I don\u2019t think they see it yet; nor do I think they consider it their place to pick a winner. (Nor should it be, really, in practice.)Perhaps there can be another kind of backer: an entity that sees the existential thread centralized control of social media poses to democracy itself. We\u2019ve already seen how, left unchecked, centralized companies like Facebook incite genocides and throw elections. The fediverse can be an antidote to these trends \u2014 if we see it as a set of collaborating communities rather than simply the technology alone. The erosion of democracy, like monopolistic abuse of power, are human problems with human solutions rather than technological ones. Foundations and philanthropists may choose to provide this level of support, if they continue to see Meta as a threat to democracy.Building features will not protect the fediverse from being extinguished, although they may provide a useful baseline. It\u2019s going to take a whole different level of strategy, relationship-building, deal-making, and movement-building. I believe the fediverse is capable of doing this, as long as it doesn\u2019t mistake building software for making true progress.",
"html": "<p><em><img src=\"https://werd.io/file/647789a0b779bfd5d600c182/thumb.jpg\" alt=\"The Mastodon homepage, displayed on a smartphone\" width=\"1024\" height=\"683\" /></em></p><p><em>I\u2019m <a href=\"https://werd.io/2023/consider-me-your-personal-analyst\">soliciting prompts for discussion</a>. This piece is a part of that series.</em></p><p>\u00a0</p><p><a href=\"https://blog.erlend.sh\">Erlend Sogge Heggen</a> asks:</p><p><em>There\u2019s legitimate reason to be worried about Meta\u2019s P92 project being part of a EEE play against the fediverse.</em></p><p><em>How might the fediverse community counteract this, perhaps with its own EEE strategy?</em></p><p><em>We know Meta will attempt an EEE play, but what if we play the reverse UNO card and EE(E) them instead?</em></p><p><em>Embrace: Carefully federate in a minimum-viable fashion that doesn\u2019t overrun the existing <span><a href=\"https://werd.io/tag/fediverse\" class=\"p-category\">#fediverse</a></span>.</em></p><p><em>Extend: Make <span><a href=\"https://werd.io/tag/NomadicIdentity\" class=\"p-category\">#NomadicIdentity</a></span> a reality, so accounts can be moved effortlessly.</em></p><p><em>Extinguish: In case of misconduct, defederate and provide mass-migration assistance.</em></p><p>First, some quick definitions!</p><p><a href=\"https://www.engadget.com/meta-decentralized-twitter-competitor-071316333.html\">P92 is the codename for Meta / Facebook\u2019s new app that will support the same ActivityPub protocol as Mastodon and its cousins</a>. Users will be able to log in with their Instagram credentials, and one can potentially (but not definitely) imagine it being folded into the mainline Instagram app.</p><p><a href=\"https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish\">Embrace, Extend, Extinguish</a> was a phrase coined internally inside Microsoft to describe its strategy with respect to the web. The idea was that the company would embrace open protocols, extend them with its own proprietary extensions, and then use its control over those extensions to extinguish competition. In particular, its plan was to do this with HTML in order to cement Internet Explorer as <em>the</em> web browser.</p><p>Finally, <a href=\"https://en.wikipedia.org/wiki/Fediverse\">the fediverse</a>, of course, is the community of small, independently-owned, largely non-profit social networks that interoperate using shared protocols, on which <a href=\"https://joinmastodon.org/\">Mastodon</a> is the largest platform.</p><p>There is legitimate concern that a company like Meta might attempt to control the fediverse. This is particularly true if they are allowed to create a uni-polar world: one where Meta is the <em>only</em> large company embracing these standards. In that world, Meta can throw hundreds of millions of users at the protocol, and it will instantly become its largest user.</p><p>I think it\u2019s helpful to look at how Microsoft\u2019s EEE strategy failed. There were arguably two main factors: antitrust risk and competition.</p><p>The Department of Justice <a href=\"https://en.wikipedia.org/wiki/United_States_v._Microsoft_Corp.\">sued Microsoft for monopolistic business practices</a>, ultimately leading to a settlement where Microsoft capitulated to changing some of its approach in return for the DOJ dropping its desire to break up the company. It\u2019s not clear to me that this kind of case would or could take place with respect to Meta extinguishing the fediverse; while I\u2019m not a lawyer, I think the argument would probably be that many other social networks are available.</p><p>The other thing that hurt Microsoft\u2019s dominance was Firefox. It was a good browser backed by a good community, but that wasn\u2019t the deciding factor; Firefox gained market share because Google pushed it at every possible opportunity. Because Internet Explorer\u2019s dominance was a business risk to Google, and because Firefox was built by a non-profit that was non-competitive with Google\u2019s business, it made financial sense to try and break Microsoft\u2019s stranglehold. Mozilla\u2019s model was stronger than its predecessor Netscape\u2019s had been: whereas Netscape needed to sell licenses, Mozilla\u2019s deal with Google meant it made money every time someone used Firefox to search for something on the web. There was almost no friction to its growth strategy.</p><p>This activity led to a resurgence in a healthy ecosystem of standards-based web browsers for years \u2014 until Google decided to re-use the technique it had used on Firefox to push its own web browser. Even then, Chrome is a far better standards player than Internet Explorer ever was.</p><p>There won\u2019t be hard evidence that Meta is adopting ActivityPub until we see its app in the wild. But if it is, that likely means that it sees the protocol as at least worth experimenting with, and maybe even as a potential threat. That\u2019s a sign of great progress, and everyone involved in building the fediverse should feel good about it.</p><p>If Meta wants to <em>own</em> the fediverse, this isn\u2019t a battle that will be primarily won with features or technology. Easy-to-use platforms, nomadic identity that easily lets you move your presence from one provider to another, and assistance will all be essential, but they\u2019ll be table stakes. (If Meta is working on the platform today, it\u2019s probably also too late for truly nomadic identity to make a difference.) To really stand a chance, the fediverse will need the kind of marketing and go-to-market support that Firefox enjoyed back in the day. Which may mean support from another large player that considers Meta\u2019s ownership of the standard to be an existential risk.</p><p>It\u2019s hard to see who that might be. Twitter is now the incompetence wing of the incompetence party. It\u2019s highly unlikely that networks like Pinterest care. Microsoft\u2019s platforms are tightly bound to its ecosystem, with access control at their core; I don\u2019t see LinkedIn joining the fediverse any time soon. Google has fallen on its face every time it\u2019s tried to build a social network, and runs YouTube as a separate entity that strongly benefits from closed ads. Salesforce <em>might</em> consider it a risk, as it provides social tools for businesses, which are easier to build and sell on an open social networking standard. Some of these entities might consider the fediverse to be worth exploring \u2014 but there\u2019s no clear technology backer. <a href=\"https://blog.cloudflare.com/welcome-to-wildebeest-the-fediverse-on-cloudflare/\">Cloudflare actually did provide its own Mastodon-compatible platform</a> that runs on its CDN, but it hasn\u2019t seen anything like wide use. <a href=\"https://blog.medium.com/medium-embraces-mastodon-19dcb873eb11\">Medium has embraced Mastodon</a> but has not deeply built support into its existing platform.</p><p>Perhaps media companies, who generally live and die on the size of their audiences, and have often been beholden to the large social networks, might find themselves interested in embracing a social networking federation where they have more say and control. The rise of the fediverse certainly is a de-risking of their business models. But I don\u2019t think they see it yet; nor do I think they consider it their place to pick a winner. (Nor should it be, really, in practice.)</p><p>Perhaps there can be another kind of backer: an entity that sees the existential thread centralized control of social media poses to democracy itself. We\u2019ve already seen how, left unchecked, centralized companies like Facebook <a href=\"https://www.amnesty.org/en/latest/news/2022/09/myanmar-facebooks-systems-promoted-violence-against-rohingya-meta-owes-reparations-new-report/\">incite genocides</a> and <a href=\"https://time.com/5949210/facebook-misinformation-2020-election-report/\">throw elections</a>. The fediverse <a href=\"https://www.eff.org/deeplinks/2022/11/fediverse-could-be-awesome-if-we-dont-screw-it\">can be an antidote to these trends</a> \u2014 if we see it as a set of collaborating communities rather than simply the technology alone. The erosion of democracy, like monopolistic abuse of power, are human problems with human solutions rather than technological ones. Foundations and philanthropists may choose to provide this level of support, if they continue to see Meta as a threat to democracy.</p><p>Building features will not protect the fediverse from being extinguished, although they may provide a useful baseline. It\u2019s going to take a whole different level of strategy, relationship-building, deal-making, and movement-building. I believe the fediverse is capable of doing this, as long as it doesn\u2019t mistake building software for making true progress.</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": "37596982",
"_source": "191",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2023/05/31/introducing-nostr-crossposting.html",
"name": "Introducing Nostr cross-posting",
"content": {
"html": "<p>Similar to <a href=\"https://www.manton.org/2023/04/24/why-microblog-is.html\">my announcement last month about supporting Bluesky</a>, we\u2019re adding Nostr cross-posting to Micro.blog starting today. You can enable it under Account \u2192 Edit Sources & Cross-posting:</p>\n<img src=\"https://cdn.uploads.micro.blog/10/2023/09d7b90c8f.png\" width=\"600\" height=\"170\" alt=\"Screenshot with Nostr icon and add link.\" style=\"padding-bottom:0px;\" /><p>Nostr might have the most uncertain future among recent up-and-coming social web protocols. I\u2019m fascinated with the architecture because it\u2019s so different than ActivityPub, RSS, and IndieWeb protocols. I think it\u2019s interesting and worth tinkering with. I\u2019ve been personally using it through Micro.blog for about a week, so why not let other folks play with it too?</p>\n<p>Nostr is quite technical. If you don\u2019t want to be on the edge, feel free to wait. It\u2019s so early that using Nostr feels like testing a prototype, letting your blog posts loose into the wild west of the internet to float between Nostr \u201crelay\u201d servers.</p>\n<p>To get started, you will need a Nostr account. Unlike every other social network, in Nostr you don\u2019t actually register on a specific server. Your account is just a private key, which you will paste into Micro.blog. For iOS, I suggest using <a href=\"https://damus.io\">Damus</a> or <a href=\"https://nos.social\">Nos</a>. For the web, check out <a href=\"https://coracle.social\">Coracle</a>.</p>\n<p>These apps <a href=\"https://nostr.com/clients\">and others</a> will create your private key, name, and profile photo. Make sure to save your key in a password manager. If you lose it, you lose access to your account.</p>\n<p>Micro.blog\u2019s support for these emerging protocols is essentially one-way, pushing your blog posts out to people on other platforms. Later we will consider federation, where posts and replies from other platforms and brought into Micro.blog, like we already do for Mastodon and ActivityPub. I\u2019d like to see how much traction there is before we do more.</p>",
"text": "Similar to my announcement last month about supporting Bluesky, we\u2019re adding Nostr cross-posting to Micro.blog starting today. You can enable it under Account \u2192 Edit Sources & Cross-posting:\nNostr might have the most uncertain future among recent up-and-coming social web protocols. I\u2019m fascinated with the architecture because it\u2019s so different than ActivityPub, RSS, and IndieWeb protocols. I think it\u2019s interesting and worth tinkering with. I\u2019ve been personally using it through Micro.blog for about a week, so why not let other folks play with it too?\nNostr is quite technical. If you don\u2019t want to be on the edge, feel free to wait. It\u2019s so early that using Nostr feels like testing a prototype, letting your blog posts loose into the wild west of the internet to float between Nostr \u201crelay\u201d servers.\nTo get started, you will need a Nostr account. Unlike every other social network, in Nostr you don\u2019t actually register on a specific server. Your account is just a private key, which you will paste into Micro.blog. For iOS, I suggest using Damus or Nos. For the web, check out Coracle.\nThese apps and others will create your private key, name, and profile photo. Make sure to save your key in a password manager. If you lose it, you lose access to your account.\nMicro.blog\u2019s support for these emerging protocols is essentially one-way, pushing your blog posts out to people on other platforms. Later we will consider federation, where posts and replies from other platforms and brought into Micro.blog, like we already do for Mastodon and ActivityPub. I\u2019d like to see how much traction there is before we do more."
},
"published": "2023-05-31T11:21:09-05:00",
"category": [
"Photos",
"Essays"
],
"post-type": "article",
"_id": "37596251",
"_source": "12",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@arpcomics",
"url": "https://mythology.social/@arpcomics",
"photo": null
},
"url": "https://mythology.social/@arpcomics/110463051243855814",
"content": {
"html": "<p>Any chance <a href=\"https://mythology.social/tags/IvoryApp\">#<span>IvoryApp</span></a> works with <a href=\"https://mythology.social/tags/CalcKey\">#<span>CalcKey</span></a>? Ivory makes for a superior <a href=\"https://mythology.social/tags/Mastodon\">#<span>Mastodon</span></a> experience and I would miss the app.</p><p>Has anyone done any <a href=\"https://mythology.social/tags/IndieWeb\">#<span>IndieWeb</span></a> posting & commenting with <a href=\"https://mythology.social/tags/WordPress\">#<span>WordPress</span></a> & CalcKey?</p><p><a href=\"https://mythology.social/tags/Fediverse\">#<span>Fediverse</span></a></p>",
"text": "Any chance #IvoryApp works with #CalcKey? Ivory makes for a superior #Mastodon experience and I would miss the app.Has anyone done any #IndieWeb posting & commenting with #WordPress & CalcKey?#Fediverse"
},
"published": "2023-05-31T11:26:38+00:00",
"post-type": "note",
"_id": "37588128",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@voxpelli",
"url": "https://mastodon.social/@voxpelli",
"photo": null
},
"url": "https://mastodon.social/@voxpelli/110453933398696783",
"content": {
"html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://fosstodon.org/@softinio\">@<span>softinio</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://fosstodon.org/@linux_mclinuxface\">@<span>linux_mclinuxface</span></a></span> Or you know, focus on the open standards rather than on the implementations.</p><p>As long as a network is controlled by a single implementation it will be at the liberty of whoever controls that single implementation.</p><p><a href=\"https://indieweb.org/plurality\"><span>https://</span><span>indieweb.org/plurality</span><span></span></a></p><p><a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://mastodon.social/tags/IndieWebPrinciples\">#<span>IndieWebPrinciples</span></a></p>",
"text": "@softinio @linux_mclinuxface Or you know, focus on the open standards rather than on the implementations.As long as a network is controlled by a single implementation it will be at the liberty of whoever controls that single implementation.https://indieweb.org/plurality#IndieWeb #IndieWebPrinciples"
},
"published": "2023-05-29T20:47:50+00:00",
"post-type": "note",
"_id": "37552357",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@hl",
"url": "https://social.lol/@hl",
"photo": null
},
"url": "https://social.lol/@hl/110453921288154799",
"content": {
"html": "<p>Thanks to <span class=\"h-card\"><a class=\"u-url\" href=\"https://social.lol/@tldr\">@<span>tldr</span></a></span> for asking \"Why do you blog\", as I hadn't really thought hard about it before, but I think I've got an answer <a href=\"https://www.henryleach.com/2023/05/why-do-i-blog/\"><span>https://www.</span><span>henryleach.com/2023/05/why-do-</span><span>i-blog/</span></a> <a href=\"https://social.lol/tags/blog\">#<span>blog</span></a> <a href=\"https://social.lol/tags/writing\">#<span>writing</span></a> <a href=\"https://social.lol/tags/notes\">#<span>notes</span></a> <a href=\"https://social.lol/tags/indieweb\">#<span>indieweb</span></a></p>",
"text": "Thanks to @tldr for asking \"Why do you blog\", as I hadn't really thought hard about it before, but I think I've got an answer https://www.henryleach.com/2023/05/why-do-i-blog/ #blog #writing #notes #indieweb"
},
"published": "2023-05-29T20:44:46+00:00",
"post-type": "note",
"_id": "37552358",
"_source": "7235",
"_is_read": false
}
I’m testing Calckey to improve compatibility with Micro.blog. Some of the UI is quite busy and not for me, but I love how they are showing ActivityPub usernames, with the profile photo and dimmed domain name. Might borrow this.
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2023/05/29/im-testing-calckey.html",
"content": {
"html": "<p>I\u2019m testing <a href=\"https://calckey.social\">Calckey</a> to improve compatibility with Micro.blog. Some of the UI is quite busy and not for me, but I love how they are showing ActivityPub usernames, with the profile photo and dimmed domain name. Might borrow this.</p>\n<img src=\"https://cdn.uploads.micro.blog/10/2023/2fa3187a54.png\" width=\"600\" height=\"52\" alt=\"Screenshot of Calckey with usernames.\" />",
"text": "I\u2019m testing Calckey to improve compatibility with Micro.blog. Some of the UI is quite busy and not for me, but I love how they are showing ActivityPub usernames, with the profile photo and dimmed domain name. Might borrow this."
},
"published": "2023-05-29T10:51:51-05:00",
"category": [
"Photos"
],
"post-type": "note",
"_id": "37547509",
"_source": "12",
"_is_read": false
}
@tchambers@decius Also: #BlueSky, #Fediverse _and_ the #IndieWeb can learn from one another. The IndieWeb’s focus on plurality and composition of independent standards is worse from a PR perspective but better from a resiliency and innovation perspective
{
"type": "entry",
"author": {
"name": "@voxpelli",
"url": "https://mastodon.social/@voxpelli",
"photo": null
},
"url": "https://mastodon.social/@voxpelli/110447751745635022",
"content": {
"html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://indieweb.social/@tchambers\">@<span>tchambers</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://ioc.exchange/@decius\">@<span>decius</span></a></span> Also: <a href=\"https://mastodon.social/tags/BlueSky\">#<span>BlueSky</span></a>, <a href=\"https://mastodon.social/tags/Fediverse\">#<span>Fediverse</span></a> _and_ the <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> can learn from one another. The IndieWeb\u2019s focus on plurality and composition of independent standards is worse from a PR perspective but better from a resiliency and innovation perspective</p>",
"text": "@tchambers @decius Also: #BlueSky, #Fediverse _and_ the #IndieWeb can learn from one another. The IndieWeb\u2019s focus on plurality and composition of independent standards is worse from a PR perspective but better from a resiliency and innovation perspective"
},
"published": "2023-05-28T18:35:46+00:00",
"post-type": "note",
"_id": "37530190",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@miclgael",
"url": "https://mastodon.au/@miclgael",
"photo": null
},
"url": "https://mastodon.au/@miclgael/110445688698160921",
"content": {
"html": "<p>My first new blog post since 2021. \ud83d\ude05 </p><p>\"Welcome back!\" by Michael Gale</p><p><a href=\"https://www.michaelgale.dev/blog/welcome-back\"><span>https://www.</span><span>michaelgale.dev/blog/welcome-b</span><span>ack</span></a></p><p><a href=\"https://mastodon.au/tags/webdev\">#<span>webdev</span></a> <a href=\"https://mastodon.au/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodon.au/tags/blog\">#<span>blog</span></a> <a href=\"https://mastodon.au/tags/musicmonday\">#<span>musicmonday</span></a></p>",
"text": "My first new blog post since 2021. \ud83d\ude05 \"Welcome back!\" by Michael Galehttps://www.michaelgale.dev/blog/welcome-back#webdev #indieweb #blog #musicmonday"
},
"published": "2023-05-28T09:51:06+00:00",
"post-type": "note",
"_id": "37522575",
"_source": "7235",
"_is_read": false
}
I moved my personal site to it 5 years ago. From my blog post:
"I am also interested in exploring other open web technologies, like ActivityPub and OStatus. I’m not 100% convinced that Mastodon will take over Twitter, but there is a lot of promise in the ideas and technologies behind it."
{
"type": "entry",
"author": {
"name": "@stefan",
"url": "https://stefanbohacek.online/@stefan",
"photo": null
},
"url": "https://stefanbohacek.online/@stefan/110442903708441241",
"content": {
"html": "<p>WordPress is celebrating its 20th anniversary today!</p><p><a href=\"https://wordpress.org/news/2023/05/celebrating-20-years-of-wordpress/\"><span>https://</span><span>wordpress.org/news/2023/05/cel</span><span>ebrating-20-years-of-wordpress/</span></a></p><p>I moved my personal site to it 5 years ago. From my blog post:</p><p>\"I am also interested in exploring other open web technologies, like ActivityPub and OStatus. I\u2019m not 100% convinced that Mastodon will take over Twitter, but there is a lot of promise in the ideas and technologies behind it.\"</p><p><a href=\"https://stefanbohacek.com/blog/migrating-the-site-to-wordpress/\"><span>https://</span><span>stefanbohacek.com/blog/migrati</span><span>ng-the-site-to-wordpress/</span></a></p><p>There sure is!</p><p><a href=\"https://stefanbohacek.online/tags/WordPress\">#<span>WordPress</span></a> <a href=\"https://stefanbohacek.online/tags/anniversary\">#<span>anniversary</span></a> <a href=\"https://stefanbohacek.online/tags/OpenWeb\">#<span>OpenWeb</span></a> <a href=\"https://stefanbohacek.online/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://stefanbohacek.online/tags/ActivityPub\">#<span>ActivityPub</span></a> <a href=\"https://stefanbohacek.online/tags/mastodon\">#<span>mastodon</span></a> <a href=\"https://stefanbohacek.online/tags/fediverse\">#<span>fediverse</span></a></p>",
"text": "WordPress is celebrating its 20th anniversary today!https://wordpress.org/news/2023/05/celebrating-20-years-of-wordpress/I moved my personal site to it 5 years ago. From my blog post:\"I am also interested in exploring other open web technologies, like ActivityPub and OStatus. I\u2019m not 100% convinced that Mastodon will take over Twitter, but there is a lot of promise in the ideas and technologies behind it.\"https://stefanbohacek.com/blog/migrating-the-site-to-wordpress/There sure is!#WordPress #anniversary #OpenWeb #IndieWeb #ActivityPub #mastodon #fediverse"
},
"published": "2023-05-27T22:02:51+00:00",
"post-type": "note",
"_id": "37515054",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"published": "2023-05-27T15:00:13-0400",
"url": "https://martymcgui.re/2023/05/27/this-week-in-the-indieweb-audio-edition--may-20th---26th-2023/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://media.martymcgui.re/3e/8d/0d/98/5e3b86d0df11091f35df769be94afa4f512534cc2b3eda30486caeb9.mp3"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 May 20th - 26th, 2023",
"content": {
"text": "Show/Hide Transcript\n \n Recapping micro.camp and remapping social protocols. It\u2019s the audio edition for This Week in the IndieWeb for May 20th - 26th, 2023.\nYou can find all of my audio editions and subscribe with your favorite podcast app here: martymcgui.re/podcasts/indieweb/.\nMusic from Aaron Parecki\u2019s 100DaysOfMusic project: Day 85 - Suit, Day 48 - Glitch, Day 49 - Floating, Day 9, and Day 11\nThanks to everyone in the IndieWeb chat for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!",
"html": "Show/Hide Transcript\n \n <p>Recapping micro.camp and remapping social protocols. It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2023-05-26.html\">This Week in the IndieWeb for May 20th - 26th, 2023</a>.</p>\n<p>You can find all of my audio editions and subscribe with your favorite podcast app here: <a href=\"https://martymcgui.re/podcasts/indieweb/\">martymcgui.re/podcasts/indieweb/</a>.</p>\n<p>Music from <a href=\"https://aaronparecki.com/\">Aaron Parecki</a>\u2019s <a href=\"https://100.aaronparecki.com/\">100DaysOfMusic project</a>: <a href=\"https://aaronparecki.com/2017/03/15/14/day85\">Day 85 - Suit</a>, <a href=\"https://aaronparecki.com/2017/02/06/7/day48\">Day 48 - Glitch</a>, <a href=\"https://aaronparecki.com/2017/02/07/4/day49\">Day 49 - Floating</a>, <a href=\"https://aaronparecki.com/2016/12/29/21/day-9\">Day 9</a>, and <a href=\"https://aaronparecki.com/2016/12/31/15/\">Day 11</a></p>\n<p>Thanks to everyone in the <a href=\"https://chat.indieweb.org/\">IndieWeb chat</a> for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "audio",
"_id": "37514846",
"_source": "175",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://indieweb.social/tags/indieweb",
"photo": null
},
"url": "https://martymcgui.re/2023/05/27/150805/",
"content": {
"html": "<p>Recapping micro.camp and remapping social protocols. It\u2019s your < 10min update on the #IndieWeb community!</p><br /><p>This Week in the IndieWeb audio edition for May 20th - 26th, 2023.<br /><a href=\"https://martymcgui.re/2023/05/27/this-week-in-the-indieweb-audio-edition--may-20th---26th-2023/\">https://martymcgui.re/2023/05/27/this-week-in-the-indieweb-audio-edition--may-20th---26th-2023/</a></p>",
"text": "Recapping micro.camp and remapping social protocols. It\u2019s your < 10min update on the #IndieWeb community!\nThis Week in the IndieWeb audio edition for May 20th - 26th, 2023.\nhttps://martymcgui.re/2023/05/27/this-week-in-the-indieweb-audio-edition--may-20th---26th-2023/"
},
"published": "2023-05-27T19:08:05+00:00",
"post-type": "note",
"_id": "37512887",
"_source": "7235",
"_is_read": false
}
