mastodon.social and mastodon.online are the first instances with a global search, BUT this setting is opt-in and you must activate it so that your posts are included:
👉 https://mastodon.social/settings/privacy
👉 https://mastodon.online/settings/privacy
Mastodon

A newer server operated by the Mastodon gGmbH non-profit

Mastodon hosted on mastodon.online
@Tibor I am running beta 2, and the global search isn’t available. Is that something coming on beta 3? I see those two instances are on nightly.

@david @Tibor Yeah it's coming in beta 3 and isn't in beta 2. Servers that have it right now are running nightly or backported the relevant commits.

(Also, for the record, I don't think mastodon.social and .online were actually the first instances ;).

@Tibor Claiming first is a bit weird. I've had #search since I installed 9 months ago, and that was late to the fediverse...
@petererer @Tibor full text search, not search in general.

@Tibor

Opted in!

I don't expect to be searched much, but turned it on to show support. Thanks for the notification.

@Tibor @chockenberry

Here’s my question: Is there a way as a #MastoAdmin on 4.2 to allow “normal” search (search limited to posts you’ve favorited etc) but disallow “full search” (searching all posts for any term)?

I know *users* have to enable full search for themselves, but is there a way for a Mastodon admin to disallow this *even if* one of their users has opted in?

@jsit @Tibor @chockenberry Why would you want to do that? Overriding consent is against the consent-driven design of Mastodon and this feature.

You can stop your users from searching by not setting up ElasticSearch. There's no way to opt someone out who has opted in to other instances searching though. You'd have to hack out that feature and roll your own Mastodon.

@blake Many admins are *fiercely* opposed to this feature and would rush at the chance to turn it off against their users’s wishes (or their users's inadvertent checking of the box) if they could.

"If you don't like it, join another instance.”

@jsit That doesn't sound like a good reason -- hell, any reason at all -- to override someone's consent.

If you don't like it, don't update.
@blake I'm inclined to agree with you, but I think there are many admins who would feel otherwise.
@Tibor
How is it global, making the server search through posts it didn't see before 4.2?