This is likely bugs in Lemmy's websockets API which are fixed in v0.18.0. Check the footer on the frontpage of your instance to see if that version has been rolled out there, if not it will be soon and should fix these issues.
this post was submitted on 24 Jun 2023
3 points (100.0% liked)
Lemmy
12443 readers
55 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to [email protected].
founded 4 years ago
MODERATORS