Skip Navigation

User banner
Posts
30
Comments
503
Joined
2 yr. ago

  • Ok thank you that's helpful. I'll take a look at those two instances and what's going on.

  • I'm monitoring the 0.19 release. If you're in the 152 beta it should have some compatibility fixes (and currently rolling that out to everyone).

  • Connect dev here, I'm monitoring and releasing a fix (v152)

  • Is this happening on all instances or only a specific instance? Does it happen even if you're a guest user or signed out?

  • Appreciation Post

    Jump
  • I'm glad you're enjoying it and thank you for the appreciation!

  • Thanks for the feedback. I'll take a look at that issue!

  • I'm still here :) just taking a bit of a break but still reading everything in this community.

  • I'm ok just taking some time for personal things. Regular updates will resume soon :)

  • I'll take a look. Thanks for the feedback!

  • Can you try this on v150? I made some optimizations to loading the subscription list although I don't have nearly as many subscriptions as you do.

  • It's the messages at the bottom of the screen For example after hiding a post.

  • Thanks I'll take a look!

  • Oh thank you that's helpful. I'll take a look at improving this for the next release tomorrow.

  • Hi, are you on beta version 146? I can take a look!

    How many subscriptions about do you have?

  • What version is this happening on? From the profile button?

  • Hi, thanks for the feedback. I believe this should now be fixed on beta 146.

  • Thanks will have this fixed in the next release (tomorrow).

    Edit: now fixed on 146

  • Will add this in the next release. Thanks for the feedback!

  • Good idea, I'll add this in the next release (tomorrow).

  • Hi, I think this is caused by a couple things. Lemmy has a ratelimit on the number of API requests you can send and also marking posts as read and a lot of filters cause the app to pull more since some content gets filtered out.

    I think a possible solution from my side might be instead of sending the read calls right away (so quickly scrolling past everything will send a lot of API calls quickly) would be to queue them and release it in chunks.