Post 9prc1M38DJnxcsvREO by msh@coales.co
 (DIR) More posts by msh@coales.co
 (DIR) Post #9prVDcoX0h2JPs04rQ by ink_slinger@coales.co
       2019-12-11T17:10:51Z
       
       1 likes, 0 repeats
       
       Yes, it's absolutely silly that Twitter is trying to created an "open" protocol that will basically be ActivityPub (except that, despite technically being open, they'll effectively control it, like Google does with Android).But do we really want Twitter to adopt AP and become part of the fediverse? Sure, we could choose not to federate, but if we do federate with them, they'll drown out everyone else. Federated timelines would effectively just be a fire hose of tweets.
       
 (DIR) Post #9prVDd6bvTUwJwSW2a by ink_slinger@coales.co
       2019-12-11T17:17:28Z
       
       1 likes, 0 repeats
       
       Also, the notion that the Twitter decentralization protocol would somehow involve blockchain is hilarious. Gotta pull a terabyte of data just to view your timeline.I mean, if this protocol actually materializes, it won't use blockchain. That's just bullshit to get investors hot, but the idea that it ever would is hilarious to think about.
       
 (DIR) Post #9prVFwxN5jfaSzFAdE by adasauce@radical.town
       2019-12-11T17:18:42Z
       
       1 likes, 0 repeats
       
       @ink_slinger oh I hadn't heard about this? twitter looking to extinguish fediverse?
       
 (DIR) Post #9prbHZTBz8lbvaHfCS by msh@coales.co
       2019-12-11T18:27:00Z
       
       0 likes, 0 repeats
       
       @ink_slinger it looks like Twitter figures it is easier to be the steward of a standard than to embrace and extend an established one to achieve their goal...that goal being false decentralisation like Google has been pushing towards with email.Basically control the protocol as well as provide the dominant instance from the start. Distributed in architecture only.
       
 (DIR) Post #9prc1L5ZmkAMeB3sP2 by ink_slinger@coales.co
       2019-12-11T17:29:35Z
       
       0 likes, 0 repeats
       
       @adasauce Seems that way. Here's the relevant jack thread: https://twitter.com/jack/status/1204766078468911106
       
 (DIR) Post #9prc1LP4cFlJceBRnE by adasauce@radical.town
       2019-12-11T17:43:58Z
       
       0 likes, 0 repeats
       
       @ink_slinger whole thread is yuck.on one side, i hope they adopt AP and its easier for people to get off twitter and move to another  AP instance.on the other hand, keep greasy megacorps off the fedi. we know they're going to be scraping the whole thing for tracking and targeting, then the profiles they're keeping on users will extend beyond twitter. instance admins would have to draw a pretty hard line to block federation with twitter, and I'm most of the big ones (.social, etc) would have enough pressure from users to connect to twitter that admins would get a lot of backlash for blocking.
       
 (DIR) Post #9prc1Ll3IXLKioT03E by ink_slinger@coales.co
       2019-12-11T17:52:15Z
       
       0 likes, 0 repeats
       
       @adasauce On the other hand, a lot of people, even on the big instances, are here specifically because they wanted to get away from Twitter. That could be a hard balancing act for some admins (whereas, for others, it would be easy to draw a clear line and say "no").
       
 (DIR) Post #9prc1M38DJnxcsvREO by msh@coales.co
       2019-12-11T18:35:16Z
       
       0 likes, 0 repeats
       
       @ink_slinger @adasauce if Twitter federated I would lean towards an instance level silence to start with. That would keep the federated timeline relatively clean but allow local users to interact with selected Twitter users.I also do not subscribe to any Mastodon relays as a way to keep my federated timeline quieter. Then even if Twitter shows up there it would be mostly be limited to tweets that locally known accounts interact with.