I haven't seen a feature for that yet, maybe I missed it? If indeed it is absent, I suggest !lemmywishlist@lemmy.ml - posting this
RoundSparrow
I've been testing for hours, and "Subscribe Pending" went away for the first hour or so after the restart of lemmy.ml - but now I'm getting them again. The underlying issue still seems there.
I think lemmy.ml has more posts, comments, likes in the database due to historic reasons - and the backend is timing out, PostgreSQL not keeping up to application timeout. I have seen the problem on Beehaw, Lemmy.world when they are busy and throwing nginx 500 errors on their front page.
Wonder if I can finally sub to lemmy.ml communities…
From my remote instance, I've been subbing to lemmy.ml communuites about every 2 or 3 minutes, and it just now started to jam up. I'm speculating that the server restart fixed the problem for the first hour or so, but now it's back. Open GitHub Issue: https://github.com/LemmyNet/lemmy/issues/3101
Thank you for sharing.
Were these remote instance communities or local ones?
I've only seen it happen with remote instance ones. I'm curious what the code is doing.
I found another documentation page that actually tells you how to get the "v3" version....
https://join-lemmy.org/docs/en/contributors/04-api.html
That needs to be part of the "Lemmy from Scratch" documentation page too.
I knew it was v3 because I saw a webapp failure on one of the Lemmy instance (lemmy.ml) I was using ;) We need to update those install documents.
It seems right now I can get a client to load, but websockets aren't working. Others on Reddit reported the same issue: https://old.reddit.com/r/Lemmy/comments/142sszq/spinning_up_lemmy_websockets_dont_connect/
EDIT: Ok, I solved the websocket problem by using proper nginx config that the instructions said. I was confused about the domain names with the certification generation as I already had some nginx certs for other subdomains in place.
A couple of us have been detailing experience and problems with those instructions:
!lemmy_admin is the official place for discussing install and being a server administrator
My guess is to leave open the possibility of adding HashTag support within the app. YouTube hash HashTags that allow you to jump between channels... I could see something like that working.
Is that the correct was to specify the version?
No, I had to dig around too, the correct command is:
curl localhost:8536/api/v3/site
Most common cause is people changing their language settings in their profile. It's a daily occurrence. The app really needs to tell people "25 messages not displayed because you are only viewing in Spanish".