I didn’t want to manipulate counts. If we had 500 instances registered, that would be problem.
Currently it doesn’t re-subscribe because it’s kind of edge case. It would also be fixed by increasing count to 2. I’m resetting the database every 1-2 months too.
This seems more like a Lemmy issue. However, to fix this issue, we can unsubscribe after 2 users follows instead of 1 🤔
I think open discovery algorithms are the way. We are against algos but sorting by like similarity would be beneficial.
What are you guys thinking? @dessalines@lemmy.ml @nutomic@lemmy.ml Are you optimistic about this or fuck any algorithms?
That is interesting. You haven’t blocked visibility of endorsements either. I’ll check it.
@Dave@lemmy.nz I hope this works for you :)
I reset statuses every few months for a re-check. Other than that, there’s no mechanism specifically for this case.
Interesting but potentially useful feature. I’ll have to think about where to squeeze it in :)
In order for an instance to follow a community in another instance, both must be registered in lemmy-federate.
If an instance has the “auto add” feature enabled, newly created communities will be added automatically within 1 to 5 minutes. This process is automatic. No action is required from an admin/moderator/user. You can see this from instances page.
If “auto add” is not enabled, any user can add that community manually. If not added, lemmy-federate will not work for that community.
Off topic, no need to apologize this much :)
I tried it and it works as of now. But it could be timeout, rate limit or something else. I’m thinking of showing the errors on the management page (or with Grafana). I created a task for this. Then you can see what kind of problem you’re having.
Lemmy Federate doesn’t do anything special. It searches and follows communities just like normal users do. The only difference is that it does this from every (registered) instance, for almost every community. The reason I didn’t explain it in more detail is that it has evolved into an admin tool rather than a user tool. Generally, admins know what this tool is for.
However, I can explain a few things that will be useful for you outside of the “All” tab:
Lemmy Federate enhances community discoverability by allowing users to search communities from their instance. Instead of relying on an external site, you can discover new communities while staying within the context of your own instance.
Let’s say that technology@lemmy.world is federated in your instance, but technology@lemmy.ml is not. In this case, you won’t see crossposts from technology@lemmy.ml sharing the same link as technology@lemmy.world.
When a community is pulled for the first time, only a certain number of recent posts are pulled with it. If you are the first to follow a community you are interested in from your instance, you will not be able to see all posts from that community.
I created this tool and have been using it in my instance since the very beginning. My instance is almost 2 years old and it’s total database size is 60.2GB.
The thing is:
Sure, it will make a small difference, but it’s nothing compared to the benefits it provides.
TBH Toastify is not that awesome.
Nope. lemy.lol. With only one l, peepo logo.
I’m glad you added lemmy.ml 🙏 Yes, you just need to create a bot account and add it. Communities are added/updated periodically.
If you say so. I’m a big fan of Cosmic because I’m hoping it will fill the modern, beautiful and also fast DE gap in Linux world. That’s why I may have sounded a little harsh (especially since it’s not even beta).
Communities on Lemmy Federate are updated every 24-48 hours. You can re-add existing communities to force immediate update. So it’s a valid action.
Frankly, I would prefer using Nautilus, VLC in a stable cosmic-comp. I believe the S76 team has strayed bit of the target by working on features that are not urgent (like Cosmic Edit, Cosmic MP). Still, it seems to be progressing pretty well.
I tried daily drive but could not continue due to some critical but minor issues. I will try it again when it is labeled as beta because I really like its speed and appearance.
I wanted to let my users encrypt their payload with my public key so only I can decrypt that payload. Just like how PGP works. Eventually I’ve used hybrid encryption with AES for encrypting the payload and RSA for encrypting AES secret key.
Just to let you know this post is almost 2 years old :)
It was something like Universal Lemmy Redirect
If you update your settings, all entries will be reset. Just click Save button in the management page.