So we won’t be able to save posts? Or just the button will be hidden, but still menu-accesible?

This process needs to be easier, somehow. New users are going to search, see it doesn’t show up, assume everything is broken, and leave.

I think the proper behavior would be that two instances are federated, a user would be able to see all communities in both.

It’s going to be especially hard for users on a small instance to find content if they, or some other person on that instance, has to search for it first.

If I type “!coffeeaddicts” into the search bar, it should show all communities in all instances that are federated with my own that match that query. A person running their own instance would have to search every single community and wait however long for it to populate.

Thank you all for the responses!

It looks like an inexpensive VPS can do the job here, especially if it is just going to be an account server, with no communities.

I haven’t gone through any documentation yet, as I needed this info first.

Are there options for turning off certain things like IP logs, etc, to make it more private (for the users) to keep their info away from admin eyes? Or is all of that necessary for function?

If only we knew someone who knew how to bend things…

Looks like we’ll all be going this for a while until new community creation slows down

Well that’s the worst story so far. Completely unacceptable in every way.

I believe there’s a Github PR addressing this, they are adding many other instances that have more than 100 daily active users, so, next update possibly?

Have the search open a page with a search bar, underneath have three tabs across.

Local, Subscribed, World/Fediverse/Etc