5 ms·
Some of these arguments start on really odd premises: > Imagine you're a rather small server and suddenly Eli Lilly and Company joins your instance. Today they
by icehawk 4y ago
Some of these arguments start on really odd premises:
> Imagine you're a rather small server and suddenly Eli Lilly and Company joins your instance. Today they have around 140K followers on Twitter and they are a publicly traded company. First of all with an account that large, every one of their posts will cause a lot of load on your infrastructure. Secondly though, they are a very interesting target to attack.
Why would Eli Lilly join some small instance? Why wouldn't they make their own instance? They have their own email and website after all. why be lilly@someoneelse.social when they could just be their own thing?
- pornel 4y agoIf they set up @social@lilly.com this solves the blue checkmark dilemmas too. It verifies their identity without implying status/endorsement/$8 flex.
- fragmede 4y agoSorta? There's nothing stopping a spammer from registering and running their own instance+user of @social@elilillypad.com, or any other variation that brandsight hasn't thought to register.
- pornel 4y agoYeah, domains as a UI element have flaws, but for better or worse they are the technological foundation of identity on the Internet.
- this_user 4y ago> Why wouldn't they make their own instance? Because it's not worth the effort. If anything, there are going to a commercial providers that run servers for companies in a bundled way where all of their clients use their servers. But more likely, they won't bother at all with this, because it's not an important part of their business.
- ilyt 4y agoAnd then the big public instance decides it's not worth even federating with small folks because if you block them they will come to your instance because you have "content" - a bunch of big names that use it - and also display their site's ads to them. ...aaaand we're back to Twitter in all but name