I don’t think such an aggregator is required. Interoperability is smooth enough that you don’t have to think about different instances most of the time. I’ve only really noticed two points that would be confusing:
- the sign up process
- the “local”/“all” distinction
So I think what we really need to do to make this platform intuitive to people that aren’t already familiar with it is:
- Somehow streamline signing up. The process from googling Lemmy to having an account on an instance should not be confusing or intimidating.
- Filter by “all” by default. The default should cater to the users which are less likely to figure it out themselves. If you don’t understand what instances are and what “local” vs “all” means, then you are probably here for the “all” experience. If you understand and really want “local” you are probably fine having to set it yourself.
It depends on what your bottleneck is. For example on my system I get
$ systemd-analyze Startup finished in 11.976s (firmware) + 3.879s (loader) + 2.013s (kernel) + 157ms (initrd) + 6.354s (userspace) = 24.382s graphical.target reached after 6.316s in userspace.
The kernel boot process is only responsible for 2s of my boot time. So even if this does end up improving boot times, there’s very little it can do. The real improvement for me would be to choose a faster-booting m/b. You can run
systemd-analyze
on your setup to see if the kernel boot time is more significant for you.