▲ 76 ▼ Has there been any talk of lemmy.sdf.org preemptivly defederating from Meta/Threads? (lemmy.sdf.org) submitted 3 years ago by scroll_responsibly@lemmy.sdf.org to c/sdfpubnix@lemmy.sdf.org 91 comments fedilink hide all child comments
[+] cryomancer20x6@lemmy.sdf.org 17 points 3 years ago* (last edited 2 years ago) (1 child) [deleted] permalink fedilink source hideshow 2 child comments replies: [–] OneCardboardBox@lemmy.sdf.org 1 point 3 years ago* (3 children) 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. permalink fedilink source parent hideshow 6 child comments replies: [–] ThorrJo@lemmy.sdf.org 12 points 3 years ago (1 child) surely the solution is a “wait and see” approach 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. permalink fedilink source parent hideshow 2 child comments replies: [–] OneCardboardBox@lemmy.sdf.org 6 points 3 years ago 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. permalink fedilink source parent [+] cryomancer20x6@lemmy.sdf.org 6 points 3 years ago* (last edited 2 years ago) (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] OneCardboardBox@lemmy.sdf.org 1 point 3 years ago 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. permalink fedilink source parent [–] JuliusSeizure@lemmy.sdf.org 1 point 3 years ago Preventative medicine is best. Stop it before it becomes a problem proactively. permalink fedilink source parent
[–] OneCardboardBox@lemmy.sdf.org 1 point 3 years ago* (3 children) 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. permalink fedilink source parent hideshow 6 child comments replies: [–] ThorrJo@lemmy.sdf.org 12 points 3 years ago (1 child) surely the solution is a “wait and see” approach 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. permalink fedilink source parent hideshow 2 child comments replies: [–] OneCardboardBox@lemmy.sdf.org 6 points 3 years ago 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. permalink fedilink source parent [+] cryomancer20x6@lemmy.sdf.org 6 points 3 years ago* (last edited 2 years ago) (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] OneCardboardBox@lemmy.sdf.org 1 point 3 years ago 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. permalink fedilink source parent [–] JuliusSeizure@lemmy.sdf.org 1 point 3 years ago Preventative medicine is best. Stop it before it becomes a problem proactively. permalink fedilink source parent
[–] ThorrJo@lemmy.sdf.org 12 points 3 years ago (1 child) surely the solution is a “wait and see” approach 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. permalink fedilink source parent hideshow 2 child comments replies: [–] OneCardboardBox@lemmy.sdf.org 6 points 3 years ago 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. permalink fedilink source parent
[–] OneCardboardBox@lemmy.sdf.org 6 points 3 years ago 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. permalink fedilink source parent
[+] cryomancer20x6@lemmy.sdf.org 6 points 3 years ago* (last edited 2 years ago) (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] OneCardboardBox@lemmy.sdf.org 1 point 3 years ago 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. permalink fedilink source parent
[–] OneCardboardBox@lemmy.sdf.org 1 point 3 years ago 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. permalink fedilink source parent
[–] JuliusSeizure@lemmy.sdf.org 1 point 3 years ago Preventative medicine is best. Stop it before it becomes a problem proactively. permalink fedilink source parent