Why does searching for lemmy content on mastodon.social, such as a search for [@lemmy](https://lemmy.ml/c/lemmy) or [@liaizon](https://social.wake.st/@liaizon)/110530316373516739, produce zero res
Why does searching for lemmy content on mastodon.social, such as a search for [@lemmy](https://lemmy.ml/c/lemmy) or [@liaizon](https://social.wake.st/@liaizon)/110530316373516739, produce zero res
Why does searching for lemmy content on mastodon.social, such as a search for [@lemmy](https://lemmy.ml/c/lemmy) or [@liaizon](https://social.wake.st/@liaizon)/110530316373516739, produce zero results? Some of the content is accessible through this instance, e.g. https://mastodon.social/@[email protected]/110530316373516739, it's just not findable with search, and some of it redirects when accessed in that way.
#mastodondotsocial #mastodon #lemmy #search #fediverse #interoperability @Mastodon
I’ve heard (but not confirmed) that some lemmy domains are having issues with firewalls blocking them, maybe as DDOS avoidance features, so your instance is unable to reach out and see if the user exists.
I’ve heard that from multiple people and forum posts at this point.
@sparr @lemmy @liaizon @Mastodon I think you need to do the full @[email protected]