@akatsukilevi I think it is mostly a good thing but its so big some people are worried it could flood the fediverse and drown out the existing network.
I think they could start federating by end of January.
@fedi Yeah, this is quite a concern, but I think the devs are considering it, they probably will think on something to avoid drowning out the network
One way I think could do well for this is for the fedi support to be opt-in. So instead of all blogs on Tumblr to automatically become part of the fediverse, the users can opt-in manually, which will definitively decrease the sudden flood
@fedi I'm supportive of the concept of federating with Tumblr, but it would end up being the largest instance in the fediverse, with millions of users.
I'm concerned that the sheer amount of activities coming out of one place could DDoS modestly-sized instances, unless we all come up with a way to safely deal with so much inbound traffic on the federated timeline.
A temporary bandaid might be to disable the Federated / Whole Known Network tab, and have actors only start ingesting activities from people they follow + boosted activities + followed tags. Even then, that might be a reach.
@ilinamorato @darnell @deadsuperhero @fedi I think there's a main blog that you can follow from, and then side blogs where you can post, and people can follow you, but you can't follow others from your side blogs
I only have one blog so I'm not sure
@deadsuperhero @fedi as the Fediverse (and particularly Mastodon) grows, this is absolutely a problem they're going to have to deal with eventually. Tumblr (and maybe Flickr?) federating moves up the timeline, but Mastodon.Social or some other instance was going to prompt that change eventually anyway.
Some sort of partial or double-opt-in federation type is almost inevitable. Might as well figure it out before Twitter or some other really massive service gets sold again and federates.