I'm actually trying to solve this issue on my own Lemmy app. It automatically switches instances when the requested one is down. Works only in the Feed right now and, of course, accounts are still instance-bound - but I will fix that soon.

I always wonder when people say something like this. I also develop a Lemmy app myself and don't understand this point, like are you afraid people will complain about your code cleanliness or commenting techniques?

I mean what extra work is there really? Moving secrets to environment variables is annoying, I get that at least.

I mean no offense to you at all, really, but when I check out other Lemmy apps I don't even bother with closed source ones since I can't possibly know if you just steal login information. Especially since this is so immensely easy with Lemmy.

Again, I'm not saying you do these things but it's always better being able to check yourself, you know?

Well it's open source, so whenever there's demand someone will fork and maintain it, if the original team ever leaves.

You could make like a circular shape on the screen with numbers correlating to the speed on different angles. Then maybe add some rectangle which points at the current speed and effectively changes the angle when the speed changes.

Oh wait..

This should be the community icon.

I just wished the Lemmy API docs were better lol.

There actually were a number of French nazis in France during German occupation. It's a topic often disregarded by the countries itself. E.g The Polish government tries to sweep that under the carpet.

I mean there even were Nazis in the US.

You already have 13 on your comment. You're like a lemmy celebrity now.

What is it like being famous?

takes notes for my own App 👀

Very good point! I think @TheButtonJustSpins@infosec.pub has a good idea on how to circumvent that.

I could make my own database with hashed passwords using postgreqsl and RLS, which is pretty secure. The User then decrypts the hashed passwords once on login and is simultaneously logged into multiple instances of Lemmy to get the JWT of each instance, which is then stored in SessionStorage or even in a Cookie if the User wants to which would make this a one-time process.

On signup the User could just register to one instance and then I just generate random 32 Character passwords and hash them with the Users' password, then get the JWTs and if cookies are enabled the that would only have to be done every year or so (or when the User deletes the Cookies).

This whole process is seems pretty easy, especially if you've done something like this before and I'm betting some other App Dev is already taking notes lmao.

Edit: Let's also do a thought experiment on what data will be leaked if I did this 1:1 and the database gets somehow hacked:

For each User:

1. Username (=> Gives away that you use Nemmy)
2. Hashed Passwords (=> Hashed passwords cannot be read if you don't have the original Users' password until we have access to quantum computers which can literally crack the encryption algorithm)

I'm making an App for Lemmy and I'm planning on adding that feature. I also want to make it so you only have to register once and the App can register you to all the instances you choose automatically.

Edit: The Webapp is Nemmy, also the Community !nemmy@lemmy.world

Edit2: Please note that Nemmy is early Alpha, so not really useable as a daily driver yet.

Edit3: Changed Community link to proper format

Actually, I'm guessing wefwef is using the Js client, which usually returns a 503 or 500 when something goes to shit on the instance.

I'm also developing an app for Lemmy and the only solution I found was to just keep request the data until the instance finally gives in to the pressure and works.

So it's less about "server is taking too long to respond" and more like "server responds instantly with a 503" because it's overloaded and can't handle any incoming requests.

I'm also guessing a lot of traffic comes from comments since the way of loading those is kinda stupid. (You load only the top layer and then for each comment you request the children, which sums up to a huge number of requests).

Lemmy should add more convenient APIs to reduce the amount of requests being made, maybe I'll do that myself once I'm done with the app.

Sorry for the long ass text.