I’ve been frequently having posts and replies that I’m trying to make just sit with a spinning wheel and never actually going through. I suspect this post may do the same but hopefully I’ll eventually get it posted. This happens when I’m posting to a local community or to a federated community and from both desktop and mobile (both web, there isn’t a client for my phone). Is this a known bug?
I will certainly pay attention in the future.
Related to the URL thing, is Lemmy supposed to pull a thumbnail from links and add that to the post? I linked an image directly on one of my posts and it shows up in the thread view but all of the other posts are just the grey box where I would think a thumbnail from the article would be (based on Reddit behavior, admittedly).
Yes, it’s supposed to pull a thumbnail, but it can be a bit rough around the edges. Working on improving this is one of my goals for lemm.ee right now!
Having the posting issue right now… I hit the reply button at 4:27 PM EDT and it’s still spinning.
https://i.postimg.cc/Wp9nSxfL/Screenshot-from-2023-06-18-16-28-22.png
Just to add to this… it’s pretty weird… I posted the above reply and everything responded very quickly… I went back to the other window to repost, refreshed the page, copied my text in the new field… and now it’s also just continually spinning.
UPDATE: Did the same thing and created a new post in the community and that went through just fine… but trying to make the same reply a third time still is ending in continual spinning. Giving up on that reply… but if you’re going to look at logs it’ll be between 4:27PM and 4:36PM EDT (Eastern).
So, looking at the logs, I can see that exactly around that time we had a big spike in failed requests on lemm.ee. Particularly at 4:36PM, there was a brief moment when failed requests actually exceeded successful requests. The system recovered on it’s own about 15 minutes later, but there have been two periods during today as well when I see similar short spikes in failed requests.
It appears to be correlated with incoming traffic, but it’s not clear yet whether this traffic is coming from our own users or from other instances. I will keep investigating, but for now, I would just recommend refreshing the page and reposting the comment if it comes up again. I’m hopeful that software optimizations will bring some relief for our servers very soon. And sorry that you have to deal with this!
I have a new finding! It seems that in some cases, not selecting a language from the dropdown below the comment text box will always cause the comment submission to fail.
The next time you want to respond to somebody and it doesn’t work: try selecting English from the dropdown first before hitting “Reply”. Let me know if that consistently solves the issue for you!
I never realized that there was a language selection on replies. When I create posts I always select English but it’s interesting that at the time I was having the issues this wasn’t the differentiating factor. Perhaps the parent comment was something different?
deleted by creator