hey you know what would be a very interesting way to scale large instances
literally make a second mastodon.social
and redirect all new users there, the two hosted independently and maybe even managed differently or organized in regions
and potentially some addition that help the two share the local timeline efficiently
i mean that's how the network is *designed* to scale
@CobaltVelvet yeah but the issue here is that a lot of blogs/articles/new users who don't know better link directly to mastodon.social. so yeah i could open another instance but it wouldn't like, help much? unless we sneakily redirect from our frontpage to the other one, but that would mess with people who want to login
@gargron yeah more like that, i was thinking about leaving the log in as is, but redirecting registrations to the new instance(s)
@gargron well since you'd own both we can always imagine ways around that
i mean it's really a long-term solution to a very hard future problem (scaling vertically pg)
@CobaltVelvet @Gargron maybe something based on BDR (multi-master) (coming soonish for pg10 as a plugin) would be cool, but there's of course some gotchas (specially if you modify objects from two locations at the same time)
Tsatnosk
@CobaltVelvet @gargron what happens when people return to m.s to log in on those new registrations?
Multiplex login that redirect to different subdomains? O.o
@CobaltVelvet yes but the form is embedded on the page and you can't post to another website because of CSRF