Adda

Btw., the community tag you posted has a typo (neehaw should be beehaw). Is that a typo here, or did you mistype it in the search field as well?

But, try to search in the webapp / browser with the full HTTPS link. That should work. But using !programming@beehaw.org works in my browser without a problem.

There are bugs in Jerboa and federated community searches seem to be one of them.

You can see this short part of Lemmy documentation for how the integration with other instances works.

If by main network you mean the largest federated network (the largest number of federated instances together), then it is precisely that.

It is then up to each user to decide where to create an account. On any single instance? On multiple instances where some might be federated with only a small subset of instances and others might be more general instances federated with multitude of instances, for example on the largest federated network? It depends on what the user comes here looking for. Whatever works for them is great.

Sure, they would. But for that, you would need to implement them first, and implement them right, which is a highly challenging endeavour. I could imagine that this is on a backlog for Lemmy development, but it will take a while before any usable implementation is applicable.

Ah, wait, you get the deleted error message from your instance as well? Then it seems as a bug to me. That would be worth reporting.

I have no idea how can this exact picture happen. Unless you block the IP for lemmy.ml entirely, I do not understand what is happening here. It could be that deleting your account somehow poisoned your browser cache and now everything on lemmy.ml fails to load because of that. You can try to clear it. Otherwise, I am clueless. Sorry :) You can try to create an issue to ask for instruction from more knowledgeable people, if you wish.

Just to explain, each instance can make their own decisions, but then they risk being defederated by other instances for their decisions. On their own instance, they can still function however they want, though.

As I replied to another thread, that would be possible. You can try to create and issue for it.

You are completely right. Disabling the approval feature equals unmoderatable instance (when the bots come), because a human (a moderator) simply cannot compete with a Python script posting spam every few milliseconds. Such instances are therefore instantly defederated by others in order to protect themselves.

That is possible, implementable a clear in its functionality. You can try to open an issue im the websites GitHub repository and see what the developers and others think. Alternatively, you can try to implement this functionality yourself and create a PR for it.

It was. Again, you could do with the slur filter whatever you wanted as an instance admin. And admins of other instances can defederate with your instance for your decision, too.

If someone implements it on the per-instance basis, it works and is not resource heavy, great. But it will be a while, before someone actually gets there.

No worries :)

It is not invite-only. Most instances are approval-only. As I said earlier, as of now, it is a necessary evil.

I disagree. That would not solve the issue with spam bots. Furthermore, the word centralization is forbidden in conjunction with Lemmy in a single sentence :) You cannot create a decentralized self-hosted federated platform and have a centralized account approval server. That goes againts everything decentralization stands for.

This manual approval of new accounts was implemented to battle spam and floods of newly created bot accounts. Sadly, it is a necessary evil as people do not seem to be able to behave themselves (and create bot account to spam), as is always the case.

AFAIK, seeing what you have shown that you have tried, the cause might be that your instance lemmy.one does not know that something as a !tf2@lemmy.ml exists. That is because nobody from your instance have ever subscribed to that community, so your instance does not download content from this community to your instance. You would have to be the first one to subscribe to that community in order to start federating that community content to your instance.

If pasting https://lemmy.ml/c/tf2 in Jerboa community search produces any results, you would have to go through the web interface first. Subscribe there, and only then you will be able to see its content in Jerboa (on your instance).

This is a mechanism for preventing downloading unnecessary quantities of content from communities nobody on a new instance is interested in and wasting bandwidth and storage space. If someone wants to start federating with a new community, they need to explicitly request to start federating it as describe above.

AFAIK, it is more of a bug than server load issue. This have been going on for a while in Jerboa. Will be hopefully fixed when someone has the time to find the cause of the issue.

That would be greatly appreciated by many, I am sure. Good luck :)

deleted by creator