So, as any self-respecting datahoarder and selfhoster, I have my server rack populated with a few machines, churning along as they tend to my hobby-related projects. Now that I’ve started using Lemmy I’m toying with the idea of selfhosting an instance, as I have both the hardware, bandwidth, and skillset for it.
So my question is: Are there any advantages to it? And other than time and resources, what are the downsides?
An option to remove unauthenticated access to the main feed would be a great fix for the first issue, and probably would be desirable on single user/invite only instances where the admins don’t want random people taking up server resources with the web interface
This isn’t a terrible idea, but it’s also important to understand single-user and tiny invite-only instances as analogous to “leechers” in the torrenting world. The federation load that an instance instance imposed on other instances depends much more on the number of communities it subscribes to than the number of active users. If a user stops using Lemmy but leaves their instance up, it’s generating federation load for no reason.
Tiny instances are inefficient, and while it is desirable for the network to be able to scale to the point where it can reasonably support lots of them anyway, right now federation queues are backed up and messages are frequently getting dropped. Encouraging lots MORE tiny instances is probably not the efficient thing right this second. Rather, we’d want more users joining mid-sized instances that are not overloaded locally and that are making efficient use of the federation load they generate by using it to serve 100-1000 users rather than 1 or 2.