Hi everyone. Phenomenal job with the app, it’s really looking like it could replace reddit with no trouble.
I’m getting timeout issues though, every time I upvote something. I’m sure it’s nothing but I wanted to give you the heads-up.
One more suggestion is to make it easier to find communities on here! Then it’ll be perfect.
Thanks again :)
Timeouts might be from the server struggling since the reddit blackout is bringing in a lot of users at the same time right now. I’d wait a few days and see if the issue disappears or maybe a second account on a lesser known instance might help.
I’ve noticed (although on the .ml instance) that even whenever GET requests go through fine (albeit a bit slow) POST requests don’t actually return a response. After 60 seconds they will timeout, even if the operation actually does complete successfully. This happens mainly on voting and making comments from what I see.
That’s pretty common. Database reads are much lighter operations than writes, and you can cache responses to heavily alleviate the strain of those requests.
There’s no real way to get around database writes though. Each one of those has to go through the DB eventually. You can do things to mitigate it like putting the messages in a queue to be bul-inserted in batches, but it’s much harder to optimize write performance than it is to optimize reads.
Oh absolutely. I would expect the response to take longer. But what I’m saying is that even once the operation is complete, the server will not return a response to you. You can simply refresh to see that your request did go through, but you will still be waiting for a response.
I seem to be getting them about 30 seconds after each interaction, such as upvoting or clicking on a thread to load comments.
I think its best to just use the lemmy web instance interface to subscribe to communities on all kinds of instances, and then they just show up in Jerboa. :)
Timeouts may be because you are using an overloaded instance like lemmy.ml when you should spread out on other instances. :)
I wish there were a way to transfer/propagate a single identity across multiple instances. I would love to use a less crowded instance, but I don’t want to keep creating new accounts.
Maybe it will come in the future. But I also think we should not try and keep the same identity across servers. Lemmy is made to be pseudo anonymous, and you should not use your real name on any instance.
It may go against habit though, since the Internet today encourages people to log in everywhere using the same identity. Because then all your behavior can be monitored and data can be extracted that is extreamly profitable.
Fair enough.
Although does this create a separate problem where every instance you sign up to has your email address? Or is email option in most instances?
Email is optional on most instance signups i believe. It can be useful if you forget your password however. But if you use a password manager, that will never happen anyway.
It can also be useful if you want to get notified when your account is approved. But most instances will approve your account of course, the message you fill in is just to filter out the bots.
Another option is to use an email that is temporarily set up for that purpose only. In Fastmail, you have Masked Email so you can create emails for specific sites, such as different Lemmy instances or anything else. Im sure other email providers have something similar.
At least for me, I noticed subs worked but wouldn’t show up in the list UNTIL I restarted the app.
I’d imaging it is a massive influx of users periodically overloading it.
I’m having this same issue, but it’s always on the app and never on the browser.
Yeah this is quite an annoying issue so far. It keeps popping up randomly. Not sure if it’s related, but sometimes after this happens I also get a blank screen. I can live with it tho, growing pains are to be expected
+1 on the blank screen, it forces me to use the back button on my phone then click the post again. Quite annoying but still better than not having the app.
Possibly related to this: Expect some brief restarts today (Jun 12 CET).
It is also happening to me, both on the app and the Web UI
