kbin.social is being overrun with spammers. Can we disable registrations on this instance so they can't keep creating new accounts? Every day I log on, I have to spend the first 20-30 minutes, reporting and blocking a bunch of new accounts....
But that's what the author is saying. Make the existing tools easy and polished so that average users who don't care can/will use them. Right now, their only options are the corporate platforms because there's no simple way for them to have their own website or social web presence. If signing up for a CMS with a custom domain were as easy as signing up for Instagram/tiktok/etc, maybe more ppl would do it.
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...
Meta (or any large entity) cannot monopolize or control the fediverse. If their implementation starts drifting from established norms, they will be blocked by most instances or will just be incompatible. The example used to back up this argument is usually XMPP, but people forget that XMPP is still around. It never died; its just a smaller, niche network.
The fediverse is already a small, niche network. So if Meta comes in and tries to control the network, it will then be responsible for maintaining its own "Meta-fediverse" network (that some instances may choose to be a part of) while the remaining instances will remain as a small, niche network. Meta can't force current fediverse servers to implement any Meta-specific features or to change their software in any way.
The mod workload argument is the only one that I see being a real issue, but the target is wrong. Anyone worried about that should be discussing it with fediverse devs to improve mod tools, not trying to force the entire fediverse to stay at their preferred size
Once content dependence is established, there is no turning back.
Everyone who is on the fediverse has already made that choice. They are intentionally on a network with less content because of the other benefits And a huge portion of the discussion of Meta joining the fediverse is made up of ppl who are saying they will block Threads on day 1.
the latter will make it impossible to grow again.
That's what everyone was saying back when the fediverse was even smaller, or even before it existed. "How can you compete with giants like G+, twitter, and facebook?" There will always be groups of people who will not participate in corporate social media. And there will always be people who like the convenience of corporate social media but get fed up with it and seek alternatives. And there will always be people who bounce between services.
Tons of people will leave platforms like Mastodon to go to Threads
They're only here because they left corporate social media. If they were going to leave for Threads, why wouldn't they do it now? They've heard all the warnings about some supposed EEE and assume that Threads won't connect to the fediverse forever so why would Threads adding ActivityPub support suddenly change their mind? Going to threads now puts them in the same state as going to threads later in some hypothetical future where the fediverse is too small to matter.
If we want a fediverse with the values we care about to grow...
I don't care about Meta and I'm not relying on them for anything. When they join the fediverse, individual instance owners will still have all the power. User on the fediverse will still be able to control their own feeds. But there are people who use Threads and being able to communicate with them would be nice. I don't think any of the fears about Meta on the fediverse are justified and I think the fediverse will continue on just like it has for more than a decade.
Secure a place in history. Create the source material for hundreds of journalists, bloggers and shitposters writing about the downfall of reddit and the rise of the threadiverse. (also missing!)...
Pleroma still doesn't have a wikipedia article because of this, despite being one of the oldest AP-enabled fediverse services. It's been deleted twice because some moderator didn't like the quality or number of sources.
Can registrations on kbin.social be disabled to stop spammers (kbin.social)
kbin.social is being overrun with spammers. Can we disable registrations on this instance so they can't keep creating new accounts? Every day I log on, I have to spend the first 20-30 minutes, reporting and blocking a bunch of new accounts....
gilest.org: Make the indie web easier (gilest.org)
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...
You can be the one to create the kbin page on wikipedia (en.wikipedia.org)
Secure a place in history. Create the source material for hundreds of journalists, bloggers and shitposters writing about the downfall of reddit and the rise of the threadiverse. (also missing!)...