Mastodon founder, Eugen Rochko, praises Threads entry into the #Fediverse because it makes Mastodon “a far more attractive option.”
This is fairly obvious and basic network effects since both Threads & Mastodon become more valuable as their users can now share content across these services seamlessly.
This angers Mastodon admins for whom the fact that not a lot of people use Mastodon was a selling point. They do not want it to grow and be useful to more people.
Hey hcommons.social and the #fediverse: we've made the decision not to federate with #Meta and #Threads. We do not feel that we can adequately protect members of our community from potential attacks from anti-LGBTQ+, anti-Black, anti-academic, or other extremists who can freely create accounts and sow hatred on Threads unless we block the server. We do not want to allow any kinds of connections that would make our most at-risk users less safe.
We understand that this may disappoint some of you, and that you may wish to seek another instance that will allow you to communicate more freely with your friends on that network. Please read more about our reasoning on our team blog: https://team.hcommons.org/2023/12/15/threads/
Way more interesting and healthy fediverse news is happening in the shadows and is barely getting discussed! Which is: Discourse has federation between different instances of itself and other #fediverse software such as Mastodon working!
With Meta beginning to test federation, there's a lot of discussion as to whether we should preemptively defederate with Threads. I made a post about the question, and it seems that opinions differ a lot among people on Kbin. There were a lot of arguments for and against regarding ads, privacy, and content quality, but I don't...
Oh awesome, I open my app to find the #fediverse in a giant collective panic because a social platform owned by a giant company dares to join it.
Fedi: “I want an open platform where everything is standardized”
(#Threads enables ActivityPub)
Fedi: “NOT LIKE THAT ANYTHING BUT THAT”
If you declare an open standard and provide the clearly superior ecosystem, you relinquish control of who uses it just by it being open. You can’t have it both ways. Ever.
A project has started to build a #Fediverse#testsuite, so it becomes possible to systematically test interoperability between applications in the fediverse.
It is going to need some virtualization, to run "substantial" server-side applications for testing. So we'd like to know what development and virtualization platforms #ActivityPub developers develop and test on.
If you are a Fediverse developer, could you spend 5min and answer our survey?
In the light of renewed conversations about Meta and Threads, I would like to remind everyone that it is now easier than ever to run your own fediverse community, without having to worry about setting up and maintaining your own server.
Rachel Lambert, Director of Product Management at Meta just posted about working with the #fediverse
"Working with experts to figure out how we can reshape regulations that are built for closed systems, and adapt them to more open ones"
Ah. That's probably the game.
They've performed significant regulatory capture, and they're going to come out swinging about how the fediverse is full of material that requires regulation, and that anyone participating has to implement policies that are impossible at a hobby scale.
Okay #Fediverse, let’s get something straight. We are all grown ups here (hopefully) and can make choices for ourselves. We alive in a society that allows us the freedom to choose for ourselves what to do.
Why would you allow or want to be part of an instance where they choose for you who or what to block? I understand that there are BAD people on #Meta, just as there are on EVERY platform on the internet.
Give the regular people on each platform a chance to been seen.
The proliferation of #ActivityPub is exciting. But don't dismiss those that want to defederate with corporate socials. The #fediverse was built by individuals escaping the harassment they faced on those platforms.
If you don't agree with your server admin's decision to federate with a specific domain, you can block it on your own. You have the power!
This seems preferable to an admin making the decision for all users.
#mastowatch is a pretty sweet little app that provides all sorts of info on various fediverse instances/servers. One of the more interesting pieces of data it collects is the list of blocked servers for a particular instance. Cool to see the perp lists haha
Anyone over the age of 30 who has spend any time in tech-adjacent spaces still cheering for #BigTech "joining" the #Fediverse is fucking deluding themselves. We've been through so many cycles of this shit over the past twenty years, how some people can still trust #facebook to do anything remotely ethical is beyond me.
They're not here to join, they're here to destroy. This is just the most cost-effective, PR-friendly way of doing it.
Default instance blocks should largely replace defederation
Since what content users might want to see is quite unlikely to match which servers the admins tolerate, choosing instance on the Fediverse can be quite complicated, which is inconvenient and off-putting for new users.
For this reason, and simply that the Fediverse is stronger united, I believe defederation should ideally be reserved for illegal content and extreme cases. If Fediverse platforms would allow instances to simply block the rest for users by default, the user experience would be the same, unless they decide otherwise.
With yesterday's announcement that Meta is starting to test Threads and ActivityPub integration, I see the #Fediverse is at an all time high again of whining and crying and being butthurt over it all.
I get stating your opinion about not wanting them here or whatever, but come on people, don't sound like a little 2 year old who lost their pacifier. It gets old, quick.
Just mute/block and move on and be done with it all. It's really that damn simple.
The network effect for #ActivityPub is gaining some serious momentum right now. As more services adopt the protocol, more people, more communities and more content are added to the network making it increasingly more valuable for everyone. This will only accelerate in the coming months as Threads, Wordpress, Tumblr, Flipboard and others federate.
We're still in early innings but there's no way to put this genie back in the bottle. The open social Web / the #Fediverse is going to be huge.
Wow #Fediverse, thanks for the help! I am genuinely surprised at how close the results were. It looks like the recommendation is to try out the #Threadiverse (#Kbin and / or #Lemmy) first - but only by 1.8% over #Peertube! Y'all must know that I've been getting frustrated with #Reddit lately. I also appreciate the recommendations for other things to explore.
Now the question is Kbin or Lemmy? Or both? (any thoughts?)
Folks, perhaps the biggest Fediverse news of the week (the month? year?) is that the W3C @w3c, essentially the organization that manages the entire internet, has shut down its social media presence on Twitter and moved to Mastodon, and is encouraging others to do the same.
what do we have to do to make the #ActivityPub plugin attractive to more #WordPress users? We are currently at 4000+ active users on WordPress.org + the WordPress.com users.
A case for preemptively defederating with Threads (kbin.social)
With Meta beginning to test federation, there's a lot of discussion as to whether we should preemptively defederate with Threads. I made a post about the question, and it seems that opinions differ a lot among people on Kbin. There were a lot of arguments for and against regarding ads, privacy, and content quality, but I don't...