you mean because the 3rd party apps don't support it yet?
Die4Ever
my bug report was closed but I'm still seeing the issue on voyager.lemmy.ml even after it was updated to rc.5
https://github.com/LemmyNet/lemmy-ui/issues/2215#event-10991644637
maybe someone else here can confirm my findings?
The first is that listed subscriber numbers are for your server only
For your first issue, subscriber counts will be fixed in Lemmy v0.19.0
https://github.com/LemmyNet/lemmy/issues/1440
Preview here: https://voyager.lemmy.ml/communities?listingType=All&sort=TopMonth&page=1
The second is that there are many redundant communities, which makes it difficult for onboarding new users. There should be some way to group like-communities into super-groups based on topics
Yeah this one has an issue open, you could join the discussion if you have any ideas, this is a big one
Well now you can use :0.19.0-rc.5
:)
it's in alpha currently, but you could still run it
I think you might have to use the :dev
tag to get this update, a bit risky to stay on that tag though, maybe wait for the next docker image of an alpha release
in v0.19.0 Lemmy will automatically delete entries over 7 days old
https://github.com/LemmyNet/lemmy/issues/4113
https://github.com/LemmyNet/lemmy/commit/cb01427dcff14b3d88e30220695fc97978786a9a
currently it waits 3 months before deleting
I think it's part of this https://github.com/LemmyNet/lemmy/issues/187
Also local only communities, since this isn't really possible with remote communities anyways https://github.com/LemmyNet/lemmy/issues/1576
yes you're right, also that config flag was renamed to cache_external_link_previews
in v0.19.0 you could try disabling pictrs caching https://github.com/LemmyNet/lemmy/commit/1d23df37d86cc5cb6d7d9efaaf4360ecc9a9796f
cache_external_link_previews: false
I don't think that will clear the existing cache though
Yep haha, it was just running when I made my comment. It's the alpha testing server so it does go down sometimes.
Clickbait title, it uses more than 8 cores just fine (obviously), but the scaling factor for how often threads should get scheduled wasn't going above 8 cores. So basically it was just running a bit suboptimally for extremely heavy multitasking, will be interesting if anyone manages to get a decent measurement on how much the fix helps.
oh btw 3rd party apps aren't working with 0.19.0 yet, because of changes to the authentication API