• 1 Post
  • 12 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle



  • I felt slightly frustrated when I tried some Lemmy apps and they only offer a few largest instances in the initial setup and leave people to discover/find smaller instances by themselves.

    It is understandable that they don’t want to present a thousand choices and confuse people, or get people to sign up for an instance that disappears a week later. Also, larger instances tend to get a snowball effect by receiving more donations / volunteers and scale better, other nodes are also more likely to help them if there are e.g. federation problems.

    However this effectively promotes an centralized ecosystem that both depends on and burdens a small number of key instances.


  • Thank you for looking into it. I tried subscribing again and it went through, and several threads just got through to kbinMeta over there, so I’ll cautiously say it seems to be fixed now.

    Glad to hear federation is being worked on, it does feel it needs to be more robust to live up to the promise that one gets the same experience no matter which instance (local or remote) one view a magazine from. (I’m not being critical, interoperability is always a hard problem no matter which stage of development it is)

    Again, thanks for the good work and for bringing kbin to us!






    • Still somewhat annoyed that there is no seat belt on the shuttle, even if it is to maintain continuity with TOS. M’Benga looked like he was going to bang his head and get a concussion when they were landing.

    • La’an: They won’t see us coming.
      Zac: We totally saw you from the other side of the planet a hemisphere away.

    • What was Zac trying to accomplish? He lured them there with the Starfleet Delta, but he was not going to hitch a ride home. He expected whatever ship that comes to inspect to… forget and go away, or suffer some disastrous result when the crew become unable to function? Why not just stay low and be king if he wasn’t planning to leave?



  • Currently there are (is?) content-only servers like https://lemmit.online/ .

    I have been thinking perhaps the idea can be carried further and we can separate the user-facing front end and the back end.

    Imagine having multiple front end servers (e.g. fe1.site, fe2.site, … fe5.site) all connecting to the same user database and the same back end server which serves the communities and contents etc (call it be.site for example). A user signs up once and can login to any front end server with the same account, create a community /c/whatever on e.g. fe3 and it will be accessible automatically on fe1-fe5.

    This is in addition to the back end federating with outside servers. Outside sees the community as be.site/c/whatever and users there as be.site/u/whoever. (or maybe make an alias like www.site/c/whatever www.site/u/whoever).

    Additional front end servers can be added to spread the load if there are many users. If done right the users shouldn’t even need to choose (or be aware of) which front end server they log on to, it can be automatically load-balanced. Another idea would be that special front end servers can be created to only serve API calls for apps.

    I’m not sure if this will have bottleneck somewhere else, but I think this is an interesting idea to explore.