this post was submitted on 11 Jun 2023
9 points (100.0% liked)
Lemmy.World Announcements
29157 readers
474 users here now
This Community is intended for posts about the Lemmy.world server by the admins.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world/
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Support e-mail
Any support requests are best sent to [email protected] e-mail.
Report contact
- DM https://lemmy.world/u/lwreport
- Email [email protected] (PGP Supported)
Donations ๐
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
Join the team
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
How is it a hassle? It seems perfect-enough to me.
At least on Android, I can't respond to or vote on responses that show up in my inbox. Clicking on the message itself does nothing instead of taking me to the message. The UI definitely needs improvements in usability but it's still very much in development as far as I could tell.
Oh! I just figured that out -- try tapping-and-holding for a second. Some menu options should come up then.
Thanks I'll give that a try. Upvote/downvote/reply should all just appear by default though IMO
Miner's android, I am using jerboa, and they are appearing automatically for me.
Hmm, maybe my app is just borked then. I'll try wiping app data and reinstalling.
I think it's having trouble keeping up with the rush of users. I'll admit though it's pretty frustrating that my upvotes don't register. I get "timeout" after a few seconds.
I only seem to be having that problem with Jeroba. In the browser it seems to work fine with the lemmies I've tried
At first it was both, couldn't upvote on the browser or Jerboa. Since this afternoon though I haven't been getting a timeout error on Jerboa.
Edit: nevermind it's happening again. Maybe it's happening due to server load?