Is there a reason to check out #BlueSky ? I feel like #Mastodon is a more robust Twitter clone with added elements. Going to BlueSky feels redundant. Though I hear it's more normie coded #indieweb #openweb #fediverse
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.social/@xavierhayesmuth/113258293502531144",
"content": {
"html": "<p>Is there a reason to check out <a href=\"https://mastodon.social/tags/BlueSky\">#<span>BlueSky</span></a> ? I feel like <a href=\"https://mastodon.social/tags/Mastodon\">#<span>Mastodon</span></a> is a more robust Twitter clone with added elements. Going to BlueSky feels redundant. Though I hear it's more normie coded <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodon.social/tags/openweb\">#<span>openweb</span></a> <a href=\"https://mastodon.social/tags/fediverse\">#<span>fediverse</span></a></p>",
"text": "Is there a reason to check out #BlueSky ? I feel like #Mastodon is a more robust Twitter clone with added elements. Going to BlueSky feels redundant. Though I hear it's more normie coded #indieweb #openweb #fediverse"
},
"published": "2024-10-06T03:13:30+00:00",
"post-type": "note",
"_id": "42460375",
"_source": "8007",
"_is_read": false
}
I'm trying to understand #indieweb #webmentions and see if it's worth adding to my site. I think I've set it up correctly, but can someone help me test it? Here's a URL I guess? https://www.lloydatkinson.net/posts/2024/stupid-problems-require-stupid-solutions-cloudflare-is-breaking-my-svgs/
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.social/@lloydjatkinson/113257826883254397",
"content": {
"html": "<p>I'm trying to understand <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodon.social/tags/webmentions\">#<span>webmentions</span></a> and see if it's worth adding to my site. I think I've set it up correctly, but can someone help me test it? Here's a URL I guess? <a href=\"https://www.lloydatkinson.net/posts/2024/stupid-problems-require-stupid-solutions-cloudflare-is-breaking-my-svgs/\"><span>https://www.</span><span>lloydatkinson.net/posts/2024/s</span><span>tupid-problems-require-stupid-solutions-cloudflare-is-breaking-my-svgs/</span></a></p>",
"text": "I'm trying to understand #indieweb #webmentions and see if it's worth adding to my site. I think I've set it up correctly, but can someone help me test it? Here's a URL I guess? https://www.lloydatkinson.net/posts/2024/stupid-problems-require-stupid-solutions-cloudflare-is-breaking-my-svgs/"
},
"published": "2024-10-06T01:14:50+00:00",
"post-type": "note",
"_id": "42459898",
"_source": "8007",
"_is_read": false
}
The original idea two years ago for what would become the Pages theme, intended to allow having your own social network via your website.
https://ovidem.com/blog/decentralized-twitter/
#socialmedia #indieweb #SmallWeb #smolweb
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.social/@indieaisle/113257733650948031",
"content": {
"html": "<p>The original idea two years ago for what would become the Pages theme, intended to allow having your own social network via your website.</p><p><a href=\"https://ovidem.com/blog/decentralized-twitter/\"><span>https://</span><span>ovidem.com/blog/decentralized-</span><span>twitter/</span></a><br /><a href=\"https://mastodon.social/tags/socialmedia\">#<span>socialmedia</span></a> <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodon.social/tags/SmallWeb\">#<span>SmallWeb</span></a> <a href=\"https://mastodon.social/tags/smolweb\">#<span>smolweb</span></a></p>",
"text": "The original idea two years ago for what would become the Pages theme, intended to allow having your own social network via your website.\n\nhttps://ovidem.com/blog/decentralized-twitter/\n#socialmedia #indieweb #SmallWeb #smolweb"
},
"published": "2024-10-06T00:51:07+00:00",
"post-type": "note",
"_id": "42459779",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"published": "2024-10-05T20:25:31+00:00",
"url": "https://werd.io/2024/the-two-fediverses",
"name": "The two Fediverses",
"content": {
"text": "I was tagged in\u00a0a fairly critical SocialHub post about the Social Web Foundation launch announcement. I wasn\u2019t in a position to add to the conversation then, but I\u2019ve been thinking about it all week.\n\nBefore I dive further, a reminder: I am not an employee or founder of the Social Web Foundation. I am in touch with the founders and have been an unpaid advisor, but I can\u2019t and don\u2019t speak for it. This post is mine alone, and doesn\u2019t necessarily reflect anyone else\u2019s opinions or ideas. I also haven\u2019t vetted or previewed it with anyone.\n\nThere are three main criticisms I\u2019ve seen of the Social Web Foundation:Meta is a partner\nIt\u2019s called The Social Web Foundation but is focused on ActivityPub, ignoring AT Protocol, Nostr, and other decentralized social web protocols that are emerging elsewhere\nIt\u2019s focused on substantially growing the Fediverse, which is not something everyone wants\nI believe they\u2019re interrelated, and that these differences can be overcome.Meta enters the chatPerhaps the biggest red flag to critics is Meta\u2019s presence as one of the SWF\u2019s thirteen launch partners. Many consider it to be an extremely negative force on the web. Its presence is certainly divisive. I\u2019ve been a critic of its Facebook product in particular since its inception: a company that imposes its centralized view of the world on the communications of its billions of users, and in the process has caused real harms.\n\nThose harms include potential mental health and social media addiction effects in teenagers, failing to protect LGBTQ users, and more \u2014 up to and including enabling a genocide.\n\nThe last claim might seem outlandish, but it\u2019s real. As Harvard Law School\u2019s Systemic Justice Project pointed out:Scholars, reporters, and United Nations investigators agree that the social media giant played a role in an explosion of ethnic conflict in 2017 that led to the death and displacement of hundreds of thousands Rohingya Muslims in Northern Myanmar.Given this, the argument goes, why would anyone \u2014 particularly an organization trying to build the future of the social web \u2014 even consider working with Meta? Doesn\u2019t its presence as a partner taint the work of the Foundation?\n\nAs the writer, researcher, and community lead Erin Kissane has pointed out:I think it\u2019s unwise to assume that an organization that has demonstrably and continuously made antisocial and sometimes deadly choices on behalf of billions of human beings and allowed its products to be weaponized by covert state-level operations behind multiple genocides and hundreds (thousands? tens of thousands?) of smaller persecutions, all while ducking meaningful oversight, lying about what they do and know, and treating their core extraction machines as fait-accompli inevitabilities that mustn\u2019t be governed except in patently ineffective ways will be a good citizen after adopting a new, interoperable technical structure.These profoundly negative impacts are possible because it is one of the most prominent \u2014 potentially the most prominent \u2014 platform owner on the internet. Around four billion users use one of Meta\u2019s products every month; that\u2019s half all the humans on earth, or around 75% of all the people in the world aged 15 or older. Arguably no platform should ever be allowed to become this big or influential (can any government claim to have this level of reach or insight into this many people?). Still, at least for now, here it is.\n\nFor many people, Meta is the internet. This clearly doesn\u2019t absolve aiding a genocide, throwing an election, or thwarting academic research, but it also makes Meta a platform owner that\u2019s hard to ignore.\n\nMeta sits in a position of influence over the social web. Threads, its fairly recent Twitter-like platform, is rolling out support for the ActivityPub standard that underlies the Fediverse, so it is poised to also be influential there. Once Threads supports the Fediverse bidirectionally, it will easily be the largest social platform on the network. It will consequently have an enormous amount of influence on how the network evolves, regardless of its participation in the Social Web Foundation.What is a successful Fediverse?Meta\u2019s involvement and potential dominance inevitably raises the question: What kind of future do we want for the Fediverse? Whether we focus on technical interoperability or grassroots social activism, the answer to this question will shape how we approach growth, inclusivity, and the role of large corporations in the decentralized web.\n\nIf you see the Fediverse as a way to interoperate between social networks, such that a user on one platform can communicate with a user on another, you might welcome a large tech company supporting the standard (a bit like one might have welcomed a company to standards-based HTML a generation ago). If, on the other hand, you see the Fediverse as an antidote to technology corporations or a movement that is more about a collaborative grassroots movement than pure technical interoperability \u2014 a sort of work of activism \u2014 you might be quite alarmed.\n\nThese mindsets are analogous to Evan Prodromou\u2019s Big Fedi / Small Fedi dichotomy, but I\u2019d like to apply a slightly different lens.If your model of the Fediverse is an interoperable standard that underpins all social networks:All parties should focus on a single technical standard in order ensure everyone can interoperate and the network can grow.\nThe focus should be on onboarding, education, and developer experience.\nGrowth is paramount. The goal is to bring the whole world in.\nHaving the creator of the biggest social network join is an opportunity.\nThe end state is likely a handful of very large social networks, followed by a significant long tail of small ones.\nFor ease of reference, let\u2019s call this the growth Fediverse.If your model of the Fediverse is a social movement intentionally set apart from corporate social media:A plurality of underlying protocols is allowable and maybe even desirable: the important thing is the support of grassroots communities outside the usual bounds of the tech industry.\nThe focus should be on equity, community dynamics, relationships, and movement-building in service of community.\nPreserving the values of the existing community is paramount. The rest of the world can stay away; there\u2019s no need for growth.\nThe presence of the largest corporate social media vendor is inherently a threat.\nThe end state is likely a collection of small, interoperable communities united by their desire for an alternative to \u201cbig tech\u201d.\nLet\u2019s call this one the movement Fediverse.\n\nBoth models of the Fediverse clearly exist. I\u2019m hardly the first to have discussed them, but the Social Web Foundation announcement has re-ignited the conversation.\n\nVery clearly, the Foundation is closer to the first model than the second. As such, people who don\u2019t care for that model have accused it of being an agent of oligarchy; of doing harm by partnering with Meta; of using the term \u201csocial web\u201d while focusing solely on ActivityPub.A false binaryThe thing is, the lines between these two paths are blurry. It\u2019s not necessarily an either-or. The priority for the first is growth of the network and a large, interoperable social web; the priority of the second is small, pro-social communities that exist outside of usual tech industry dynamics. Someone might well feel that the way to get to small, pro-social communities is as a by-product of interoperability, just as not everything on the web itself is corporate even though partners to the W3C body that defines web standards include Google and Amazon.\n\nSome of the things that the movement Fediverse wants are intrinsically important to the growth Fediverse. You can\u2019t grow a giant social network without caring about community safety, for example; over the two years since he acquired Twitter, Elon Musk has ably demonstrated that most users don\u2019t want to stick around on a platform where they don\u2019t feel safe. Community standards are therefore very important to any network that seeks to grow and retain users. Usability and accessibility are similarly vital: what use is a movement that is exclusionary to less-technical people, or, say, the visually-impaired? Any healthy network needs to support diverse voices and ensure that those authors are welcome. The list of shared values goes on.\n\nBut there are also undeniable differences. Hanging the needs of an anti-corporate social movement on a technology is a big ask. I\u2019m not critical of the values of the people who do \u2014 I largely share them \u2014 but I don\u2019t think you can reasonably expect everybody involved in a technology to have the same ideals.\n\nLike any community, the movement Fediverse also has areas where it, too, could benefit from introspection and growth in order to live up to its own values. Some parts of the community have struggled with inclusivity, particularly when onboarding marginalized users who wished to discuss systemic injustice openly. As Marcia X recounted in Logic(s):What took me aback regarding the fediverse is that my networks were mostly \u201cleftists\u201d and self-proclaimed radical thinkers regarding race, ableism, gender, patriarchy, sexuality, et cetera, and yet what I was being exposed to was a lot of naivet\u00e9 or hostility for questioning whiteness as a basis for many people\u2019s takes or approaches to these subject matters. And if I were to question or push back on their whiteness, I was often accused of being biased myself.While many people in the movement are already working hard to address these issues, more can be done to ensure that all users feel safe, heard, and respected. In some cases, the movement Fediverse has fallen short when it comes to fully supporting the lived experiences of new users, especially those from marginalized groups. However, there is clear potential \u2014 and growing momentum \u2014 to improve this. By continuing to evolve and actively listen to new voices, the movement Fediverse can better embody the values of inclusivity and social justice that it stands for. But there is work to do.\n\nIn other words, it\u2019s important to recognize that both groups have challenges to address. Each needs to continue working to ensure decisions are made inclusively, with an eye on the safety of users and the accessibility of communities. By recognizing these shared goals, there\u2019s a real opportunity for mutual learning and growth.\n\nEach has much to gain from each other. One doesn\u2019t need to be a subscriber to the growth Fediverse to enjoy gains from user experience research, technology onboarding, and outreach conducted there. Similarly, one doesn\u2019t need to subscribe to the ideals of the movement Fediverse to feel the benefit of their community dynamics and social goals. In fact, there may be a productive tension between the two that keeps each of their worst impulses in check. One might consider the movement Fediverse to be akin to a labor movement: a way for users to organize and advocate for stronger, safer, and more progressive community design. In turn, the growth Fediverse could be a check against becoming too insular and leaving the rest of the world out in the cold.\n\nWhile the movement and growth Fediverse may have differing approaches, both share a commitment to user safety, inclusivity, and decentralization. The question is not whether these goals are shared, but how best to achieve them.Moving forwardJust as unions create productive tensions in businesses that create better working conditions and higher productivity, I think the discussion between the movement Fediverse and the growth Fediverse has the potential to push the open social web further than might otherwise have been possible.\n\nThe checks and balances produced by an open debate between the two approaches are particularly useful when considering partners like Meta. The productive tension between these two visions could ensure that while larger platforms like Meta are held accountable, the values of grassroots communities \u2014 safety, inclusivity, and equity, for example \u2014 are not sacrificed in the pursuit of growth.\n\nIt\u2019s not a foregone conclusion that Meta will dominate how the Social Web Foundation is run, but it\u2019s also not a foregone conclusion that it won\u2019t. The Social Web Foundation clearly states in its mission statement (emphasis mine):A Fediverse that is controlled only by one company isn\u2019t really a Fediverse at all. We think a productive, creative and healthy Fediverse needs multiple providers, none of whom dominate the space.The goal is a multipolar federated social web. I think a large part of the solution is not to say this, but to show it: conduct meetings and make decisions with as much transparency as possible, so as to prove that Meta (and any other partner) is not dominant. By structurally providing as much sunlight as possible, allowing feedback and comment, and repeatedly demonstrating that this feedback is being considered and acted on where appropriate, both the potential harms and concerns from the movement Fediverse community can be reduced. Just as source code that is open to scrutiny is auditable and verifiable, decision-making process that are open to sunlight can be held accountable. Public meeting notes, decision documents, and so on, all help to support accountability.\n\nIn any event, the Social Web Foundation doesn\u2019t need to be the foundation to cover all views of what the Fediverse should be. It\u2019s a foundation that is going to try and do great work to expand the Fediverse. From its mission statement:We believe that increased use of the Fediverse has the potential to make all of our online social experiences better, as well as to create lots of new opportunities for creation and self-expression. So we\u2019re committed to growing the number of people using the Fediverse.As Evan Prodromou said in that SocialHub thread abut people who don\u2019t feel the Foundation represents them:We want a united social web, using a single protocol for internetwork communication. I\u2019d compare email, where proprietary LAN email protocols like Microsoft Exchange are gatewayed into the formal standard protocol SMTP. [\u2026] The SWF is not mandatory. People who want to do other things for the Fediverse should definitely do so. But I do want to extend the invitation for people who are interested to reach out.This doesn\u2019t have to be one size fits all. It\u2019s worth considering what organizing more concretely for the movement Fediverse looks like, and how it might intersect and act as a check on the growth Fediverse.\n\nIt\u2019s understandable that some in the movement Fediverse feel uncomfortable with large corporate platforms, particularly those with a history of past harms, joining the network. However, engaging with these platforms \u2014 rather than dismissing their involvement outright \u2014 may offer a unique opportunity to influence their practices and ensure they align with the values of the community. Constructive engagement with Meta and other large platforms could offer a unique opportunity for the movement Fediverse to influence how these entities engage with the broader social web, ensuring they uphold the values of safety, inclusivity, and equity.\n\nLikewise, ignoring the concerns of the movement Fediverse is not wise: these are valid ideas rooted in real experiences. The tech industry carries real systemic inequalities that go all the way back to its origins in military funding. Addressing those inequities is a prerequisite to the web reaching its potential as a way for everyone in the world to connect and learn from each other. Companies like Meta, as I\u2019ve explained at length above, have committed real harms as a byproduct of their priorities, business models, and funding partners. Grassroots communities that practice intentionality, activism, mutual aid, and radical equity have a lot to offer, and in many ways are models for how the world should be.\n\nThe movement Fediverse\u2019s emphasis on mutual aid, radical equity, and intentionality offers invaluable lessons for how the larger Fediverse \u2014 and even corporate actors \u2014 could operate. Practices like community-driven moderation, transparent governance, and prioritizing marginalized voices could help ensure that the Fediverse grows without losing its soul.\n\nEach group is approaching the problem in good faith. In the end, it\u2019s up to all of us to ensure that the future of the web remains decentralized, inclusive, and safe. We must continue to engage, advocate, and, most importantly, listen to one another as we navigate and build this space together. The Fediverse is made of pluralities: of implementations, communities, vendors, and visions of the future. That\u2019s at the heart of its beauty and its opportunity. The software interoperates; so should we.",
"html": "<p><img src=\"https://werd.io/file/6701a0b17545f00005051e82/thumb.jpg\" alt=\"Street art that reads: together, we create!\" width=\"1024\" height=\"576\" /></p><p>I was tagged in\u00a0<a href=\"https://socialhub.activitypub.rocks/t/socialwebfoundation-what-do-people-think/4564/42\">a fairly critical SocialHub post about the Social Web Foundation launch announcement</a>. I wasn\u2019t in a position to add to the conversation then, but I\u2019ve been thinking about it all week.</p><p>Before I dive further, a reminder: I am not an employee or founder of the Social Web Foundation. I <em>am</em> in touch with the founders and have been an unpaid advisor, but I can\u2019t and don\u2019t speak for it. This post is mine alone, and doesn\u2019t necessarily reflect anyone else\u2019s opinions or ideas. I also haven\u2019t vetted or previewed it with anyone.</p><p>There are three main criticisms I\u2019ve seen of the Social Web Foundation:</p><ul><li>Meta is a partner</li>\n<li>It\u2019s called <em>The Social Web Foundation</em> but is focused on ActivityPub, ignoring AT Protocol, Nostr, and other decentralized social web protocols that are emerging elsewhere</li>\n<li>It\u2019s focused on substantially growing the Fediverse, which is not something everyone wants</li>\n</ul><p>I believe they\u2019re interrelated, and that these differences can be overcome.</p><h3>Meta enters the chat</h3><p>Perhaps the biggest red flag to critics is Meta\u2019s presence as one of the SWF\u2019s thirteen launch partners. Many consider it to be an extremely negative force on the web. Its presence is certainly divisive. I\u2019ve been <a href=\"https://www.businessinsider.com/facebook-recruiter-brutal-rejection-ben-werdmuller-2018-10\">a critic of its Facebook product in particular</a> since its inception: a company that imposes its centralized view of the world on the communications of its billions of users, and in the process has caused real harms.</p><p>Those harms include <a href=\"https://www.washingtonpost.com/technology/2024/08/05/meta-lawsuit-teen-mental-health/\">potential mental health and social media addiction effects in teenagers</a>, <a href=\"https://www.rollingstone.com/culture/culture-features/meta-oversight-board-social-media-failing-lgbtq-1234947358/\">failing to protect LGBTQ users</a>, and more \u2014 up to and including enabling a genocide.</p><p>The last claim might seem outlandish, but it\u2019s real. <a href=\"https://systemicjustice.org/article/facebook-and-genocide-how-facebook-contributed-to-genocide-in-myanmar-and-why-it-will-not-be-held-accountable/\">As Harvard Law School\u2019s Systemic Justice Project pointed out</a>:</p><blockquote><p>Scholars, reporters, and United Nations investigators agree that the social media giant played a role in an explosion of ethnic conflict in 2017 that led to the death and displacement of hundreds of thousands Rohingya Muslims in Northern Myanmar.</p></blockquote><p>Given this, the argument goes, why would anyone \u2014 particularly an organization trying to build the future of the social web \u2014 even <em>consider</em> working with Meta? Doesn\u2019t its presence as a partner taint the work of the Foundation?</p><p><a href=\"https://erinkissane.com/untangling-threads\">As the writer, researcher, and community lead Erin Kissane has pointed out</a>:</p><blockquote><p>I think it\u2019s unwise to assume that an organization that has demonstrably and continuously made antisocial and sometimes deadly choices on behalf of billions of human beings and allowed its products to be weaponized by covert state-level operations behind multiple genocides and hundreds (thousands? tens of thousands?) of smaller persecutions, all while ducking meaningful oversight, lying about what they do and know, and treating their core extraction machines as fait-accompli inevitabilities that mustn\u2019t be governed except in patently ineffective ways will be a good citizen after adopting a new, interoperable technical structure.</p></blockquote><p>These profoundly negative impacts are possible because it is one of the most prominent \u2014 potentially <em>the </em>most prominent \u2014 platform owner on the internet. <a href=\"https://www.statista.com/statistics/947869/facebook-product-mau/#:~:text=During%20the%20fourth%20quarter%20of,compared%20to%20the%20previous%20quarter.\">Around four billion users use one of Meta\u2019s products every month</a>; that\u2019s half all the humans on earth, or around 75% of all the people in the world aged 15 or older. Arguably no platform should ever be allowed to become this big or influential (can any government claim to have this level of reach or insight into this many people?). Still, at least for now, here it is.</p><p>For many people, Meta <em>is</em> the internet. This clearly doesn\u2019t absolve aiding a genocide, <a href=\"https://www.theguardian.com/news/series/cambridge-analytica-files\">throwing an election</a>, or <a href=\"https://independenttechresearch.org/survey-metas-shutdown-of-crowdtangle-bad-for-the-public-interest/\">thwarting academic research</a>, but it also makes Meta a platform owner that\u2019s hard to ignore.</p><p>Meta sits in a position of influence over the social web. <a href=\"https://threads.net\">Threads</a>, its fairly recent Twitter-like platform, is rolling out support for the ActivityPub standard that underlies the Fediverse, so it is poised to <em>also</em> be influential there. Once Threads supports the Fediverse bidirectionally, it will easily be the largest social platform on the network. It will consequently have an enormous amount of influence on how the network evolves, regardless of its participation in the Social Web Foundation.</p><h3>What is a successful Fediverse?</h3><p>Meta\u2019s involvement and potential dominance inevitably raises the question: What kind of future do we want for the Fediverse? Whether we focus on technical interoperability or grassroots social activism, the answer to this question will shape how we approach growth, inclusivity, and the role of large corporations in the decentralized web.</p><p>If you see the Fediverse as a way to interoperate between social networks, such that a user on one platform can communicate with a user on another, you might welcome a large tech company supporting the standard (a bit like one might have welcomed a company to standards-based HTML a generation ago). If, on the other hand, you see the Fediverse as an antidote to technology corporations or a movement that is more about a collaborative grassroots movement than pure technical interoperability \u2014 a sort of work of activism \u2014 you might be quite alarmed.</p><p>These mindsets are analogous to Evan Prodromou\u2019s <a href=\"https://evanp.me/2023/12/26/big-fedi-small-fedi/\">Big Fedi / Small Fedi</a> dichotomy, but I\u2019d like to apply a slightly different lens.</p><h4>If your model of the Fediverse is an interoperable standard that underpins all social networks:</h4><ul><li>All parties should focus on a single technical standard in order ensure everyone can interoperate and the network can grow.</li>\n<li>The focus should be on onboarding, education, and developer experience.</li>\n<li>Growth is paramount. The goal is to bring the whole world in.</li>\n<li>Having the creator of the biggest social network join is an opportunity.</li>\n<li>The end state is likely a handful of very large social networks, followed by a significant long tail of small ones.</li>\n</ul><p>For ease of reference, let\u2019s call this the <em>growth Fediverse</em>.</p><h4>If your model of the Fediverse is a social movement intentionally set apart from corporate social media:</h4><ul><li>A plurality of underlying protocols is allowable and maybe even desirable: the important thing is the support of grassroots communities outside the usual bounds of the tech industry.</li>\n<li>The focus should be on equity, community dynamics, relationships, and movement-building in service of community.</li>\n<li>Preserving the values of the existing community is paramount. The rest of the world can stay away; there\u2019s no need for growth.</li>\n<li>The presence of the largest corporate social media vendor is inherently a threat.</li>\n<li>The end state is likely a collection of small, interoperable communities united by their desire for an alternative to \u201cbig tech\u201d.</li>\n</ul><p>Let\u2019s call this one the <em>movement Fediverse</em>.</p><p>Both models of the Fediverse clearly exist. I\u2019m hardly the first to have discussed them, but the Social Web Foundation announcement has re-ignited the conversation.</p><p>Very clearly, the Foundation is closer to the first model than the second. As such, people who don\u2019t care for that model have accused it of being an agent of oligarchy; of doing harm by partnering with Meta; of using the term \u201csocial web\u201d while focusing solely on ActivityPub.</p><h3>A false binary</h3><p>The thing is, the lines between these two paths are blurry. It\u2019s not necessarily an either-or. The priority for the first is growth of the network and a large, interoperable social web; the priority of the second is small, pro-social communities that exist outside of usual tech industry dynamics. Someone might well feel that the way to get to small, pro-social communities is as a by-product of interoperability, just as not everything on the web itself is corporate even though partners to the W3C body that defines web standards include Google and Amazon.</p><p>Some of the things that the movement Fediverse wants are intrinsically important to the growth Fediverse. You can\u2019t grow a giant social network without caring about community safety, for example; over the two years since he acquired Twitter, Elon Musk has ably demonstrated that <a href=\"https://www.nbcnews.com/tech/tech-news/fewer-people-using-elon-musks-x-struggles-keep-users-rcna144115\">most users don\u2019t want to stick around on a platform where they don\u2019t feel safe</a>. Community standards are therefore very important to any network that seeks to grow and retain users. Usability and accessibility are similarly vital: what use is a movement that is exclusionary to less-technical people, or, say, the visually-impaired? Any healthy network needs to support diverse voices and ensure that those authors are welcome. The list of shared values goes on.</p><p>But there are also undeniable differences. Hanging the needs of an anti-corporate social movement on a technology is a big ask. I\u2019m not critical of the values of the people who do \u2014 I largely share them \u2014 but I don\u2019t think you can reasonably expect everybody involved in a technology to have the same ideals.</p><p>Like any community, the movement Fediverse also has areas where it, too, could benefit from introspection and growth in order to live up to its own values. Some parts of the community have struggled with inclusivity, particularly when onboarding marginalized users who wished to discuss systemic injustice openly. <a href=\"https://logicmag.io/policy/blackness-in-the-fediverse-a-conversation-with-marcia-x/\">As Marcia X recounted in Logic(s)</a>:</p><blockquote><p>What took me aback regarding the fediverse is that my networks were mostly \u201cleftists\u201d and self-proclaimed radical thinkers regarding race, ableism, gender, patriarchy, sexuality, et cetera, and yet what I was being exposed to was a lot of naivet\u00e9 or hostility for questioning whiteness as a basis for many people\u2019s takes or approaches to these subject matters. And if I were to question or push back on their whiteness, I was often accused of being biased myself.</p></blockquote><p>While many people in the movement are already working hard to address these issues, more can be done to ensure that all users feel safe, heard, and respected. In some cases, the movement Fediverse has fallen short when it comes to fully supporting the lived experiences of new users, especially those from marginalized groups. However, there is clear potential \u2014 and growing momentum \u2014 to improve this. By continuing to evolve and actively listen to new voices, the movement Fediverse can better embody the values of inclusivity and social justice that it stands for. But there is work to do.</p><p>In other words, it\u2019s important to recognize that both groups have challenges to address. Each needs to continue working to ensure decisions are made inclusively, with an eye on the safety of users and the accessibility of communities. By recognizing these shared goals, there\u2019s a real opportunity for mutual learning and growth.</p><p>Each has much to gain from each other. One doesn\u2019t need to be a subscriber to the growth Fediverse to enjoy gains from user experience research, technology onboarding, and outreach conducted there. Similarly, one doesn\u2019t need to subscribe to the ideals of the movement Fediverse to feel the benefit of their community dynamics and social goals. In fact, there may be a productive tension between the two that keeps each of their worst impulses in check. One might consider the movement Fediverse to be akin to a labor movement: a way for users to organize and advocate for stronger, safer, and more progressive community design. In turn, the growth Fediverse could be a check against becoming too insular and leaving the rest of the world out in the cold.</p><p>While the movement and growth Fediverse may have differing approaches, both share a commitment to user safety, inclusivity, and decentralization. The question is not whether these goals are shared, but how best to achieve them.</p><h3>Moving forward</h3><p>Just as unions create productive tensions in businesses that create better working conditions and higher productivity, I think the discussion between the movement Fediverse and the growth Fediverse has the potential to push the open social web further than might otherwise have been possible.</p><p>The checks and balances produced by an open debate between the two approaches are particularly useful when considering partners like Meta. The productive tension between these two visions could ensure that while larger platforms like Meta are held accountable, the values of grassroots communities \u2014 safety, inclusivity, and equity, for example \u2014 are not sacrificed in the pursuit of growth.</p><p>It\u2019s not a foregone conclusion that Meta will dominate how the Social Web Foundation is run, but it\u2019s also not a foregone conclusion that it <em>won\u2019t</em>. <a href=\"https://socialwebfoundation.org/mission/\">The Social Web Foundation clearly states in its mission statement</a> (emphasis mine):</p><blockquote><p>A Fediverse that is controlled only by one company isn\u2019t really a Fediverse at all. <strong>We think a productive, creative and healthy Fediverse needs multiple providers, none of whom dominate the space.</strong></p></blockquote><p>The goal is a multipolar federated social web. I think a large part of the solution is not to <em>say</em> this, but to <em>show</em> it: conduct meetings and make decisions with as much transparency as possible, so as to <em>prove</em> that Meta (and any other partner) is not dominant. By structurally providing as much sunlight as possible, allowing feedback and comment, and repeatedly demonstrating that this feedback is being considered and acted on where appropriate, both the potential harms and concerns from the movement Fediverse community can be reduced. Just as source code that is open to scrutiny is auditable and verifiable, decision-making process that are open to sunlight can be held accountable. Public meeting notes, decision documents, and so on, all help to support accountability.</p><p>In any event, the Social Web Foundation doesn\u2019t need to be <em>the</em> foundation to cover all views of what the Fediverse should be. It\u2019s <em>a</em> foundation that is going to try and do great work to expand the Fediverse. <a href=\"https://socialwebfoundation.org/mission/\">From its mission statement</a>:</p><blockquote><p>We believe that increased use of the Fediverse has the potential to make all of our online social experiences better, as well as to create lots of new opportunities for creation and self-expression. So we\u2019re committed to growing the number of people using the Fediverse.</p></blockquote><p>As Evan Prodromou <a href=\"https://socialhub.activitypub.rocks/t/socialwebfoundation-what-do-people-think/4564/22?u=benwerd\">said in that SocialHub thread</a> abut people who don\u2019t feel the Foundation represents them:</p><blockquote><p>We want a united social web, using a single protocol for internetwork communication. I\u2019d compare email, where proprietary LAN email protocols like Microsoft Exchange are gatewayed into the formal standard protocol SMTP. [\u2026] The SWF is not mandatory. People who want to do other things for the Fediverse should definitely do so. But I do want to extend the invitation for people who are interested to reach out.</p></blockquote><p>This doesn\u2019t have to be one size fits all. It\u2019s worth considering what organizing more concretely for the movement Fediverse looks like, and how it might intersect and act as a check on the growth Fediverse.</p><p>It\u2019s understandable that some in the movement Fediverse feel uncomfortable with large corporate platforms, particularly those with a history of past harms, joining the network. However, engaging with these platforms \u2014 rather than dismissing their involvement outright \u2014 may offer a unique opportunity to influence their practices and ensure they align with the values of the community. Constructive engagement with Meta and other large platforms could offer a unique opportunity for the movement Fediverse to influence how these entities engage with the broader social web, ensuring they uphold the values of safety, inclusivity, and equity.</p><p>Likewise, ignoring the concerns of the movement Fediverse is not wise: these are valid ideas rooted in real experiences. The tech industry carries real systemic inequalities that go all the way back to its origins in military funding. Addressing those inequities is a prerequisite to the web reaching its potential as a way for everyone in the world to connect and learn from each other. Companies like Meta, as I\u2019ve explained at length above, have committed real harms as a byproduct of their priorities, business models, and funding partners. Grassroots communities that practice intentionality, activism, mutual aid, and radical equity have a lot to offer, and in many ways are models for how the world should be.</p><p>The movement Fediverse\u2019s emphasis on mutual aid, radical equity, and intentionality offers invaluable lessons for how the larger Fediverse \u2014 and even corporate actors \u2014 could operate. Practices like community-driven moderation, transparent governance, and prioritizing marginalized voices could help ensure that the Fediverse grows without losing its soul.</p><p>Each group is approaching the problem in good faith. In the end, it\u2019s up to all of us to ensure that the future of the web remains decentralized, inclusive, and safe. We must continue to engage, advocate, and, most importantly, listen to one another as we navigate and build this space together. The Fediverse is made of pluralities: of implementations, communities, vendors, and visions of the future. That\u2019s at the heart of its beauty and its opportunity. The software interoperates; so should we.</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": "42458760",
"_source": "191",
"_is_read": false
}
Who all here is also active on #SpaceHey? Looking for some friends over there. I intend to use it for long form casual posts/shit posts that appropriate to post on the personal blog I'm developing lol
Also, is there any ways to connect #Mastodon and #SpaceHey profiles/posts outside of certified links? #indieweb #openweb #fediverse
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.social/@xavierhayesmuth/113256459066434443",
"content": {
"html": "<p>Who all here is also active on <a href=\"https://mastodon.social/tags/SpaceHey\">#<span>SpaceHey</span></a>? Looking for some friends over there. I intend to use it for long form casual posts/shit posts that appropriate to post on the personal blog I'm developing lol </p><p>Also, is there any ways to connect <a href=\"https://mastodon.social/tags/Mastodon\">#<span>Mastodon</span></a> and <a href=\"https://mastodon.social/tags/SpaceHey\">#<span>SpaceHey</span></a> profiles/posts outside of certified links? <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodon.social/tags/openweb\">#<span>openweb</span></a> <a href=\"https://mastodon.social/tags/fediverse\">#<span>fediverse</span></a></p>",
"text": "Who all here is also active on #SpaceHey? Looking for some friends over there. I intend to use it for long form casual posts/shit posts that appropriate to post on the personal blog I'm developing lol \n\nAlso, is there any ways to connect #Mastodon and #SpaceHey profiles/posts outside of certified links? #indieweb #openweb #fediverse"
},
"published": "2024-10-05T19:26:58+00:00",
"post-type": "note",
"_id": "42457911",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mstdn.ca/@kgadams/113256082821182681",
"content": {
"html": "<p><a href=\"https://mstdn.ca/tags/safari\">#<span>safari</span></a> <a href=\"https://mstdn.ca/tags/chrome\">#<span>chrome</span></a> <a href=\"https://mstdn.ca/tags/wordpress\">#<span>wordpress</span></a> <a href=\"https://mstdn.ca/tags/themes\">#<span>themes</span></a> <a href=\"https://mstdn.ca/tags/twentyfourteen\">#<span>twentyfourteen</span></a> <a href=\"https://mstdn.ca/tags/oceanwp\">#<span>oceanwp</span></a> <a href=\"https://mstdn.ca/tags/webmention\">#<span>webmention</span></a> <a href=\"https://mstdn.ca/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mstdn.ca/tags/sidebars\">#<span>sidebars</span></a> <a href=\"https://mstdn.ca/tags/ubergeekkellysworld\">#<span>ubergeekkellysworld</span></a></p><p><a href=\"https://www.kgadams.net/sitenews/site-design-refresh-completed\"><span>https://www.</span><span>kgadams.net/sitenews/site-desi</span><span>gn-refresh-completed</span></a></p>",
"text": "#safari #chrome #wordpress #themes #twentyfourteen #oceanwp #webmention #indieweb #sidebars #ubergeekkellysworld\n\nhttps://www.kgadams.net/sitenews/site-design-refresh-completed"
},
"published": "2024-10-05T17:51:17+00:00",
"post-type": "note",
"_id": "42457119",
"_source": "8007",
"_is_read": false
}
I've been meaning for a while to migrate my web site to a static site generator. Started poking at that project in earnest in late June if file dates are to be believed. (Sounds plausible.)
The events of the last several days have certainly made me quite a bit more inclined to get that project sorted.
I'm getting closer...
(My goal is that a regular visitor to my web site basically shouldn't know that anything has changed. Including anyone following my blog via the Atom feed.)
#IndieWeb
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://social.mkj.earth/@mkj/113255378444068613",
"content": {
"html": "<p>I've been meaning for a while to migrate my web site to a static site generator. Started poking at that project in earnest in late June if file dates are to be believed. (Sounds plausible.)</p><p>The events of the last several days have certainly made me quite a bit more inclined to get that project sorted.</p><p>I'm getting closer...</p><p>(My goal is that a regular visitor to my web site basically shouldn't know that anything has changed. Including anyone following my blog via the Atom feed.)</p><p><a href=\"https://social.mkj.earth/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
"text": "I've been meaning for a while to migrate my web site to a static site generator. Started poking at that project in earnest in late June if file dates are to be believed. (Sounds plausible.)\n\nThe events of the last several days have certainly made me quite a bit more inclined to get that project sorted.\n\nI'm getting closer...\n\n(My goal is that a regular visitor to my web site basically shouldn't know that anything has changed. Including anyone following my blog via the Atom feed.)\n\n#IndieWeb"
},
"published": "2024-10-05T14:52:09+00:00",
"post-type": "note",
"_id": "42455616",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.social/@hgdarshankumar/113255090771082935",
"content": {
"html": "<p>Hello <a href=\"https://mastodon.social/tags/Mastodon\">#<span>Mastodon</span></a>!<br /><a href=\"https://youtube.com/shorts/JR1JbfaM4vs?si=6KeqFwnbTb0WmT1t\"><span>https://</span><span>youtube.com/shorts/JR1JbfaM4vs</span><span>?si=6KeqFwnbTb0WmT1t</span></a></p><p>Check out this amazing dance video featuring Vicky Kaushal, Triptii Dimri, and Karan Aujla! Tauba Tauba is a must-watch! <a href=\"https://mastodon.social/tags/TaubaTauba\">#<span>TaubaTauba</span></a> <a href=\"https://mastodon.social/tags/BadNewz\">#<span>BadNewz</span></a> <a href=\"https://mastodon.social/tags/bollywooddance\">#<span>bollywooddance</span></a> <a href=\"https://mastodon.social/tags/DanceChallenge\">#<span>DanceChallenge</span></a> <br /><a href=\"https://mastodon.social/tags/vickykaushal\">#<span>vickykaushal</span></a> <br /><a href=\"https://mastodon.social/tags/karanaujla\">#<span>karanaujla</span></a> <br /><a href=\"https://mastodon.social/tags/triptiidimri\">#<span>triptiidimri</span></a> <br /><a href=\"https://mastodon.social/tags/Mastodon\">#<span>Mastodon</span></a> <br /><a href=\"https://mastodon.social/tags/Fediverse\">#<span>Fediverse</span></a> <br /><a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <br /><a href=\"https://mastodon.social/tags/Privacy\">#<span>Privacy</span></a> <br /><a href=\"https://mastodon.social/tags/Art\">#<span>Art</span></a> <br /><a href=\"https://mastodon.social/tags/Writing\">#<span>Writing</span></a> <br /><a href=\"https://mastodon.social/tags/Photography\">#<span>Photography</span></a> <br /><a href=\"https://mastodon.social/tags/Music\">#<span>Music</span></a> <br /><a href=\"https://mastodon.social/tags/Gaming\">#<span>Gaming</span></a> <br /><a href=\"https://mastodon.social/tags/Science\">#<span>Science</span></a></p>",
"text": "Hello #Mastodon!\nhttps://youtube.com/shorts/JR1JbfaM4vs?si=6KeqFwnbTb0WmT1t\n\nCheck out this amazing dance video featuring Vicky Kaushal, Triptii Dimri, and Karan Aujla! Tauba Tauba is a must-watch! #TaubaTauba #BadNewz #bollywooddance #DanceChallenge \n#vickykaushal \n#karanaujla \n#triptiidimri \n#Mastodon \n#Fediverse \n#IndieWeb \n#Privacy \n#Art \n#Writing \n#Photography \n#Music \n#Gaming \n#Science"
},
"published": "2024-10-05T13:39:00+00:00",
"photo": [
"https://files.mastodon.social/media_attachments/files/113/255/089/232/807/327/original/ee9e0844b1f4817a.jpg"
],
"post-type": "photo",
"_id": "42455382",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://nerdculture.de/@gisiger/113254947907826754",
"content": {
"html": "<p>This is an excellent idea by <span class=\"h-card\"><a class=\"u-url\" href=\"https://social.lol/@amerpie\">@<span>amerpie</span></a></span>! I will participate next week \ud83d\udc4d\ud83c\udffb</p><p><a href=\"https://louplummer.lol/an-appreciation-challenge-spread-the-love/\"><span>https://</span><span>louplummer.lol/an-appreciation</span><span>-challenge-spread-the-love/</span></a></p><p>via <span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@feedle\">@<span>feedle</span></a></span> </p><p><a href=\"https://nerdculture.de/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://nerdculture.de/tags/smolweb\">#<span>smolweb</span></a> <a href=\"https://nerdculture.de/tags/blogging\">#<span>blogging</span></a></p>\n<a class=\"u-mention\" href=\"https://mastodon.social/@feedle\"></a>\n<a class=\"u-mention\" href=\"https://social.lol/@amerpie\"></a>",
"text": "This is an excellent idea by @amerpie! I will participate next week \ud83d\udc4d\ud83c\udffb\n\nhttps://louplummer.lol/an-appreciation-challenge-spread-the-love/\n\nvia @feedle \n\n#indieweb #smolweb #blogging"
},
"published": "2024-10-05T13:03:04+00:00",
"post-type": "note",
"_id": "42454927",
"_source": "8007",
"_is_read": false
}
No matter where you look on #Mastodon, you will never escape one of the following:
- #Linux power users
- #Weebs
- #Transgirls
- #Furry gooners
- #Liberal journalist/lawyer
- Disillusioned #sysadmin
- Bright-eyed #IT student
- Memelords with expert level #shitposts
- Niche #indieweb sites
- #bots with mildly-entertaining-to-insanely-annoying automated feeds
and last but not least:
- Wine moms with blogs just having fun đ
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.social/@xavierhayesmuth/113251603967329318",
"content": {
"html": "<p>No matter where you look on <a href=\"https://mastodon.social/tags/Mastodon\">#<span>Mastodon</span></a>, you will never escape one of the following: </p><p>- <a href=\"https://mastodon.social/tags/Linux\">#<span>Linux</span></a> power users<br />- <a href=\"https://mastodon.social/tags/Weebs\">#<span>Weebs</span></a><br />- <a href=\"https://mastodon.social/tags/Transgirls\">#<span>Transgirls</span></a> <br />- <a href=\"https://mastodon.social/tags/Furry\">#<span>Furry</span></a> gooners <br />- <a href=\"https://mastodon.social/tags/Liberal\">#<span>Liberal</span></a> journalist/lawyer<br />- Disillusioned <a href=\"https://mastodon.social/tags/sysadmin\">#<span>sysadmin</span></a> <br />- Bright-eyed <a href=\"https://mastodon.social/tags/IT\">#<span>IT</span></a> student<br />- Memelords with expert level <a href=\"https://mastodon.social/tags/shitposts\">#<span>shitposts</span></a> <br />- Niche <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> sites<br />- <a href=\"https://mastodon.social/tags/bots\">#<span>bots</span></a> with mildly-entertaining-to-insanely-annoying automated feeds</p><p>and last but not least:<br /><br />- Wine moms with blogs just having fun \ud83d\ude0a</p>",
"text": "No matter where you look on #Mastodon, you will never escape one of the following: \n\n- #Linux power users\n- #Weebs\n- #Transgirls \n- #Furry gooners \n- #Liberal journalist/lawyer\n- Disillusioned #sysadmin \n- Bright-eyed #IT student\n- Memelords with expert level #shitposts \n- Niche #indieweb sites\n- #bots with mildly-entertaining-to-insanely-annoying automated feeds\n\nand last but not least:\n\n- Wine moms with blogs just having fun \ud83d\ude0a"
},
"published": "2024-10-04T22:52:15+00:00",
"post-type": "note",
"_id": "42450113",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.social/@jelloeater/113251222233949381",
"content": {
"html": "<p><a href=\"https://ooh.directory\"><span>https://</span><span>ooh.directory</span><span></span></a></p><p><span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@OohDirectory\">@<span>OohDirectory</span></a></span> I just found you folks from <span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@jimniels\">@<span>jimniels</span></a></span> <br />Sooo coooooollllll!!!!<br /><a href=\"https://mastodon.social/tags/SmallWeb\">#<span>SmallWeb</span></a> <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a></p>\n<a class=\"u-mention\" href=\"https://mastodon.social/@OohDirectory\"></a>\n<a class=\"u-mention\" href=\"https://mastodon.social/@jimniels\"></a>",
"text": "https://ooh.directory\n\n@OohDirectory I just found you folks from @jimniels \nSooo coooooollllll!!!!\n#SmallWeb #indieweb"
},
"published": "2024-10-04T21:15:11+00:00",
"post-type": "note",
"_id": "42449548",
"_source": "8007",
"_is_read": false
}
Trombei com o novo sĂtio da desenvolvedora e artista chinesa Nic Chan, e agora quero deixar o meu sistema operacional com essa cara 8-bit/ Macintosh/ #pixelart.
Ă uma Ăłtima pedida para quem quer se inspirar em configurar um sĂtio pessoal. Funciona sem Javascript, mas habilitĂĄ-lo vale a pena.
Um #SurfandoWeb via The Jolly Teapot.
#indieweb
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://social.harpia.red/objects/4b593b57-ff84-4607-ba11-48e7405419c3",
"content": {
"html": "<p>Trombei com o <a href=\"https://www.nicchan.me\">novo s\u00edtio da desenvolvedora e artista chinesa Nic Chan</a>, e agora quero deixar o meu sistema operacional com essa cara <em>8-bit</em>/ Macintosh/ <a href=\"https://social.harpia.red/tag/pixelart\">#pixelart</a>.</p><p>\u00c9 uma \u00f3tima pedida para quem quer se inspirar em configurar um s\u00edtio pessoal. Funciona sem Javascript, mas habilit\u00e1-lo vale a pena.</p><p>Um <a href=\"https://social.harpia.red/tag/surfandoweb\">#SurfandoWeb</a> via <a href=\"http://thejollyteapot.com/september-2024-blend\">The Jolly Teapot</a>.</p><p><a href=\"https://social.harpia.red/tag/indieweb\">#indieweb</a></p>",
"text": "Trombei com o novo s\u00edtio da desenvolvedora e artista chinesa Nic Chan, e agora quero deixar o meu sistema operacional com essa cara 8-bit/ Macintosh/ #pixelart.\n\n\u00c9 uma \u00f3tima pedida para quem quer se inspirar em configurar um s\u00edtio pessoal. Funciona sem Javascript, mas habilit\u00e1-lo vale a pena.\n\nUm #SurfandoWeb via The Jolly Teapot.\n\n#indieweb"
},
"published": "2024-10-04T19:08:49+00:00",
"post-type": "note",
"_id": "42448529",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.social/@RobertaFidora/113250660615711328",
"content": {
"html": "<p>Has anyone created a Buy Music Club page for <a href=\"https://mastodon.social/tags/music\">#<span>music</span></a> from the <a href=\"https://mastodon.social/tags/Fediverse\">#<span>Fediverse</span></a>? </p><p><a href=\"https://www.buymusic.club\"><span>https://www.</span><span>buymusic.club</span><span></span></a> </p><p><a href=\"https://mastodon.social/tags/BandcampFriday\">#<span>BandcampFriday</span></a> <a href=\"https://mastodon.social/tags/Bandcamp\">#<span>Bandcamp</span></a> <a href=\"https://mastodon.social/tags/FediArt\">#<span>FediArt</span></a> <a href=\"https://mastodon.social/tags/FediMusic\">#<span>FediMusic</span></a> <a href=\"https://mastodon.social/tags/Mastodon\">#<span>Mastodon</span></a> <a href=\"https://mastodon.social/tags/MastoMusic\">#<span>MastoMusic</span></a> <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
"text": "Has anyone created a Buy Music Club page for #music from the #Fediverse? \n\nhttps://www.buymusic.club \n\n#BandcampFriday #Bandcamp #FediArt #FediMusic #Mastodon #MastoMusic #IndieWeb"
},
"published": "2024-10-04T18:52:21+00:00",
"post-type": "note",
"_id": "42448530",
"_source": "8007",
"_is_read": false
}
In een van de hoekjes van het internet wordt maandelijks het Indieweb Carnaval gevierd. De organisator noemt een thema, (onafhankelijke) bloggers schrijven er op los.
Deze maand is meertaligheid het onderwerp. Het internet spreekt Engels en dit weblog Nederlands (op een enkele post na waarvan ik denk dat het zinvol is een vertaalde versie te schrijven). Het gevolg is dat het aantal [âŚ]
https://www.filmvanalledag.nl/2024/10/04/lingua-franca/
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://www.filmvanalledag.nl/2024/10/04/lingua-franca/",
"content": {
"html": "<p>In een van de hoekjes van het internet wordt maandelijks het Indieweb Carnaval gevierd. De organisator noemt een thema, (onafhankelijke) bloggers schrijven er op los. </p><p>Deze maand is meertaligheid het onderwerp. Het internet spreekt Engels en dit weblog Nederlands (op een enkele post na waarvan ik denk dat het zinvol is een vertaalde versie te schrijven). Het gevolg is dat het aantal [\u2026]</p><p><a href=\"https://www.filmvanalledag.nl/2024/10/04/lingua-franca/\">https://www.filmvanalledag.nl/2024/10/04/lingua-franca/</a></p>",
"text": "In een van de hoekjes van het internet wordt maandelijks het Indieweb Carnaval gevierd. De organisator noemt een thema, (onafhankelijke) bloggers schrijven er op los. \n\nDeze maand is meertaligheid het onderwerp. Het internet spreekt Engels en dit weblog Nederlands (op een enkele post na waarvan ik denk dat het zinvol is een vertaalde versie te schrijven). Het gevolg is dat het aantal [\u2026]\n\nhttps://www.filmvanalledag.nl/2024/10/04/lingua-franca/"
},
"published": "2024-10-04T18:12:08+00:00",
"post-type": "note",
"_id": "42447931",
"_source": "8007",
"_is_read": false
}
I tend to agree with @github.com/mantonâs comment and analysis.
As Manton points out, there are many of us now, many implementers and publishers that are implementing and supporting multiple protocols, and thus it matters to us that we at least maintain the level of compatibility and interoperability that we achieved in the initial Recommendations of these specifications.
I think we can continue to do that, especially if we scope the Working Group to being a maintenance WG for the existing specs. This is something that Evan has convinced me of, while previously I saw a renewed Social Web WG to work on new features. Given the progress with use of extensions, and the Fed ID CG/WG stages process (or something like it), that seems like a better way to pursue new features, in parallel in the Social CG.
Another benefit of one Social Web working group is that its scope is easier to determine and explain, both to prior participants, and to W3C Members who will be voting on its creation.
A renewal of a working group to do maintenance on all of its prior specs, both editorial and bug fixes, makes a lot of sense to W3C and to Members, who like seeing working groups that take up the responsibility of maintaining specs. This especially makes more sense when all those specifications have far more implementations now than when they were shipped by the prior working group!
As I saw in another blog post about the social web, we are all here on âteam openâ, and I think we suffer, collectively, by attempting to draw lines with any âActivityPub-onlyâ approach. Both because it unnecessarily divides a very diverse, mixed, and broader âActivtyPub supportingâ community, and because itâs much fuzzier, to the point of overlapping with adjacent and aligned efforts.
The rel=me specification is a good example of this overlap. Would that be included in an âActivityPub-onlyâ approach? Because itâs certainly used by communities beyond that.
We have a whole task force on HTML Discovery in the CG where some of us (myself included) is working on improving rel=author support when interacting between HTML representations of profiles, yes, often with microformats, and retrieving the JSON(-LD) Activity Streams 2 versions of those profiles. That sort of interoperability benefits from a more inclusive approach.
We have bridges (https://fed.brid.gy/) that have helped the âActvityPub-verseâ grow that we could only dream about during the prior Social Web WG, because that group put in the hard work of figuring out interoperability across protocols and formats. We already did that hard work so why squander it? A maintenance group for all our specs provides a venue for any marginal bits of small work we may (or may not) need to maintain the positive outcomes of all that prior hard work.
Lastly, @github.com/gobengo brings up important concerns that I think merit explicitly addressing, regarding âexperience in the SocialWG from 2013-2017â (actually 2014-2018 per https://www.w3.org/wiki/Socialwg)
First, in summary I will say as the saying goes âDon't fight the last warâ, or I prefer a non-violent expression instead: âDonât argue the prior debatesâ.
We were in a very different situation at the start of the first Social Web Working Group, having emerged from an incredibly diverse âW3C Workshop on Social Standards: The Future of Businessâ (AKA osfw3c) in 2013.
The first Social Web WG had to evaluate numerous prior group efforts (17+) and different approaches (~15) that were proposed by members of the group for consideration before narrowing down to ~3 approaches. Lots of time was spent doing this, which we would obviously avoid by sticking to maintenance of existing specs.
We also found so much in common that we were able to leverage as building blocks and points of compatibility. HTTP & link rel discovery. URLs for profiles. Etc. the list goes on.
All of that is pointing out how the first Social Web WG was very different than what a similarly scoped Social Web WG could be like today.
Second, the other strong point of more recent evidence that we should use instead of fearing âthe last warâ, is how the Social CG has been conducted for the past 5-6 years, especially the past few years mostly chaired by Dmitri.
Every Social CG meeting I have been to has been incredibly positive & productive. Even when we disagree, we do so in very civil, polite, informed ways that consider each otherâs use-cases, perspectives, opinions, with folks working on different projects and protocols! It has been an incredible experience and I am grateful to be a part of it, and especially grateful for Dmitriâs stewardship. I mentioned this briefly in a post after a recent meeting https://tantek.com/2024/216/t1/socialcg-telcon.
With the Social CG, under Dmitriâs chairing, we have found a new more harmonious rhythm, and frankly, broader inclusiveness of different efforts and communities than we ever had previously. We have proven we can have regular meetings that âcontinue[s] the work of the W3C Social Web Working Groupâ where agenda items are curated and prioritized in a manner that respects the time and interests of the participants.
I would expect the harmony of the Social Web CG to continue in a similar renewed Social Web WG, and would support Dmitri as a co-chair of that working group to keep our momentum going. In addition, I would ask anyone else wanting to co-chair to learn from and adopt Dmitriâs chairing workmode accordingly. I believe that is our best path to success for this community, and for all our collective goals.
References:
* https://www.w3.org/wiki/SocialCG
* https://www.w3.org/wiki/SocialWG
* https://indieweb.org/2013/osfw3c
{
"type": "entry",
"published": "2024-10-04 08:40-0700",
"url": "http://tantek.com/2024/278/t2/",
"in-reply-to": [
"https://github.com/swicg/potential-charters/pull/3"
],
"content": {
"text": "I tend to agree with @github.com/manton\u2019s comment and analysis.\n\nAs Manton points out, there are many of us now, many implementers and publishers that are implementing and supporting multiple protocols, and thus it matters to us that we at least maintain the level of compatibility and interoperability that we achieved in the initial Recommendations of these specifications.\n\nI think we can continue to do that, especially if we scope the Working Group to being a maintenance WG for the existing specs. This is something that Evan has convinced me of, while previously I saw a renewed Social Web WG to work on new features. Given the progress with use of extensions, and the Fed ID CG/WG stages process (or something like it), that seems like a better way to pursue new features, in parallel in the Social CG.\n\nAnother benefit of one Social Web working group is that its scope is easier to determine and explain, both to prior participants, and to W3C Members who will be voting on its creation.\n\nA renewal of a working group to do maintenance on all of its prior specs, both editorial and bug fixes, makes a lot of sense to W3C and to Members, who like seeing working groups that take up the responsibility of maintaining specs. This especially makes more sense when all those specifications have far more implementations now than when they were shipped by the prior working group!\n\nAs I saw in another blog post about the social web, we are all here on \u201cteam open\u201d, and I think we suffer, collectively, by attempting to draw lines with any \u201cActivityPub-only\u201d approach. Both because it unnecessarily divides a very diverse, mixed, and broader \u201cActivtyPub supporting\u201d community, and because it\u2019s much fuzzier, to the point of overlapping with adjacent and aligned efforts.\n\nThe rel=me specification is a good example of this overlap. Would that be included in an \u201cActivityPub-only\u201d approach? Because it\u2019s certainly used by communities beyond that.\n\nWe have a whole task force on HTML Discovery in the CG where some of us (myself included) is working on improving rel=author support when interacting between HTML representations of profiles, yes, often with microformats, and retrieving the JSON(-LD) Activity Streams 2 versions of those profiles. That sort of interoperability benefits from a more inclusive approach.\n\nWe have bridges (https://fed.brid.gy/) that have helped the \u201cActvityPub-verse\u201d grow that we could only dream about during the prior Social Web WG, because that group put in the hard work of figuring out interoperability across protocols and formats. We already did that hard work so why squander it? A maintenance group for all our specs provides a venue for any marginal bits of small work we may (or may not) need to maintain the positive outcomes of all that prior hard work.\n\nLastly, @github.com/gobengo brings up important concerns that I think merit explicitly addressing, regarding \u201cexperience in the SocialWG from 2013-2017\u201d (actually 2014-2018 per https://www.w3.org/wiki/Socialwg)\n\nFirst, in summary I will say as the saying goes \u201cDon't fight the last war\u201d, or I prefer a non-violent expression instead: \u201cDon\u2019t argue the prior debates\u201d.\n\nWe were in a very different situation at the start of the first Social Web Working Group, having emerged from an incredibly diverse \u201cW3C Workshop on Social Standards: The Future of Business\u201d (AKA osfw3c) in 2013.\n\nThe first Social Web WG had to evaluate numerous prior group efforts (17+) and different approaches (~15) that were proposed by members of the group for consideration before narrowing down to ~3 approaches. Lots of time was spent doing this, which we would obviously avoid by sticking to maintenance of existing specs.\n\nWe also found so much in common that we were able to leverage as building blocks and points of compatibility. HTTP & link rel discovery. URLs for profiles. Etc. the list goes on.\n\nAll of that is pointing out how the first Social Web WG was very different than what a similarly scoped Social Web WG could be like today.\n\nSecond, the other strong point of more recent evidence that we should use instead of fearing \u201cthe last war\u201d, is how the Social CG has been conducted for the past 5-6 years, especially the past few years mostly chaired by Dmitri.\n\nEvery Social CG meeting I have been to has been incredibly positive & productive. Even when we disagree, we do so in very civil, polite, informed ways that consider each other\u2019s use-cases, perspectives, opinions, with folks working on different projects and protocols! It has been an incredible experience and I am grateful to be a part of it, and especially grateful for Dmitri\u2019s stewardship. I mentioned this briefly in a post after a recent meeting https://tantek.com/2024/216/t1/socialcg-telcon.\n\nWith the Social CG, under Dmitri\u2019s chairing, we have found a new more harmonious rhythm, and frankly, broader inclusiveness of different efforts and communities than we ever had previously. We have proven we can have regular meetings that \u201ccontinue[s] the work of the W3C Social Web Working Group\u201d where agenda items are curated and prioritized in a manner that respects the time and interests of the participants. \n\nI would expect the harmony of the Social Web CG to continue in a similar renewed Social Web WG, and would support Dmitri as a co-chair of that working group to keep our momentum going. In addition, I would ask anyone else wanting to co-chair to learn from and adopt Dmitri\u2019s chairing workmode accordingly. I believe that is our best path to success for this community, and for all our collective goals.\n\nReferences:\n* https://www.w3.org/wiki/SocialCG\n* https://www.w3.org/wiki/SocialWG\n* https://indieweb.org/2013/osfw3c",
"html": "I tend to agree with <a href=\"https://github.com/manton\">@github.com/manton</a>\u2019s comment and analysis.<br /><br />As Manton points out, there are many of us now, many implementers and publishers that are implementing and supporting multiple protocols, and thus it matters to us that we at least maintain the level of compatibility and interoperability that we achieved in the initial Recommendations of these specifications.<br /><br />I think we can continue to do that, especially if we scope the Working Group to being a maintenance WG for the existing specs. This is something that Evan has convinced me of, while previously I saw a renewed Social Web WG to work on new features. Given the progress with use of extensions, and the Fed ID CG/WG stages process (or something like it), that seems like a better way to pursue new features, in parallel in the Social CG.<br /><br />Another benefit of one Social Web working group is that its scope is easier to determine and explain, both to prior participants, and to W3C Members who will be voting on its creation.<br /><br />A renewal of a working group to do maintenance on all of its prior specs, both editorial and bug fixes, makes a lot of sense to W3C and to Members, who like seeing working groups that take up the responsibility of maintaining specs. This especially makes more sense when all those specifications have far more implementations now than when they were shipped by the prior working group!<br /><br />As I saw in another blog post about the social web, we are all here on \u201cteam open\u201d, and I think we suffer, collectively, by attempting to draw lines with any \u201cActivityPub-only\u201d approach. Both because it unnecessarily divides a very diverse, mixed, and broader \u201cActivtyPub supporting\u201d community, and because it\u2019s much fuzzier, to the point of overlapping with adjacent and aligned efforts.<br /><br />The rel=me specification is a good example of this overlap. Would that be included in an \u201cActivityPub-only\u201d approach? Because it\u2019s certainly used by communities beyond that.<br /><br />We have a whole task force on HTML Discovery in the CG where some of us (myself included) is working on improving rel=author support when interacting between HTML representations of profiles, yes, often with microformats, and retrieving the JSON(-LD) Activity Streams 2 versions of those profiles. That sort of interoperability benefits from a more inclusive approach.<br /><br />We have bridges (<a href=\"https://fed.brid.gy/\">https://fed.brid.gy/</a>) that have helped the \u201cActvityPub-verse\u201d grow that we could only dream about during the prior Social Web WG, because that group put in the hard work of figuring out interoperability across protocols and formats. We already did that hard work so why squander it? A maintenance group for all our specs provides a venue for any marginal bits of small work we may (or may not) need to maintain the positive outcomes of all that prior hard work.<br /><br />Lastly, <a href=\"https://github.com/gobengo\">@github.com/gobengo</a> brings up important concerns that I think merit explicitly addressing, regarding \u201cexperience in the SocialWG from 2013-2017\u201d (actually 2014-2018 per <a href=\"https://www.w3.org/wiki/Socialwg\">https://www.w3.org/wiki/Socialwg</a>)<br /><br />First, in summary I will say as the saying goes \u201cDon't fight the last war\u201d, or I prefer a non-violent expression instead: \u201cDon\u2019t argue the prior debates\u201d.<br /><br />We were in a very different situation at the start of the first Social Web Working Group, having emerged from an incredibly diverse \u201cW3C Workshop on Social Standards: The Future of Business\u201d (AKA osfw3c) in 2013.<br /><br />The first Social Web WG had to evaluate numerous prior group efforts (17+) and different approaches (~15) that were proposed by members of the group for consideration before narrowing down to ~3 approaches. Lots of time was spent doing this, which we would obviously avoid by sticking to maintenance of existing specs.<br /><br />We also found so much in common that we were able to leverage as building blocks and points of compatibility. HTTP & link rel discovery. URLs for profiles. Etc. the list goes on.<br /><br />All of that is pointing out how the first Social Web WG was very different than what a similarly scoped Social Web WG could be like today.<br /><br />Second, the other strong point of more recent evidence that we should use instead of fearing \u201cthe last war\u201d, is how the Social CG has been conducted for the past 5-6 years, especially the past few years mostly chaired by Dmitri.<br /><br />Every Social CG meeting I have been to has been incredibly positive & productive. Even when we disagree, we do so in very civil, polite, informed ways that consider each other\u2019s use-cases, perspectives, opinions, with folks working on different projects and protocols! It has been an incredible experience and I am grateful to be a part of it, and especially grateful for Dmitri\u2019s stewardship. I mentioned this briefly in a post after a recent meeting <a href=\"https://tantek.com/2024/216/t1/socialcg-telcon\">https://tantek.com/2024/216/t1/socialcg-telcon</a>.<br /><br />With the Social CG, under Dmitri\u2019s chairing, we have found a new more harmonious rhythm, and frankly, broader inclusiveness of different efforts and communities than we ever had previously. We have proven we can have regular meetings that \u201ccontinue[s] the work of the W3C Social Web Working Group\u201d where agenda items are curated and prioritized in a manner that respects the time and interests of the participants. <br /><br />I would expect the harmony of the Social Web CG to continue in a similar renewed Social Web WG, and would support Dmitri as a co-chair of that working group to keep our momentum going. In addition, I would ask anyone else wanting to co-chair to learn from and adopt Dmitri\u2019s chairing workmode accordingly. I believe that is our best path to success for this community, and for all our collective goals.<br /><br />References:<br />* <a href=\"https://www.w3.org/wiki/SocialCG\">https://www.w3.org/wiki/SocialCG</a><br />* <a href=\"https://www.w3.org/wiki/SocialWG\">https://www.w3.org/wiki/SocialWG</a><br />* <a href=\"https://indieweb.org/2013/osfw3c\">https://indieweb.org/2013/osfw3c</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "reply",
"refs": {
"https://github.com/swicg/potential-charters/pull/3": {
"type": "entry",
"url": "https://github.com/swicg/potential-charters/pull/3",
"name": "pull request 3 to GitHub project \u201cpotential-charters\u201d",
"post-type": "article"
}
},
"_id": "42447061",
"_source": "1",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mstdn.social/@the_cheis/113249965024365387",
"content": {
"html": "<p>Nuevo post:</p><p>Marcadores #1</p><p><a href=\"https://mstdn.social/tags/internet\">#<span>internet</span></a> <a href=\"https://mstdn.social/tags/blogs\">#<span>blogs</span></a> <a href=\"https://mstdn.social/tags/blogging\">#<span>blogging</span></a> <a href=\"https://mstdn.social/tags/web\">#<span>web</span></a> <a href=\"https://mstdn.social/tags/curation\">#<span>curation</span></a> <a href=\"https://mstdn.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mstdn.social/tags/enmiblog\">#<span>enmiblog</span></a></p><p><a href=\"https://thecheis.com/2024/10/04/marcadores-1/\"><span>https://</span><span>thecheis.com/2024/10/04/marcad</span><span>ores-1/</span></a></p>",
"text": "Nuevo post:\n\nMarcadores #1\n\n#internet #blogs #blogging #web #curation #indieweb #enmiblog\n\nhttps://thecheis.com/2024/10/04/marcadores-1/"
},
"published": "2024-10-04T15:55:27+00:00",
"post-type": "note",
"_id": "42446793",
"_source": "8007",
"_is_read": false
}
âď¸ Mentions United ... 3, 2, 1, Go
At some point, you write something yourself. In this case, a JavaScript solution to unite blog posts with their interactions on the #socialweb and beyond...
#indieweb #fediverse #interactions #javascript
https://kiko.io/post/Mentions-United-3-2-1-go/
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://indieweb.social/@kiko/113248737015518151",
"content": {
"html": "<p>\u270d\ufe0f Mentions United ... 3, 2, 1, Go</p><p>At some point, you write something yourself. In this case, a JavaScript solution to unite blog posts with their interactions on the <a href=\"https://indieweb.social/tags/socialweb\">#<span>socialweb</span></a> and beyond...</p><p><a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://indieweb.social/tags/fediverse\">#<span>fediverse</span></a> <a href=\"https://indieweb.social/tags/interactions\">#<span>interactions</span></a> <a href=\"https://indieweb.social/tags/javascript\">#<span>javascript</span></a> </p><p><a href=\"https://kiko.io/post/Mentions-United-3-2-1-go/\"><span>https://</span><span>kiko.io/post/Mentions-United-3</span><span>-2-1-go/</span></a></p>",
"text": "\u270d\ufe0f Mentions United ... 3, 2, 1, Go\n\nAt some point, you write something yourself. In this case, a JavaScript solution to unite blog posts with their interactions on the #socialweb and beyond...\n\n#indieweb #fediverse #interactions #javascript \n\nhttps://kiko.io/post/Mentions-United-3-2-1-go/"
},
"published": "2024-10-04T10:43:09+00:00",
"post-type": "note",
"_id": "42443870",
"_source": "8007",
"_is_read": false
}
Reminder that I write about a lot of stuff, blindness, life stuff, my author news. I never stick to 1 topic so if you wanna follow, my RSS feed is https://robertkingett.com/feed/ #RSS #Blog #IndieWeb
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://tweesecake.social/@weirdwriter/113248622439815678",
"content": {
"html": "<p>Reminder that I write about a lot of stuff, blindness, life stuff, my author news. I never stick to 1 topic so if you wanna follow, my RSS feed is <a href=\"https://robertkingett.com/feed/\"><span>https://</span><span>robertkingett.com/feed/</span><span></span></a> <a href=\"https://tweesecake.social/tags/RSS\">#<span>RSS</span></a> <a href=\"https://tweesecake.social/tags/Blog\">#<span>Blog</span></a> <a href=\"https://tweesecake.social/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
"text": "Reminder that I write about a lot of stuff, blindness, life stuff, my author news. I never stick to 1 topic so if you wanna follow, my RSS feed is https://robertkingett.com/feed/ #RSS #Blog #IndieWeb"
},
"published": "2024-10-04T10:14:01+00:00",
"post-type": "note",
"_id": "42443569",
"_source": "8007",
"_is_read": false
}
Looks like Libre.fm, an open-software version of Last.fm by the GNU Project, is being reworked to support ActivityPub!
https://roadmap.libre.fm
#LibreFM #LastFM #Fediverse #SocialWeb #IndieWeb #ActivityPub #GNU #GNUProject #Music #FediMusic
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.moule.world/@MOULE/113248290568082105",
"content": {
"html": "<p>Looks like Libre.fm, an open-software version of Last.fm by the GNU Project, is being reworked to support ActivityPub!</p><p><a href=\"https://roadmap.libre.fm\"><span>https://</span><span>roadmap.libre.fm</span><span></span></a></p><p><a href=\"https://mastodon.moule.world/tags/LibreFM\">#<span>LibreFM</span></a> <a href=\"https://mastodon.moule.world/tags/LastFM\">#<span>LastFM</span></a> <a href=\"https://mastodon.moule.world/tags/Fediverse\">#<span>Fediverse</span></a> <a href=\"https://mastodon.moule.world/tags/SocialWeb\">#<span>SocialWeb</span></a> <a href=\"https://mastodon.moule.world/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://mastodon.moule.world/tags/ActivityPub\">#<span>ActivityPub</span></a> <a href=\"https://mastodon.moule.world/tags/GNU\">#<span>GNU</span></a> <a href=\"https://mastodon.moule.world/tags/GNUProject\">#<span>GNUProject</span></a> <a href=\"https://mastodon.moule.world/tags/Music\">#<span>Music</span></a> <a href=\"https://mastodon.moule.world/tags/FediMusic\">#<span>FediMusic</span></a></p>",
"text": "Looks like Libre.fm, an open-software version of Last.fm by the GNU Project, is being reworked to support ActivityPub!\n\nhttps://roadmap.libre.fm\n\n#LibreFM #LastFM #Fediverse #SocialWeb #IndieWeb #ActivityPub #GNU #GNUProject #Music #FediMusic"
},
"published": "2024-10-04T08:49:37+00:00",
"photo": [
"https://files.mastodon.social/cache/media_attachments/files/113/248/290/947/128/669/original/5e23ab29c4f18788.png"
],
"post-type": "photo",
"_id": "42442925",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://jlelse.blog/thoughts/2024/10/multilingualism",
"content": {
"html": "<p><strong>IndieWeb Carnival: multilingualism in a global Web</strong></p><br /><br /><p><a href=\"https://jlelse.blog/thoughts/2024/10/multilingualism\"><span>https://</span><span>jlelse.blog/thoughts/2024/10/m</span><span>ultilingualism</span></a></p>",
"text": "IndieWeb Carnival: multilingualism in a global Web\n\nhttps://jlelse.blog/thoughts/2024/10/multilingualism"
},
"published": "2024-10-04T06:19:12+00:00",
"post-type": "note",
"_id": "42441947",
"_source": "8007",
"_is_read": false
}