Honestly, my biggest concern is the raw amount of data being federated with Threads would push to the instance. I could see that becoming a problem, regardless of what your take on Meta is. We are talking about a potentially huge amount of extra stress on the server.
Fair, but surely the solution is a “wait and see” approach vs just blocking it completely? Maybe Threads overloads the server for… an hour? A day? Then someone turns it off.
Plus, if there’s a lot of data exchanged, doesn’t that just mean that a lot of SDF users want what’s on Threads, or that users on Threads care about what happens here? Either way, seems like the right move is to keep the channel open if possible.
No. I don’t want anything to do with anything Mark Zuckerberg touches, and I don’t want to have to wade thru an ocean of drivel from the type of users his services attract in order to socialize online.
The counterargument here is that there maybe so many posts etc. that users here can not effectively block them. I know that I am on Lemmy because I don’t want anything remotely like Twitter, ever. I don’t care to follow individuals, but communities.
Granted, I’m not entirely sure how the federation aspect works. If I understand it correctly, things like images etc. will only be stored if someone from this instance actively clicks on the post. However, does the sheer amount of posts being served affect the server itself? I don’t know enough to effectively comment here, I guess.
I think the performance impacts on other instances will depend on how Meta engineers integrate Federation. I’m sure it will involve some “Federation Gateway” service on their infra, whose job it is to cache content from and make requests to the Fediverse at large.
Honestly, my biggest concern is the raw amount of data being federated with Threads would push to the instance. I could see that becoming a problem, regardless of what your take on Meta is. We are talking about a potentially huge amount of extra stress on the server.
Fair, but surely the solution is a “wait and see” approach vs just blocking it completely? Maybe Threads overloads the server for… an hour? A day? Then someone turns it off.
Plus, if there’s a lot of data exchanged, doesn’t that just mean that a lot of SDF users want what’s on Threads, or that users on Threads care about what happens here? Either way, seems like the right move is to keep the channel open if possible.
No. I don’t want anything to do with anything Mark Zuckerberg touches, and I don’t want to have to wade thru an ocean of drivel from the type of users his services attract in order to socialize online.
Yeah, but you’re arguing for completely different reasons than I’m taking about. They raised a technical concern and that’s what I addressed.
The counterargument here is that there maybe so many posts etc. that users here can not effectively block them. I know that I am on Lemmy because I don’t want anything remotely like Twitter, ever. I don’t care to follow individuals, but communities.
Granted, I’m not entirely sure how the federation aspect works. If I understand it correctly, things like images etc. will only be stored if someone from this instance actively clicks on the post. However, does the sheer amount of posts being served affect the server itself? I don’t know enough to effectively comment here, I guess.
I think the performance impacts on other instances will depend on how Meta engineers integrate Federation. I’m sure it will involve some “Federation Gateway” service on their infra, whose job it is to cache content from and make requests to the Fediverse at large.
Preventative medicine is best. Stop it before it becomes a problem proactively.