Notices tagged with fediverse, page 2
-
Tantek ()'s status on Sunday, 24-Sep-2023 21:33:00 EDT 
Tantek
I recently wrote a high level summary blog post:
W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023
https://tantek.com/2023/262/b1/w3c-technical-plenary-tpac
of my time at the #W3C (@W3.org, @w3c@w3c.social, @W3C) #TPAC the week before.
Posting this note to explicitly #hashtag that article with topics mentioned therein:
#Sevilla #Seville #Spain #WICG #SocialCG #SWICG #Fediverse #SocialWeb #sustainability #IndieWeb #ActivityPub
because I forgot to put explicit categories (p-category markup) in the article post.
Adding that markup after publishing, and then sending an ActivityPub update (via #BridgyFed) is apparently not enough for #Mastodon to notice that the Update has new tags to display and aggregate on tag pages. In my next #w3cTPAC article post I’ll be sure to include category markup before publishing and see if that works.
Post glossary:
article post
https://indieweb.org/article
note post
https://indieweb.org/note
p-category
https://indieweb.org/p-category
tags
https://indieweb.org/tags -
Tantek ()'s status on Monday, 11-Sep-2023 19:06:00 EDT
Tantek
going to the #SocialWeb CG meeting @W3C #w3cTPAC tomorrow (2023-09-12) at 09:30 CEST.
Looking forward to seeing @evanp.me (@evan@cosocial.ca @evanpro) and many others!
So many advances in #ActivityPub, #Webmention, Micropub, #IndieAuth etc. that it may be time to restart the #SocialWebWG to officially update all our active specifications.
We can & should also reach out to #Bluesky & #Nostr communities to work together on shared semantics and bridging protocols to continue growing a heterogenous #fediverse built on the #OpenWeb.
We know it is possible. We worked hard in the Social Web working group to align a lot of semantics across #ActivityStreams and #microformats2. The fruitful results of that are services like http://fed.brid.gy/ which I myself use to send a Webmention when I make a new post (like this one) and have #BridgyFed automatically federate it via ActivityPub using my personal site identity to #Mastodon followers and others.
@snarfed.org wrote up a recent comparison of top #decentralized #socialProtocols that can help inform a lot of this discussion: https://snarfed.org/2023-09-04_50856 -
Tantek ()'s status on Tuesday, 22-Aug-2023 15:43:00 EDT
Tantek
Threads.net now supports the #indieWeb #microformats #openStandard rel-me for distributed ✅ verification!¹ (supported since 2023-08-09)
My Threads profile already had my domain since it was created from my Instagram profile.
View source on https://www.threads.net/@tantek and you can see the #relMe on a link tag:
<link rel="me" href="https://tantek.com/" />
Instructions to add yours:
* Add your domain to your Threads profile "Link" field. That’s it.
Longer explicit steps: https://indieweb.org/rel-me#Threads
Thanks especially to @timothychambers.net (@tchambers@indieweb.social, @timothyjchambers@threads.net) for requesting rel-me support² which one Threads engineer “decided to hack it together” one night!³
You can view Tim’s profile @tchambers@indieweb.social for a real world example of a Mastodon profile showing a green text ✅ verified link to a Threads profile.
Tim made several good points in his request:
“… a small, but disproportionately helpful addition would be to support this "rel=me" feature in your profiles. That could launch well before full ActivityPub, & show the first real integration to open social web standards”
Microformats (and IndieWeb) standards in general are deliberately designed as small, incremental building blocks which are disproportionately helpful as Tim says.
These small building blocks which directly enable user features are usually something a web developer can code at least some (often complete!) support for in one day/night which makes them particularly appealing as a way to rapidly support open #socialWeb standards used by the #fediverse and beyond.
Incrementally implementing microformats & IndieWeb standards⁴ also demonstrates good will and good intentions for supporting the #openWeb.
This is day 44 of #100DaysOfIndieWeb. #100Days
← Day 43: https://tantek.com/2023/171/t1/anniversaries-microformats-posse
→ 🔮
Previously:
* 2023-02-01 Wikipedia.org supports multiple rel=me links: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me
¹ https://www.threads.net/@mosseri/post/Cvu2eXurRbB
² https://www.threads.net/@timothyjchambers/post/CupCvChAxI8
³ https://www.threads.net/@0xjessel/post/Cvu7-A4viZu
⁴ https://spec.indieweb.org/ -
Tantek ()'s status on Wednesday, 19-Apr-2023 20:48:00 EDT
Tantek
10 years ago today the first #federated #IndieWeb comment thread was published and collected peer-to-peer IndieWeb replies across websites without any intermediary, silo or otherwise¹.
2013-04-19 @eschnou.com posted a brief note on his personal site with #atMentions of a few domains (putting an '@' sign immediately before a domain name to indicate an explicit cross-web @-mention), which itself was also a first²
"Testing #indieweb federation with @waterpigs.co.uk, @aaronparecki.com and @indiewebcamp.com !"
When @aaronpk.com was notified and replied from his site within minutes³, it became the first peer-to-peer federated IndieWeb comment thread, at the time using h-entry and Pingback. I blogged about it a few days later⁴.
Earlier this year I blogged more observations of all the user interactions that happened on that day and shortly thereafter to make this all work: https://tantek.com/2023/014/t4/domain-first-federated-atmention
Unfortunately Laurent Eschnou’s original post is no longer up, and we only have the Internet Archive copy. However most of the IndieWeb reply posts are still up including Barnaby’s: https://waterpigs.co.uk/notes/1334/
The oldest still working federated post and comment thread was second overall, unsurprisingly from @aaronparecki.com⁵, a whole 40 days after Laurent’s first.
This is day 37 of #100DaysOfIndieWeb. #100Days #OpenWeb #federation #fediverse
← Day 36: https://tantek.com/2023/100/t1/auto-linked-hashtags-federated
→ 🔮
Glossary
federation
https://indieweb.org/federation
h-entry
https://microformats.org/wiki/h-entry
Pingback
https://indieweb.org/Pingback
reply post
https://indieweb.org/reply
References
¹ https://web.archive.org/web/20130427010301/http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html
² https://tantek.com/2023/014/t4/domain-first-federated-atmention
³ https://aaronparecki.com/2013/04/19/3/indieweb
⁴ https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread
⁵ https://aaronparecki.com/2013/05/21/4/xkcd -
Tantek ()'s status on Wednesday, 19-Apr-2023 04:22:00 EDT
Tantek
@fredrocha.net (@john_fisherman@mastodon.social) saw your post (https://mastodon.social/@john_fisherman/110224246899618915) from the #IndieWeb stream. Beautiful photos on your site! #btconf was great wasn’t it?
My personal URL is https://tantek.com/ and my #fediverse @ is @tantek.com. My Atom feed file is auto-discoverable by feed readers from my home page.
Feeding (so to speak) two discovery birds with one stonefruit¹.
Your personal website can be your fediverse address², each providing seamless discovery for the other.
As web developers we should be building & developing our personal sites to exemplify the latest & greatest of such practices, including using Mastodon/ActivityPub as yet another distribution mechanism (ala POSSE) for your existing personal websites rather than a separate profile/stream.
Discussed this with @nebu@mastodon.social and @kadirtopal@mastodon.social just after the last talk @beyondtellerrand.com (@btconf@mastodon.social @btconf) yesterday, fitting conference closing thoughts complementing the heartfelt opening talk by @localghost.dev (https://sophie.omg.lol/ @sophie@social.lol)³.
Glossary
ActivityPub
https://indieweb.org/ActivityPub
feed file
https://indieweb.org/feed_file
POSSE
https://indieweb.org/POSSE
References
¹ https://tantek.com/2020/147/t2/replace-violent-metaphors
² https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
³ https://tantek.com/2023/107/t1/beyond-tellerand-talk-love-personal-website -
Tantek ()'s status on Wednesday, 19-Apr-2023 04:22:00 EDT
Tantek
@fredrocha.net (@john_fisherman@mastodon.social) saw your post (https://mastodon.social/@john_fisherman/110224246899618915) from the #IndieWeb stream. Beautiful photos on your site! #btconf was great wasn’t it?
My personal URL is https://tantek.com/ and my #fediverse @ is @tantek.com. My Atom feed file is auto-discoverable by feed readers from my home page.
Feeding (so to speak) two discovery birds with one stonefruit¹.
Your personal website can be your fediverse address², each providing seamless discovery for the other.
As web developers we should be building & developing our personal sites to exemplify the latest & greatest of such practices, including using Mastodon/ActivityPub as yet another distribution mechanism (ala POSSE) for your existing personal websites rather than a separate profile/stream.
Discussed this with @nebu@mastodon.social and @kadirtopal@mastodon.social just after the last talk @beyondtellerrand.com (@btconf@mastodon.social @btconf) yesterday, fitting conference closing thoughts complementing the heartfelt opening talk by @localghost.dev (https://sophie.omg.lol/ @sophie@social.lol)³.
Glossary
ActivityPub
https://indieweb.org/ActivityPub
feed file
https://indieweb.org/feed_file
POSSE
https://indieweb.org/POSSE
References
¹ https://tantek.com/2020/147/t2/replace-violent-metaphors
² https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
³ https://tantek.com/2023/107/t1/beyond-tellerand-talk-love-personal-website -
Tantek ()'s status on Wednesday, 22-Mar-2023 11:14:00 EDT
Tantek
Watching #MozFest session Dialogues & Debates: Making the Fediverse¹ and panelist @stevetex@mozilla.social (@stevetex) just announced that we (#Mozilla) are standing up a #Mastodon instance², starting with limited sign-ups.
I’m excited that Mozilla is experimenting with #socialWeb alternatives to centralized #socialMedia silos.
There are many #Mozillians with #fediverse addresses you can follow:
* https://wiki.mozilla.org/Mastodon
Several of these folks also have their own #IndieWeb sites.
It’s interesting seeing how people are individually choosing to use a fediverse address on someone else’s server, vs their own server like with a subdomain, vs just using their existing site.
One trend I have seen is people using someone else’s Mastodon server as a stepping stone, a learning experience, before migrating to either self-hosting Mastodon (or an easier to run alternative like microblog.pub³, not to be confused with micro.blog⁴), or ideally directly using their own site, blog etc. to connect to the fediverse⁵.
Do you have an @-@ address and want to use your own site instead?
If you’re a #webdev, you can totally do this by connecting your existing personal site with https://fed.brid.gy/ and own your presence on the web, social web, fediverse all at one place.
Got questions? Drop by the IndieWeb chat! https://chat.indieweb.org/dev
This is day 35 of #100DaysOfIndieWeb #100Days
← Day 34: https://tantek.com/2023/072/t1/blog-as-if-ai-trained-posts
→ 🔮
¹ https://schedule.mozillafestival.org/session/UEEGYL-1
² https://mozilla.social/
³ https://indieweb.org/microblog.pub
⁴ https://indieweb.org/micro.blog
⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb -
Tantek ()'s status on Wednesday, 22-Mar-2023 11:14:00 EDT
Tantek
Watching #MozFest session Dialogues & Debates: Making the Fediverse¹ and panelist @stevetex@mozilla.social (@stevetex) just announced that we (#Mozilla) are standing up a #Mastodon instance², starting with limited sign-ups.
I’m excited that Mozilla is experimenting with #socialWeb alternatives to centralized #socialMedia silos.
There are many #Mozillians with #fediverse addresses you can follow:
* https://wiki.mozilla.org/Mastodon
Several of these folks also have their own #IndieWeb sites.
It’s interesting seeing how people are individually choosing to use a fediverse address on someone else’s server, vs their own server like with a subdomain, vs just using their existing site.
One trend I have seen is people using someone else’s Mastodon server as a stepping stone, a learning experience, before moving to either self-hosting Mastodon (or an easier to run alternative like microblog.pub³, not to be confused with micro.blog⁴), or ideally, directly using their existing site, blog etc. to connect to the fediverse⁵.
Do you have an @-@ address and want to use your own site instead?
If you’re a #webdev, you can totally do this by connecting your existing personal site with https://fed.brid.gy/ and own your presence on the web, social web, fediverse all at one place.
Got questions? Drop by the IndieWeb chat! https://chat.indieweb.org/dev
¹ https://schedule.mozillafestival.org/session/UEEGYL-1
² https://mozilla.social/
³ https://indieweb.org/microblog.pub
⁴ https://indieweb.org/micro.blog
⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb -
Tantek ()'s status on Monday, 20-Feb-2023 22:16:00 EST
Tantek
Five years ago last Monday, the @W3C Social Web Working Group officially closed¹.
Operating for less than four years, it standardized several foundations of the #fediverse & #IndieWeb:
#Webmention
#Micropub
#ActivityStreams2
#ActivityPub
Each of these has numerous interoperable implementations which are in active use by anywhere from thousands to millions of users.
Two additional specifications also had several implementations as of the time of their publication as a W3C Recommendations (which you can find from the Implementation Report linked near the top of each spec). However today they’re both fairly invisible "plumbing" (as most specs should be) or they haven’t picked up widespread use like the others:
#LinkedDataNotifications (LDN)
#WebSub
To be fair, LDN was only one building block in what eventually became SoLiD², the basis of Tim Berners–Lee’s startup Inrupt.
However, in the post Elon-acquisition of Twitter and subsequent Twexodus, as Anil Dash noted³, “nobody ran to the ’web3’ platforms”, and nobody ran to SoLiD either.
The other spec, WebSub, was roughly interoperably implemented as PubSubHubbub before it was brought to the Social Web Working Group. Yet despite that implementation experience, a more rigorous specification that fixed a lot of bugs, and a test suite⁴, WebSub’s adoption hasn’t really noticeably grown since. Existing implementations & services are still functioning though. My own blog supports WebSub notifications for example, for anyone that wants to receive/read my posts in real time.
One of the biggest challenges the Social Web Working Group faced was with so many approaches being brought to the group, which approach should we choose?
As one of the co-chairs of the group, with the other co-chairs, and our staff contacts over time, we realized that if we as chairs & facilitators tried to pick any one approach, we would almost certainly alienate and lose more than half of the working group who had already built or were actively interested in developing other approaches.
We (as chairs) decided to do something which very few standards groups do, and for that matter, have ever done successfully.
From 15+ different approaches, or projects, or efforts that were brought⁵ to the working group, we narrowed them down to about 2.5 which I can summarize as:
1. #IndieWeb building blocks, many of which were already implemented, deployed, and showing rough interoperability across numerous independent websites
2. ActivityStreams based approaches, which also demonstrated implementability, interoperability, and real user value as part of the OStatus suite, implemented in StatusNet, Identica, etc.
2.5 "something with Linked Data (LD)" — expressed as a 0.5 because there wasn’t anything user-visible “social web” with LD working at the start of the Working Group, however there was a very passionate set of participants insisting that everything be done with RDF/LD, despite the fact that it was less of a proven social web approach than the other two.
As chairs we figured out that if we were able to help facilitate the development of these 2.5 approaches in parallel, nearly everyone who was active in the Working Group would have something they would feel like they could direct their positive energy into, instead of spending time fighting or tearing down someone else’s approach.
It was a very difficult social-technical balance to maintain, and we hit more than a few bumps along the way. However we also had many moments of alignment, where two (or all) of the various approaches found common problems, and either identical or at least compatible solutions.
I saw many examples where the discoveries of one approach helped inform and improve another approach. Developing more than one approach in the same working group was not only possible, it actually worked.
I also saw examples of different problems being solved by different approaches, and I found that aspect particularly fascinating and hopeful. Multiple approaches were able to choose & priortize different subsets of social web use-cases and problems to solve from the larger space of decentralized social web challenges. By doing so, different approaches often explored and mapped out different areas of the larger social web space.
I’m still a bit amazed we were able to complete all of those Recommendations in less than four years, and everyone who participated in the working group should be proud of that accomplishment, beyond any one specification they may have worked on.
With hindsight, we can see the positive practical benefits from allowing & facilitating multiple approaches to move forward. Today there is both a very healthy & growing set of folks who want simple personal sites to do with as they please (#IndieWeb), and we also have a growing network of Mastodon instances and other software & services that interoperate with them, like Bridgy Fed⁶.
Millions of users are posting & interacting with each other daily, without depending on any large central corporate site or service, whether on their own personal domain & site they fully control, or with an account on a trusted community server, using different software & services.
Choosing to go from 15+ down to 2.5, but not down to 1 approach turned out to be the right answer, to both allow a wide variety⁷ of decentralized social web efforts to grow, interoperate via bridges, and frankly, socially to provide something positive for everyone to contribute to, instead of wasting weeks, possibly months in heated debates about which one approach was the one true way.
There’s lots more to be written about the history of the Social Web Working Group, which perhaps I will do some day.
For now, if you’re curious for more, I strongly recommend diving into the group’s wiki https://www.w3.org/wiki/Socialwg and its subpages for more historical details. All the minutes of our meetings are there. All the research we conducted is there.
If you’re interested in contributing to the specifications we developed, find the place where that work is being done, the people actively implementing those specs, and even better, actively using their own implementations⁸.
You can find the various IndieWeb building blocks living specifications here:
* https://spec.indieweb.org/
And discussions thereof in the development chat channel:
* https://chat.indieweb.org/dev
If you’re not sure, pop by the indieweb-dev chat and ask anyway!
The IndieWeb community has grown only larger and more diverse in approaches & implementations in the past five years, and we regularly have discussions about most of the specifications that were developed in the Social Web Working Group.
This is day 33 of #100DaysOfIndieWeb #100Days
← Day 32: https://tantek.com/2023/047/t1/nineteen-years-microformats
→ 🔮
Post Glossary:
ActivityPub
https://www.w3.org/TR/activitypub/
ActivityStreams2
https://www.w3.org/TR/activitystreams-core/
https://www.w3.org/TR/activitystreams-vocabulary/
Linked Data Notifications
https://www.w3.org/TR/ldn/
Micropub
https://micropub.spec.indieweb.org/
Webmention
https://webmention.net/draft/
WebSub
https://www.w3.org/TR/websub/
References:
¹ https://www.w3.org/wiki/Socialwg
² https://www.w3.org/wiki/Socialwg/2015-03-18-minutes#solid
³ https://mastodon.cloud/@anildash/109299991009836007
⁴ https://websub.rocks/
⁵ https://indieweb.org/Social_Web_Working_Group#History
⁶ https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed
⁷ https://indieweb.org/plurality
⁸ https://indieweb.org/use_what_you_make -
Tantek ()'s status on Thursday, 19-Jan-2023 21:05:00 EST
Tantek
Instead of posting on a personal #IndieWeb site (& POSSE copies), some post primarily to a #fediverse instance and syndicate to Twitter, or vice-versa. How to reply^1 to such posts, e.g.:
Reply to a toot (& POSSE tweet): https://tantek.com/2023/019/t4
* @-@ (Twitter @-name)
This is a variant of case (2) in https://tantek.com/2023/018/t1/elevate-indieweb-above-silo.
We can update the directive and two questions & answers in that prior post accordingly:
* Elevate #IndieWeb domains above @-@ addresses, and those above any silo identities
1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.
2. Was their post only published on a #fediverse instance (and/or silo), or was it POSSEd to a fediverse instance (and/or silo) and do you plan to federate (and/or POSSE) your reply^3?
Then use their @-@ address or silo @-name, or @-@ (silo @-name) for both, or (@-@, silo @-name) parenthetically following their @-domain if (1). This will notify them on that instance (or silo), and may help thread your POSSE reply.
When posting a reply, you (or your CMS automatically) should explicitly link with u-in-reply-to markup^4 to the post your are replying to, and any of its syndicated copy permalinks on destinations you plan to POSSE your reply (see also multi-reply^5).
This is day 18 of #100DaysOfIndieWeb #100Days, written the day after.
← Day 17: https://tantek.com/2023/018/t1/elevate-indieweb-above-silo
→ 🔮
^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post
^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
^4 https://indieweb.org/in-reply-to
^5 https://indieweb.org/multiple-reply -
Tantek ()'s status on Thursday, 19-Jan-2023 02:11:00 EST
Tantek
The answer to “How should you @-mention someone you are replying to?”^1 can depend on many factors or a few. Context matters somewhat, sometimes.
We can simplify it to 2 questions, based on 1 directive:
* Elevate #IndieWeb domains, above any silo or @-@ identities
Two questions and answers:
1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.
2. Was their post only published on a silo (or #fediverse instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then @-mention their silo @-name (or @-@ address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply.
Examples:
If the author has their own domain:
Reply to an IndieWeb post (& POSSE toot): https://tantek.com/2023/008/t1/
* @-domain (@-@)
Reply to an IndieWeb post (& POSSE tweet): https://tantek.com/2023/016/t1/
* @-domain [that matches their Twitter @-name]
Reply to a toot: https://tantek.com/2023/008/t4/
* @-domain (@-@)
Reply to a tweet: https://tantek.com/2023/002/t2/
* @-domain (Twitter @-name)
If the author does not have their own domain:
Reply to a toot: https://tantek.com/2023/002/t4/
* @-@
Reply to a tweet: none since this series, though it would be of the form:
* Twitter @-name
This is day 17 of #100DaysOfIndieWeb #100Days, again finished the next day.
← Day 16: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
→ 🔮
^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post
^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute -
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1)'s status on Wednesday, 28-Dec-2022 21:20:57 EST 
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
https://500ish.com/mastodon-brought-a-protocol-to-a-product-fight-ba9fda767c6a
#Medium link; don't be surprised if it does weird things before showing you the article.
"Mastodon brought a protocol to a product fight"
> Yes, yes, the network is under immense strain as people flee the Elon strain infecting Twitter. But come on, there are folks who really believe this is going to replace, or even stand alongside Twitter, as a massively scaled social network? I call bullshit. While it’s impressive that millions of users have apparently given Mastodon a try, the product is far too slapdash and clunky to keep folks engaged. A lump of coal.
No, it isn't meant to be a #Twitter replacement. Keep your Twitter account until you no longer want it--or the company closes and the site shuts down--you can use Mastodon alongside Twitter.
And the #Fediverse networks are much more than just #Mastodon. Don't think you have experienced the network and all it has to offer if all you've done is briefly tried to use Mastodon, because you haven't experienced it.
> I’ve somehow avoided signing up for the service up until now. Largely because signing up was and is so comically obtuse — pick your server everyone, hope you choose wisely!
Have you not used e-mail? It works the same way. You pick a server, such as Gmail or Outlook dot com, and sign up. Please tell me you realize that the people you communicate with are not all on the same e-mail service that you use.
> But, but, it’s not a product, it’s a protocol. Yeah, that’s a nice thing to say. And to believe in. But I truly believe the ship has sadly sailed for such idealism in this space. Jack Dorsey can talk about how this should have been what Twitter was from the get go until he’s bluesky in the face. It’s just not going to happen. And he’s more to blame for that than most everyone else. As is he for the Elon element of this current equation. But that’s a different story.
Okay, so how about this story: Twitter has only been profitable two or three years of its entire history. Since it started, it has existed by burning through investors' funds. Eventually, with or without Elon Musk's ownership, that runs out. Without such funding, their corporate-centralized ( #corpocentric ) model cannot exist very long. And same for their centralized competitors, such as Post.news, Gab, Parler, and so on. What is left is either #federated or #peer-to-peer approaches, where no single entity is responsible for funding and managing the entire network. So whether it is the #Fediverse ( with #ActivityPub and #OStatus and their successors ) & the Federation ( with #Diaspora ) or #Bluesky, or #Twister, or #NOSTR, the eventual future of #socnets is #decentralized, if not entirely peer-to-peer unless a national government takes over Facebook and Twitter in order to provide effectively unlimited resources. It is the protocol that makes it possible for thousands or millions of instances to displace and replace one big centralized instance.
1/2 -
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1)'s status on Sunday, 11-Dec-2022 20:58:05 EST
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
https://prodromou.pub/@evan/109498060348615260
@evan@prodromou.pub @evan@identi.ca ( and formerly @evan@e14n.com ) has said this a few times, but here it is again.
"Every time you post on Twitter, you produce value for the advertisers.
You tell everyone in your network there that it's OK to stay. That you're all helpless to leave.
You tell the people who've lost their jobs, the people who are being hounded and harassed, that they are not important to you.
You know you're going to be ashamed of it later.
Just stop posting.
Do it here, not there. Connect here, not there.
Don't reply, don't like, don't retweet.
Stop feeding your life into the machine."
This was true before Elon #Musk bought #Twitter, but I guess it wasn't as important before.
I don't fully agree, simply because there may be some advantages to many people who continue to use Twitter instead of moving to the #Fediverse (e.g., #GNU_Social, #Mastodon, #Pleroma, #Misskey, #PixelFed, #Lenny / #Lemmy, etc) or they would have moved over already.
Also, because unless one self-hosts one's own presence, an angry instance admin is all it takes to lose all posts and connections and have to start over. Or, if one has contacts on a different instance, then irate instance admins participating in #blockwars (including #fediblock) can separate the person from some portion of their contacts.
So remember, everything that Twitter is or can do to you, your Fediverse instance can also do. Most instances will never do most of those things, but pretending that one is safe here could result in disappointment in the future. -
Tantek ()'s status on Tuesday, 06-Dec-2022 16:48:00 EST
Tantek
Two days ago my #BridgyFed followers crossed 8-bits:
https://fed.brid.gy/user/tantek.com
Signs of #TwitterMigration: my prev post had ~2x more #fediverse responses than Twitter, a ~500:1 difference per follower (having ~250x more Twitter followers).
Many possible factors. Mastodon users see more from their followings. Twitter accounts could be mostly bots or abandoned. Recent posts are technical, maybe Mastodon users are more technical. Tech friends migrated first. Or hashtagging #fediverse. -
Tantek ()'s status on Friday, 02-Dec-2022 15:01:00 EST
Tantek
#indieweb 🤝 #fediverse
✨ https://werd.io/2022/the-fediverse-and-the-indieweb (@benwerd)
✨ https://catgirlin.space/posts/moving-to-the-fediverse-and-indieweb/
✨ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
Previously: https://twitter.com/t/status/1586264352453427201, https://twitter.com/t/status/956436348361158658 #TwitterMigration #ActivityPub #SocialWeb #OpenStandards #OpenWeb -
Tantek ()'s status on Friday, 02-Dec-2022 15:01:00 EST
Tantek
#indieweb 🤝 #fediverse
✨ https://werd.io/2022/the-fediverse-and-the-indieweb (@benwerd)
✨ https://catgirlin.space/posts/moving-to-the-fediverse-and-indieweb/
✨ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
Previously: https://twitter.com/t/status/1586264352453427201, https://twitter.com/t/status/956436348361158658 #TwitterMigration #ActivityPub #SocialWeb #OpenStandards #OpenWeb -
Apollo Lemmon (apollo)'s status on Thursday, 12-Sep-2019 13:24:55 EDT 
Apollo Lemmon
Mastodon & SeizeMeans.com
Since the middle of last year I've had a Mastodon instance at SeizeMeans.com. I didn't feel I should make it open to anyone else until I put together a Code of Conduct, but today I finally pieced one together. SeizeMeans.com is a Mastodon instance open to communists, socialists, anarchists and fellow travelers.
https://apollolemmon.com/2019/09/12/mastodon-seizemeans-com/
-
Doug Webb (douginamug)'s status on Friday, 28-Dec-2018 05:50:15 EST 
Doug Webb
TODAY (28th) activist itinerary for #35c3 ✊ 🌍 🔥
- 13:00, #ExtinctionRebellion meetup @ Lect. rm. M1
- 14:00, #YunoHost workshop @ Lect. rm. M1
- 14:00, #Fediverse meetup @ Lect. rm. M3
- 17:00, #Briar 'party' @ Curry Club Augsburg Assembly
- 19:30, Intro to #Anarchy @ Lect. rm. M3Maybe see you there 🙂
-
Sebastian (sebastians)'s status on Friday, 14-Dec-2018 05:34:31 EST 
Sebastian
I'm considering running a scholar/academic/research/education oriented #peertube instance, wondering how much interest there is in it on this bit of the #fediverse?
It seems very doable, but bit steep in investment cost (hardware). I think it should be doable with a running cost of ca 100-150,- per month for hosting and hardware. Assuming sponsored/donated admin-time.
-
slackz (slackz)'s status on Wednesday, 14-Nov-2018 11:27:27 EST 
slackz
Hey all, I wanna open up this invite again. I really want to grow organizing.social. This instance is a space for community organizers and we welcome folks trying to bring that work into a proper social media space.
The #fediverse is vast and has been amazing, but #OrgSoc is way too small :P
Here's an invite link:
https://organizing.social/invite/tnBbPe2XWe wanna encourage a diversity of voices and joining this instance will mean you are a part of deciding how it operates.
#DirectDemocracy
#ComradesWelcome
All stadeus content and data are available under the