Lemmys WebSockets are being phased out currently and thus all bugs regarding them (wrong vote counters, posts being pushed in at the top in the wrong categories, etc.) are gonna go away as soon as the transition is complete.
Lemmys WebSockets are being phased out currently and thus all bugs regarding them (wrong vote counters, posts being pushed in at the top in the wrong categories, etc.) are gonna go away as soon as the transition is complete.
Already resolved itself, the Nodes counter had the same dip so probably just servers not responding.
This is great! Thanks for your work.
GitHub would probably be the best place for feature requests.
That said the feature you’re talking about is already (sorta) available. You can head over to your settings and disable “Show read posts” which will hide posts you either A) opened or B) up- downvoted.
I recently contributed a mark post as read button to the lemmy-ui which will hopefully be merged & released soon-ish.
Yes a good search over the entire lemmyverse is gonna be vital… Does anyone know if there’s a project for a global search engine going?
They are planning to switch from WS to HTTP soon (backend is already switch over I think). Either way I don’t think there’s a documentation of the API itself yet, but you can just reverse engineer the calls from the calls from JS library or look at the backend code directly.
I partly agree, duplicate communities is something that needs to be addressed somehow.
Another problem is that you never actually receive a confirmation if your application was received and/or rejected, you are just sorta stuck in limbo after applying.
Just a “normal” http API as far as I know. There won’t be any live notifications/data on release but this can be added using polling at a later stage. It was mainly done because websockets just don’t scale well at all with thousands of users.