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.
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.
It seems this is the „find out“ part of his plan.
While I agree, lemmy seems to generate a short description of the linked URL by itself which is already very useful.
Interesting read, thanks
On one hand I would love to know all these secrets on the other… A little bit of blissful ignorance might not be the worst thing.
Yeah that’s probably not gonna happen, they have communicated that they won’t give up without a fight.
Absolutely, I tried switching to it using bridges for all my messaging accounts and the performance was abhorrent, mind you just me, a single user on a self hosted instance.
Discord is not a bad bet, but I think they still have like 2-4years in them.
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.
All smoke and mirrors on planet Elon
I partly agree, duplicate communities is something that needs to be addressed somehow.
After going public your whole modus operandi switches from “having a well running company that generates a steady income” to “generating more revenue every single year or loosing everything because your share holders dump you”
They would probably have to drop their plans of going public for me to reconsider. Of course I know this is never ever gonna happen in this reality…
I added a mark as read button to the posts but now patiently waiting till the WebSockets -> REST API transition is complete so it can get merged.
The front end needs a lot of work… Every bit is appreciated and the maintainers are pretty fast at reviewing and providing feedback which is nice to see.