I just read this point in a comment and wanted to bring it to the spotlight.
Meta has practically unlimited resources. They will make access to the fediverse fast with their top tier servers.
As per my understanding this will make small instances less desirable to the common user. And the effects will be:
- Meta can and will unethically defedrate from instances which are a theat to them. Which the majority of the population won’t care about, again making the small instances obsolete.
- When majority of the content is on the Meta servers they can and will provide fast access to it and unethically slow down access to the content from outside instances. This will be noticeable but cannot be proved, and in the end the common users just won’t care. They will use Threads because its faster.
This is just what i could think of, there are many more ways to be evil. Meta has the best engineers in the world who will figure out more discrete and impactful ways to harm the small instances.
Privacy: I know they can scrape data from the fediverse right now. That’s not a problem. The problem comes when they launch their own Android / iOS app and collect data about my search and what kind of Camel milk I like.
My thoughts: I think building our own userbase is better than federating with an evil corp. with unlimited resources and talent which they will use to destroy the federation just to get a few users.
I hope this post reaches the instance admins. The Cons outweigh the Pros in this case.
We couldn’t get the people to use Signal. This is our chance to make a change.
I’m hoping that ALL admins across the Fediverse will defederate from Meta. At least we get to have our own separate platform then.
They shouldn’t just defederate from Meta, they should defederate from any other instances that federate with Meta. Like a firewall against late stage capitalism
But that is a double-edged sword. What if, for example, mastodon.social doesn’t defederate with Meta, but you defederate mastodon.social? Now you’ve just cut yourself off from a huge portion of the fediverse. Admins should defederate from Meta if their community wants to do that, but defederating from other instances that didn’t do that is going a bit too far, in my opinion.
A small price to pay for salvation from Meta.
I’ve already blocked mastodon.social.
Why?
Because the size of it, the sheer centralization around it, it creeps me out.
Why? If you have blocked meta shouldn’t you already be exempt from seeing comments and posts by their users on other instances? Why is this punitive approach needed
Edit: (Alongside downvoting, an explanation might be better suited to change people’s minds, I just eant to know the advantage of this approach since you are excluding yourself from many users and you would have already blocked meta in this scenario)
If you have blocked meta shouldn’t you already be exempt from seeing comments and posts by their users on other instances?
Yes, at least that’s how it is explained in How the beehaw defederation affects us, Back then, beehaw.org defederated from lemmy.world.
Why do I see posts/comments from beehaw users on communities outside lemmy.world and beehaw.org?
That’s because the “true” version of those posts is outside beehaw. So we get updates from those posts. And lemmy.world didn’t defederate beehaw, so posts/comments from beehaw users can still come to versions hosted on lemmy.world.
The reverse is not true. Because beehaw defederate lemmy.world, any post/comment from a lemmy.world users will NOT be sent to the beehaw version of the post.
Third instance communities
Finally, we have the example of communities that are on instances that have not been defederated by beehaw.org.
- https://beehaw.org/c/asklemmy@lemmy.ml/data_type/Post/sort/New/page/1
- https://lemmy.world/c/asklemmy@lemmy.ml/data_type/Post/sort/New/page/1
- https://lemmy.ml/c/asklemmy/data_type/Post/sort/New/page/1
We can see all three of these versions look pretty similar. That’s because for the most part they are. We are identical with lemmy.ml, as lemmy.ml hosts the “true” version, and we get all updates from the “true” version. Beehaw.org will not get posts/comments from us, so beehaw actually doesn’t have the most “true” version of this community.
Translated into the current context:
- beehaw.org = your instance, which defederates from Threads
- lemmy.world = Threads (sorry folks, just to eplain the mechanics)
- lemmy.ml = another instance, which is federated with both, your instance and Threads
Conclusions:
- You wont see posts or commens from Threads users in that remote community. You also won’t see reactions to those activities from anyone, anywhere. It’s as if comment chains started by Threads users don’t exist.
- Threads will not see posts and comments from you, even if done in communities from instances which are federated with Threads.
Or what do you think, @amiuhle@feddit.de?
Hi there! Looks like you linked to a Lemmy community using an URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !asklemmy@beehaw.org, !asklemmy@lemmy.world, !asklemmy@lemmy.ml
You’d see comments and posts from their users on other instances that don’t block Meta.
It’s unclear how many users you would actually exclude, I think a lot of users who are on the fediverse right now don’t want to have anything to do with Meta.
As the fediverse grows, there will be different bubbles with not much interaction between those, mainly because some instances won’t be moderated while others will try to create discrimination free environments.
Just so I understand, blocking an instance:
Does:
- block people from that instance from interactinh with yours
- blocks people from your own indtance being able to search theirs
- blocks communities from that instance to appear on /all
It doesn’t:
- Block comments if done on non blockef instance
- Block posts if done on non blocked instance
Is that right? I was under the impression that defederating would block them completely, as that is how it worked over at mastodon, if it doesn’t that seems like a serious oversight.
That will just drive many Fedi-users to Meta.
Different instances will make different decisions and users will go to the instances that suit their preferences. That’a how it is supposed to work and the only way it hurts the Fediverse is if we get flooded with threads complaining that other people have different preference, dammit.
I feel like this will just hurt us more then help.
Big corpos don’t want to take it over, they want it gone.
https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
Damn, that’s a terrifying vision of the future. I was on the fence with defederating, but we probably should.
Your comment should be top.
Absolutely. We’d have to be nuts to think they’re not trying to take it over and ruin it.
I don’t think XMPP comparison is correct.
First, in my personal (subjective!) opinion, XMPP died because of entirely different primary reason: it, by design, had trouble working on mobile devices. Keeping the connection was either battery-expensive or outright impossible, and using OS native push notifications had significant barriers.
As for Google Talk - it just came and went. Because they never had proper MUCs (multi user conferences, think communities), in my own (again, personal, thus subjective - not objective!) experience it was quite the opposite to how the article paints it. Whoever participated in chatrooms I’ve been in, and had used a Google account, hated Google’s decision and moved to XMPP. I’m no fond of Google, but their impact on XMPP was not strictly negative - they contributed some useful XEPs and useful free software libraries after all. Although, of course, for those who used XMPP primarily as a classic messenger system (like MSN, AIM or ICQ) for private 1:1 chats things surely looked differently.
Now, why I think the comparison is not correct. I think Threads’ situation is different because of fundamental differences in how those systems operate. And not in favor of Threads/Meta. If Threads would be Lemmy or XMPP MUC-like system (that is, having communities/groups hosted on particular servers), then it would be a complicated story, where Fediverse could even theoretically score a net win. But as I get it, Threads is Mastodon/Twitter-like thing, and their users’ content will stay with Meta, entirely at Meta’s discretion whenever they let other systems access it, and when they pull the plug. Given that Meta is also not likely to contribute to FLOSS Fediverse projects, their Fediverse presence is of questionable benefits to say the least.
Fantastic read. Thanks for the link.
For those who don’t know, the strategy is called Embrace, Extend, and Extinguish. The phase comes from Microsoft who used this to (try to) crush competing document editors, Java implementations, browsers, and operating systems. Other big tech companies employ similar strategies.
Facebook coming to the Fediverse is the Embrace phase of this process and that makes Mastodon, Lemmy, Kbin, Misskey, and Akkoma the competitors.
deleted by creator
I think the issue being missed here is that Meta will ultimately aim to suck all users into themselves, and then once they feel they’ve done enough of that, they will go completely closed, even potentially forking the protocol itself. If any legal attempt to stop this is made they will bog it down with hordes of lawyers for decades.
Their goal is not to help fediverse, it is recognising fediverse to be a threat and aiming to absorb it. Literally no different to how reddit slowly absorbed all internet forums into itself, killing the distributed internet.
Fediverse is attempting to bring back that distributed internet and they’re trying to find ways to kill it. All corporations seek monopoly, it’s how capitalism works.
Spot on. Anyone cooperating with them is a fool.
Well on the bright side, at least the fediverse is seen as a genuine threat to current social media. Hopefully it will stay that way.
If I wanted to see content from my racist Trumper uncle, I would just create a Facebook account. Keep Threads far away from the rest of the Fediverse. We don’t need to compete with them. Who cares if they’re way bigger with way more content if 99% of that content is garbage?
if 99% of that content is garbage?
Counterpoint: beans.
Serious note: I think the point of decentralized networks like this is that each instance will have to choose to federate with Threads or any other future corporate social media. If that sounds dangerous, welcome to the freedom of choice baybee! It sucks that the truth is that as long as we want this to be a free space where people can choose what and where they see content, that means some will choose to work with the big-easy-techgiant rather than take a harder approach because 99% of people aren’t that invested.
tbh, as a small instance, i might be defederating meta. im not a fan of the person that has everything through theft and scam.
Regardless of what anyone thinks about politics, nothing good will come by letting them in. I hope all current instances defederate, I know mine will.
Will lemmy.world defederate?
deleted by creator
Is there a way to block threads content?
I run my own instance here at twisti.ca and have the full intention of defederating
nice to hear that.
Embrace, Extend, Extinguish.
How many things will we let them ruin before we finally learn that corporations cannot be trusted?
Practically speaking? Everything.
Agreed, you cannot trust something that has the same ultimate goal as cancer. Endless infinite growth.
We have to stick to our guns and keep supporting the small instances.
Admins needs to strike first and defederate from Meta before they do.
What good does that do the small instances? And how does that harm Meta?
All that happens is:
- The small instances won’t get the extra activity that Meta users might bring
- Meta will not get the small amount of existing content on those small instances
That’s more a loss for us.
Ya pretty much double-edge sword
On one hand, Instagram users can bring a ton of content, which “should” be good for the overall website
On the other, it’s Meta lol
If I wanted all of the Instagram content I would be on Instagram. I don’t want all of that content cluttering up another space and overwhelming another space.
The difference is here you can manage your own feed and pick and choose. Many folks don’t want metas apps on their device but wouldn’t mind some of the content. Folks that don’t want it don’t have to sub but those that do can benefit second hand.
I don’t want Instagram content here! If I wanted Instagram-TikTok-type content I’d be there not here. I hope that crap stays away.
And yes, it’s Meta lol
Nobody wants Meta’s manipulated content. Let’s not forget why we call them Meta.
I don’t really see how it’d be a loss. The fediverse has existed for a long time alongside big centralized social media, and Threads ostensibly having ActivityPub support doesn’t really change that.
The loss of potential growth opportunity… And all the potential negative effects happen anyway, no matter if you federate or not.
How about you do that once Meta does anything other than run their own instance and help to popularize the concept of the fediverse?
That’s the “Embrace” step
We should be warry of anything big tech embraces. For example, Facebook reportedly uses servers running Linux. For that reason, we should all stop using Linux. Since Facebook has both an ios and an android app, we basically have to stop using our phones. We should shoot ourselves in the foot if there’s a chance we might get to bleed on them /s
Nice sarcasm, very helpful for discussion. Anyhow, this has applied to Linux as well: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish
To risk being serious here for a second- when Google+ launched, I remember being super bumbed out about how empty it felt and the fact that my friends couldn’t be on it yet because it was invite only. All the way back then, I had the idea that it would be really cool if there was a way for different social media websites to talk to each other directly instead of just users sharing links, so I could kind of take my friend group with me to Google+ even though they were still on Facebook. At the time I didn’t recognize either of them as really evil, I just though Google+ had a better interface. So all the way back then, 10+ years ago, I personally felt the lock in that established social networks had was way too strong for even well funded newcomers to overcome, and if there was some kind of standard for them to communicate with eachother, it would allow for a lot more innovation.
Today, not only is my vague idea a reality in the form of ActivityPub, the largest social media company in the world is actually embracing that open standard and funneling it’s users towards it. In the future, other huge corporate backed social media companies might feel pressured to build around it as well. We might be heading towards the commodification of social media, where you give put your social handle like an email address, and anyone who wants to follow you can do so from Kbin, Mastodon, Peertube, Threads, Tumblr, etc…
Today, I really do think of Meta and Mark Zuckerberg as genuinely evil. But I don’t look with suspicion on everything they do just because of that. For example, they typically do pay some amount of taxes. While I am suspicious that they aren’t paying enough, I don’t think theirs something inherently tainted about the money they pay with. That’s how I think about threads. It’s not currently federated. If I was suspicious of anything, it would be that being federated was a bold claim that brought a lot of attention to them, and that they might stall and even back out of ever doing it. That’s the play if you’re evil. If they actually federate, I view it as the fediverse has created such a great value proposition that supporting it enhances the value of Threads. Just because they are evil, it doesn’t mean everything they do is wrong and the opposite is right. Them being evil means they don’t do right reliably.
I think we need to accept the fact that we live in a world with Big Companies and think about how they can be better than they were before. Right now, I think Meta is actually making a socially good decision to support ActivityPub. And it might also be good for them. But just because it’s good for them, it doesn’t mean it’s bad for us. If we can find a way to structure incentives so big company’s interests end up aligning with ours, we’ll be in a much better place. Better than just saying anything Meta does is automatically wrong and nothing will be good until they are totally gone.
One thing I don’t understand is why would meta even federate with anyone outside of their own instances anyway?
Makes no sense to ever open up to allow any other instances in. Not like they are crying for users.
The fediverse just makes sense in their own bubble. Turn Facebook, Instagram, and their other apps into the fediverse and federate them all together.
I don’t expect them to ever open up to the actual fediverse. Same with BlueSky. I feel like all of these companies will USE the fediverse but in a closed bubble.
On one hand, I think it could be possible that Meta is planning to federate with the fediverse with the ultimate goal of destroying it and replacing it with their own instances. Similar to what Google did with XMPP according to this article. https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
On the other hand, I also think it could be possible Meta is wanting to federate with the fediverse just so it can increase it’s data collection many times quicker. Why manage servers when you can connect to other servers and suck up data as and when Threads users interact with other lemmy instances.
No idea which is more likely.
Interesting thoughts. I suppose Meta will collect what they want to collect, it’s what they do, and this is all public discussion, anyone can collect it for any reason. And I don’t doubt that their involvement in the fediverse is secretly nefarious in one way or another.
Where I think our current situation is different from the Google/XMPP thing, is that, a bunch of platforms are going down the tubes really quickly and lots of people are looking for the next thing all at the same time. It gives a lot of room for a good platform like this one to gain ground rapidly. As far as I’m concerned, if for example instagram federated, and I could browse some good feeds outside of meta’s app & privacy permissions hell, that would be a plus for me. If they subsequently pulled what Google did with XMPP and suddenly backed out, I wouldn’t react by moving to instagram exclusively and I can’t really see why any user would make such a move.
Thanks for the link about the whole google xmpp affair. Really well written. More people need to see this
You’re very welcome. I saw it in another post yesterday and have been sharing it where relevant.
I do think this sounds plausible. If they could become a dominant instance in the Fediverse, it would be easier to supplant it altogether. This is why decentralization is paramount.
Threads will be the dominant instance by a huge margin.
We don’t need them and they don’t need us.
Wasn’t Meta part of that as well with xmpp? They should not be trusted.
Not too sure if Meta was involved in the XMPP thing, but either way yes they shouldn’t be trusted.
nah zuckyfucky has always been about destroying competitors. It’s not about data, it’s about absolute dominance.
Like most big companies out there. Destroy competitors to be the main one that everyone has no choice but to go to.
Well? Apparently, they plan on making it happen. https://help.instagram.com/169559812696339
It’s a classic tactic, you open up compatibility with an open source platform so everyone moves to the fancy app that supports it all (threads) then they drop support and kill the platform (fediverse). They’ll do it and will likely be successful unless they’re blocked completely right now.
I don’t see why we can’t just stay on the fediverse, enjoy threads as long as meta wants to play ball, and then wave goodbye when they decide they don’t want to federate anymore. Nobody’s forcing anyone to move from the fediverse to meta, and I think the current demographic here is unlikely to volunteer for another walled garden experience.
Worst case scenario is we end up right back where we are now- a niche community prioritizing independence and decentralization.
The problem with federating with anything owned by meta is that it is a data syphon. I don’t think we can fully protect ourselves from that. If they want the data most of it is easy to come by by just having any ol mastodon account or running a malicious instance or just scraping what is public and inferring the rest. However we shouldn’t be inviting a threat like that into our backyard. We should definitely not be federating with them. Furthermore it gives them the opportunity to bloat things down with ads or DOS small instances with amounts of traffic and data they can’t handle and they could make it prohibitively expensive to run an instance that federates with them. Nipping those problems in the bud requires showing them the door early.
I feel like all of these companies will USE the fediverse but in a closed bubble.
Just like they did with the Internet.
Embrace, extend, extinguish
BlueSky will use their own protocol, so they will indeed be a closed bubble.
As for Meta, my (totally unjustified) hunch is that they’re expecting that other big names like Twitter, BlueSky, Google or Amazon will migrate or create their own ActivityPub services, and they want to be early adopters. If Threads is successful, I could see them migrating Facebook and Instagram too.
That’s my assessment also. This isn’t about extinguishing us, it’s about the other whales. AFAICT, they want and expect us us to be do well. (Delete could use a confirmation…)
That’s my assessment also. It’s not about us, it’s about the other whales. They actually want to see us doing well, afaict.
Once they’re federated they have full admin access. So they can see who liked posts, and lots of other info.
They could be doing this already, for all we know. We don’t know who owns all those little instances out there. Large corporations or government surveillance just need to set up a discreetly named instance or two and start subscribing, and they’ll get all the data they want. (In fact, could that be part of the reason for the explosion in silent bot accounts?)
Aw shit, yeah, obviously… The folks mining data are going to be using innocent looking nodes to do it… Okay you convinced me, I won’t pull the plug.
Oh… yeah… that’s totally it. By federating, they get to mine us for data the same as if we were on their service. Okay, I’ll pull the plug.
This reads like sarcasm but it isn’t.
They of course have no interest in growing the fediverse as an independent alternative, they want to use it for their own ends. They want to serve people the fediverse’s free content under their own umbrella and rules (and ads of course) to monetize stuff that doesn’t belong to them, or anyone else. It’s all pretty straightforward greed and capitalizing on an opportunity.
deleted by creator
Currently Reddit has significantly more users than Lemmy. Has that stopped people from signing up to Lemmy? Twitter has has significantly more users than Mastodon since forever. Has that stopped people from signing up for Mastodon? Has it killed Mastodon?
The common error I see in all the “Threads will kill the Fediverse” mania is that it assumes the same people who sign up for Threads would have otherwise signed up for Mastodon/Lemmy/Kdin/etc. 99.9% of them probably never would have. They want something that’s easy and just works; and they’re willing to let a company profit off their data to have it.
I don’t think those are good comparisons. The point he is trying to make is that when a user joins Lemmy and sees a two gaming subs, one on Lemmy.world and the other on a meta instance with more subscribers, that user will join the meta sub.
I do not want to see only corporations holding the keys to the majority of communities and if they are allowed in that will be their goal. Meta doesn’t give a shit if the 3dprinting sub has quality content, only that it is profitable for them. Corporations will choose profit over the users every time.
People will say “well if it gets bad or they start becoming bad actors then we can drop them” but that will just set us back to where we are right now. I would rather see us grow slow without corporations than fast with them.
The problem is that this doesn’t change the outcome.
To use your example, if we federate people will join the meta instance, if we don’t federate people won’t even know the lemmy.world instance exists, and even if they do they would still join the meta one if it’s bigger.
I totally agree with the sentiment, but I yet have to understand how not federating can change the outcome
The only way smaller instances can thrive and make a strong federation is by making the average person start to care more about privacy.
But you can’t do that if you can’t reach them in the first place
Sorta seems like a damned if you do, damned if you don’t type of situation.
That’s not what’s going to happen. I really don’t understand why people on Lemmy are so fussed about this, Meta are not building a lemmy instance, they are building a twitter clone. While yes you can access Threads content through Lemmy that doesn’t mean it’s going to affect the Lemmy ecosystem. Mastodon is going to be way more affected than Lemmy ever will be.
Just because they are on the Fediverse doesn’t mean it will make sense to use their services through all other Fediverse platforms and vice versa. Following an entire Lemmy “sub” on threads will be a shitty experience and Threads doesn’t have creation of subs as an option, the only viable equivalent features are user posts.
It’s about threads becoming the fediverse by virtue of their size and resources, and then making changes to the protocols which ultimately lock out the actual fediverse. It will be ‘fediverse, by Meta’ where everything is hosted and run by meta.
And how do you think defederating them will affect that at all?
They can just use their influence and say “here, W3C, add this and that to the protocol”.
How will a small mastodon server with a few thousand users stop that? Defederating them is useless.
Not totally sure, but I don’t think that negotiating with Threads on anything at any point is a winning strategy. They’ll win every time. Kind of a ‘give them an inch they take a mile’ situation in my head.
At least by staying separate the user base will have to make a conscious decision about where they want to spend time instead of letting Meta dictate that for them in the future.
It is harmful either way. Not a great situation for fediverse. I wouldn’t say defed is useless, it clearly does something. Effective? Not sure.
Not totally sure, but I don’t think that negotiating with Threads on anything at any point is a winning strategy. They’ll win every time. Kind of a ‘give them an inch they take a mile’ situation in my head.
Federating with them isn’t “negotiating” in any way.
Any fear of Threads controlling the protocol is out of our hands, because the protocol isn’t in the hands of the Mastodon devs, it’s in the hands of W3C. So no matter what Mastodon instances do, it won’t affect Threads and W3C.
At least by staying separate the user base will have to make a conscious decision about where they want to spend time instead of letting Meta dictate that for them in the future.
I think that by not federating with them, we’re TAKING AWAY the option for people to make a decision, and forcing the worst possible choice on them. Imagine I want to follow a guy that is really popular on Threads. If Mastodon federates with them, I can decide to make an account on Mastodon and follow the guy from the safety of a network that it not governed by algorithms that promote hate, or I can decide to make a Threads account and follow them there. It’s my choice.
But if Mastodon instances do NOT federate with Threads, the only way for me to follow that popular guy is by creating a Threads account and using the Threads app. By not federating, Mastodon removed my ability to choose and forced the worst possible option on me.
We should want MORE people using Mastodon, not fewer people. Let them follow Threads profiles from the safety of Mastodon.
Allowing their platform access to the fediverse is giving them something they want in exchange for access to a larger user base for us. It’s a form of trade or negotiation, however you want to look at it it’s a choice to exchange something of value.
You’re looking short term. The issue here is that Meta is going to be able to destroy the fediverse later, not right away.
People have been repeating these fearmongering ideas, but with nothing concrete.
How is Threads going to destroy the fediverse if we make it easier for people to choose to come to Mastodon?
And how do you think that pushing people towards Threads is going to save the Fediverse?
And, like I said, if the entire protocol that the fediverse runs on is independent of Mastodon, how can Mastodon even stop it?
Did you read the EEE article someone shared?
https://duckduckgo.com/?q=EEE+threads+meta+fediverse+embrace+extend+extinguish
Yep, their plan will be to take over the majority of the network, then start adding their own proprietary features and not adding features that the open source devs add, thereby taking control of the software.
EXACTLY! It only benefits us because it hugely increases the exposure of the fediverse to the outside world so people who ARE interested can merely jump over. It makes the fediverse more interesting for people like me who can “live” here and access the content I want.
two things:
have you considered that if this happens, once the fediverse’s exposure grows it will be thanks to Meta’s entrance, then the people that join the fediverse will do so by Meta’s means (in this case, Threads. But they can make some more after)? Making them the standard way to access the protocol, gradually making other communities less and less relevant.
It makes the fediverse more interesting for people like me who can “live” here and access the content I want.
I’m not trying to be rude by any means, but honestly, if the content you enjoy is on their platforms, just go there and enjoy it. You can be both there and here.
The exposure is still greater than the zero that currently exists. If only 1% see the stuff from the smaller instances and figure out what’s up, they’ll jump. That’s better than the current near 0. There’s not really a scenario where it reduces the activity here any further, only improves it.
Everyone is talking about defederating because of XMPP and EEE. But the very fact that we know about EEE means that it’s much less likely to succeed.
Zuck is seeing the metaverse crash and burn and he knows he needs to create the next hot new thing before even the boomers left on facebook get bored with it. Twitter crashing and burning is a perfect business opportunity, but he can’t just copy Twitter - it has to be “Twitter, but better”. Hence the fediverse.
From Meta’s standpoint, they don’t need the Fediverse. Meta operates at a vastly different scale. Mastodon took 7 years to reach ~10M users - Threads did that in a day or two. My guess is that Zuck is riding on the Fediverse buzzword. I’m sure whatever integration he builds in future will be limited.
TL;DR below:
I don’t think that FB even knows that lemmy exist, problem is they are so big they will crush us by accident.
Even back than with XMPP, Google didn’t kill it intentionally. No one expected it will be smaller than before google used it. I remember watching empty list where all friends were. But it happened, and I never thought that Google wanted to kill XMPP.
Meta WILL fuck up everything they touch with an aggressive amount of ads. I do not want this future.
One of the things that I feel isn’t being thought about much, is that it isn’t just Meta’s ideology and policies that will harm smaller instances and the fediverse itself; but the volume of data that their userbase will generate.
For smaller instances like mine running on six vcores, 4GB of memory, 512GB storage and a 120Mbps network…I feel like all it would take is a handful of users federating with them and the data flow alone would destroy our resources at the network if not disk level.
No, I don’t plan on allowing my instance to see or interact with theirs; but the point applies to all small instances and part time hobby servers. We don’t have the means to take on the data they could throw out into the federated network.
If that’s the case, then how will it be possible for the fediverse to scale up at all? If the goal is to replace Reddit and the like, then the goal is having millions of users regardless of if they are all coming from meta or from a whole ton of small instances.
I have some headroom for growth set aside. Since my instance is virtualized, its not too hard to scale it a bit. But there are hard limits due to other projects on the host.
For a lot of smaller instances that are currently running on cheaper VPS instances, they most likely have an upper limit to what their willing to pay for scaling up as growth happens. The only way to balance that is getting tooling in place to purge older data, but that isn’t really a good idea either.
Really though, any web platform that hits the public eye is going to face these issues over time. But allowing a large company to federate with a smaller instance will accelerate the issues. You also need to keep in mind that you don’t have all the control of these instances, as your users will cause you to federate with more and more content. Sure, you can purge and defederate, but that is a cat and mouse game.
Also, I cannot speak for the goals of others; but lemmon bar isn’t run with the goal of replacing reddit. It is meant to be a point of access to the fediverse. No more, no less.
Everyone is really scrambling now as if they really thought up to now that the Fediverse was immune to corpo bullshit
Well we would be if everyone just blocked them like gab or truth social etc. But I guess mainly Rothko is considering federating which is why everyone is freaking out