I think you might be interested in this @Elevator7009sAlt@ani.social as we discussed before :)

Absolutely. Sometimes I can be hard to understand (since English is not my native language), thanks for the clarity :)

Interesting. I didn’t realize my instance wasn’t federated with Piefed. I’ll contact the Piefed admins about this.

However, this issue is probably not related to Lemmy Federate because Piefed.social doesn’t even use it.

IIRC Lemmy and Mastodon PMs are different and incompatible. If you can receive PMs from Lemmy users then you should be able to receive auth codes. Currently @rikudou@lemmings.world is adding both Lemmy and Mastodon PMs here: https://github.com/ismailkarsli/lemmy-federate/pull/33

Also software other than Lemmy and Mbin needs to add ‘roleName: Administrator’ to their user webfinger requests. This is because ActivityPub doesn’t have a standard way to expose user roles.

I’m thinking of adding another ways of verifying like DNS based verification but still not sure. Any recommendations are welcome :)

Of course using the tool :)

Yes, it is just disabled. Lemmy Federate supports every threadiverse software and Piefed is one of them.

Currently Piefed communities can be followed by Lemmy instances but not the other way around.

In general, every fediverse software that support FEP-1b12 and can receive Lemmy-like PM’s can register to Lemmy Federate.

/cc @OpenStars@discuss.online @rimu@piefed.social @julian@community.nodebb.org

My instance has 82GB of DB size. It is almost two years old. I think you’re overestimating.

If you update your settings, all entries will be reset. Just click Save button in the management page.

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 :)

1. In order for an instance to follow a community in another instance, both must be registered in lemmy-federate.

2. 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.

3. 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:

Discoverability

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.

Crossposts

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.

Initial post count

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:

• If a community is generating enough activity, it’s likely that someone from your instance is already following that community.
• If a community isn’t generating enough activity, it won’t create much of a network/storage burden anyway.

Sure, it will make a small difference, but it’s nothing compared to the benefits it provides.

TBH Toastify is not that awesome.