Yes, refreshing the page fixes it. Ive even had some posts load with the comments from a different post. Again, refreshing fixes this.
Lemmy Support
Support / questions about Lemmy.
Ugh I hadn't seen the comments issue yet. Sounds like a major problem if you can't even be sure the comment you're responding to was meant to be part of that post.
It doesn't happen very often, and usually it's very obvious when the comments have nothing to do with the post.
From what I've noticed, it happens with comments that I've already read from a previous post. So it may be some sort of caching issue.
Edit:typo
No. Does this only happen when you're accessing a community from your instance?
I was reading posts in the mycology community
Maybe you were hallucinating. :-P
j/k, it's a bug. I've seen it happen a few times.
Sheesh I haven't even started trying to grow that kind of mushroom yet, and already the jokes are flying high! 😛
(And wow, lemmy's method of emoji's is weird... if I type :-p I get a pop-up dialog. I then have to delete the -p and I get back to regular smilies, but only a few. Then while scrolling through them the pop-up changed to a whole new list of the emojis I actually expected... WTF?)
wow, lemmy’s method of emoji’s is weird…
It's infuriating. If someone knows how to disable let us know
A quick follow-up... so it turns out the whole emoji thing here relies on you typing a colon and then the NAME of the emoji. If you wants smilies you type ":s" and it will give you that list. Of course this presumes you know what Lemmy named all the emojis, and there doesn't seem to be a way to bring up the whole list of what's available. It just doesn't make any sense.
bizarre - I appreciate you doing the legwork
I've been seeing a variety of weird junk happening, including:
- When viewing a post, love loads a different post after a while.
- The frontpage scrolls wildly and won't stop still you close the tab and reopen.
- Posts with the wrong sort criteria live loading at the top of the frontpage.
Without evidence, I attribute all these things to websockets being weird on overloaded servers, and I expect them to get sorted in v18 when the websockets API gets deprecated.