The Admin ☁️ @TheAdmin@mastodon.cloud

Hello fediverse!

We're now running Mastodon v2.5.0rc1 😏
https://github.com/tootsuite/mastodon/releases/tag/v2.5.0rc1

https://status.mastodon.cloud

👀

Done 🚀

There will be downtime once for deploy the update.

WORLDWIDE

🙄

IPv6 😏

To view the federated timeline, click the "Federated Timeline" icon in your Compose column or the respective button on the Getting Started panel. To hide the federated timeline again, simply click the "Back" link at the top of the column while you're viewing it.

Following users on remote instances who you meet on the Federated Timeline can lead to meeting more users on more instances and further connecting your instance to more and more of the entire Mastodon and OStatus network.

The Federated Timeline shows all public posts from all users "known" to your instance. This means the user is either on the same instance as you, or somebody on your instance follows that user. The Federated Timeline is a great way to engage in the broad chatter of the world.

The Local Timeline only shows public posts made by users on your home instance. This can be useful if your instance has particular community norms that users on other instances may not have, such as particular topics that get put under content warnings; or particular in-jokes and shared interests.
To view the Local Timeline, click the "Local Timeline" in the Compose column or the respective button on the Getting Started panel.

In addition to your Home timeline, there are two public timelines available. The Federated Timeline and the Local Timeline. These are both a good way to meet new people to follow or interact with.

There are different ways in which something can be decentralized; in this case, Mastodon is the "federated" kind. Think e-mail, not BitTorrent. There are different servers (instances), users have an account on one of them, but can interact and follow each other regardless of where their account is.

You can use Mastodon with any of these apps!
https://joinmastodon.org/apps

Solved the issue that some clients couldn't login to mastodon.cloud.

Done!