Conversation

Notices

1. simsa04 (simsa04@gnusocial.net)'s status on Wednesday, 25-Aug-2021 02:38:31 UTC simsa04
   The simple answer seems to me: Join the biggest instances. Their amount of users have the best chance of reaching more accounts of other instances than smaller or more nice instances.
   
   Also, it is because bigger instances with more poeple raise the likelihood that most notices of one conversation thread are actually covered/displayed that bigger instances turn out to grow even more whereas smaller ones rather stay small or perish. This is centralisation that kind of mimicks the centralised commercial platforms.
   • LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} repeated this.
   • LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Wednesday, 25-Aug-2021 02:43:28 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}

     in reply to
     That indeed is a major problem in the federated space. One of the few things that I think Evan did right in the Pump.io transition was that he set up a bunch of public pump servers and a randomizer that would take new users to the sign up page of a random public instance. It helped keep Pump instances from growing huge relative to other public instances.
   • LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Wednesday, 25-Aug-2021 02:55:57 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
     He did, but he kept control of them, so when his funds ran short, most of them disappeared. I've thought about deploying a Federati #Pump.io instance, but it runs atop #Node.js. I'd want to rent a completely separate server ( #VPS ) for it, so nothing else is affected if a poorly understood #JavaScript engine goes haywire.