> Federation IMO solves problems on the developer side:
I couldn't disagree more.
First, nobody cares about this. This has no value proposition to users. It shouldn't even be a topic of conversation.
Second, IMHO it's not even true. It's a bit like how you split a monolithic into microservices. Now you've created a bunch of versioning and orchestration problems where you have to deal with network issues. Federation means talking to third-parties, dealing with them being unreachable or behaving badly. It's a whole new class of problems.
> f Twitter were federated with other services, basically you'd have a way to reach select Twitter users from a saner place.
There's a ton of hand-waving that goes along with this statement. It's like if you tried to cut out talking to Verizon on your POTS exchange. Well, technically you can do that but then you can't talk to the customers on that service and they can't talk to you.
> First, nobody cares about this. This has no value proposition to users. It shouldn't even be a topic of conversation.
Did you quote the wrong part? Obviously, value proposition to developers isn't a value proposition to users a lot of the time.
Second, this is a dev-centric forum.
> There's a ton of hand-waving that goes along with this statement. It's like if you tried to cut out talking to Verizon on your POTS exchange. Well, technically you can do that but then you can't talk to the customers on that service and they can't talk to you.
It's exactly like that, yes. That's the very point: that if say, Verizon starts doing something unpleasant like spamming, they can find themselves cut off from the rest of the system.
Meanwhile, unlike with POTS, any alternative is accessible to Verizon users, so they could move over with minimal pain.
The ideal is that in a federated system, there's always alternatives, and no instance is too big to fail.
I couldn't disagree more.
First, nobody cares about this. This has no value proposition to users. It shouldn't even be a topic of conversation.
Second, IMHO it's not even true. It's a bit like how you split a monolithic into microservices. Now you've created a bunch of versioning and orchestration problems where you have to deal with network issues. Federation means talking to third-parties, dealing with them being unreachable or behaving badly. It's a whole new class of problems.
> f Twitter were federated with other services, basically you'd have a way to reach select Twitter users from a saner place.
There's a ton of hand-waving that goes along with this statement. It's like if you tried to cut out talking to Verizon on your POTS exchange. Well, technically you can do that but then you can't talk to the customers on that service and they can't talk to you.