Yes, it’s a lemmy thing that when the first personnel on your instance subscribes, it takes like a page of posts and then only the new ones going forward.
Lemmit.online used to have a way to add new subreddits, but it seems they have stopped accepting new ones. Must have got a bit too big to handle.
There’s an instance lemmit.online that mirrors reddit content and you can subscribe to the communities.
Like others said, there is so much content it’s hard to get conversations going, it works better to cross post interesting content to a lemmy community.
It’s explained here: https://join-lemmy.org/docs/users/03-votes-and-ranking.html
Basically, Hot and Active show posts based on upvotes minus down votes, with a time decay so older posts rank lower.
Hot has the time decay based on created time, so you’ll basically only see posts from the last day or so.
Active has the time decay based on the most recent comment, so if someone comments it can bring an old post back to the top.
There is also Scaled (if your instance has updated to 0.19), which is like Hot but posts from communities with less active users will get a boost so you don’t miss out on posts in small communities from being drowned out by big community posts with lists of upvotes.
Was it Nextcloud or Nextcloud All in One? I’ve just realised that the Nextcloud docker image I use is maintained by Docker, not Nextcloud. It’s this one: https://hub.docker.com/_/nextcloud/
I use Docker-compose and even the examples there don’t have any socket access.
The all in one image apparently uses Traefik, which seems weird to use an auto configuring reverse proxy for an all in one image where you know the lay of the land. Traefik requires access to the docker socket for auto configuration. But you can proxy the requests to limit access to only what it needs if you really want to use it.
Lemmy has heaps of apps and a web interface. Which app are you using?
Lemmy has this functionality, you just need to join a server that enabled it.
I’ve never known a reason to expose the docker socket to Nextcloud. It’s certainly not required, I’ve run Nextcloud for years without ever granting it socket access.
Most of the things on that linked page seem to be for Docker rather than Nextcloud, and relate to non-standard configuration. As someone who is not a political target, I’d be pretty happy that following Nextcloud’s setup guide and hardening guide is enough.
I also didn’t mention it, but I geoblock access from outside my country as a general rule.
Unlike most here, I’m not as concerned with opening things up. The two general guidelines I use are 1. Is it built by a big organization with intent to be exposed, and 2. What’s the risk if someone gets in.
All my stuff is in docker, so compartmentalized with little risk of breaking out of the container. Each is on it’s own docker network to the reverse proxy, so no cross-container communication unless part of the same stack.
So following my rules, I expose things like Nextcloud and Mediawiki, and I would never expose Paperless which has identity documents (access remotely via Tailscale). I have many low-risk services I expose on demand. E.g. when going away for a weekend, I might expose FreshRSS so I can access the feed, but I’d remove it once I got home.
Are specials requestable in jellyseerr?
Maybe they aren’t! Why doesn’t Overseerr support specials?
One warning: in my experience, you can not jump two major versions. Not just it won’t work, but that if you try it everything will break beyond repair and you’ll be restoring from a backup.
Two major versions can sometimes be a matter of a few months apart, so make sure you have a regular update schedule!
(Also, people say never update to a X.0 release, the first version of a major release often has major bugs).
TL;DR don’t take too long to update to new releases, and don’t update too quickly!
Also, the docker image is often a day or so behind the new release, soNextcloud tells you an update is available but often you then need to wait until the next day to get the updated docker image. I guess this is because (as I’ve just learnt) the image is built by Docker not Nextcloud.