| Left | Right |
| Left | Right |
| Left |
| Left | Right |
| Left | Right |
| Left |
#ActivityPub support is now available to everyone! ๐ ๐ 
Write.as blogs don't federate by default, so to enable it you can either sign up with our new page: https://write.as/new/blog/federated, or if you're already on Write.as, go to your blog's Customize page and click "Enable federation"
Note this also includes support for custom domains. So if your domain is hosted with us, you can now choose your handle when you enable federation and your blog will be accessible in the fediverse!
You can now challenge someone to game of #chess over toots! https://castling.club/ ๐ช
It's actually a standalone server in the #fediverse, implementing #activitypub all by itself. ๐
#ActivityPub implementation really is bare-bones, but more right now is unnecessary. There are many unanswered questions, especially around privacy.
For example, what happens when a user changes their blog from Public to Private or Password-protected? The existence of an account in the fediverse gives away information we don't otherwise divulge on Write.as.
What auth platform should we implement on an #activitypub app? I see most places are using email sign up, but that means the user has to maintain a separate password and account per site.
Is there an OpenID implementation or other federated solution we should use for this? If not, can we agree on a standard one that most fediverse apps support to make onboarding users easier? We probably have enough scale with the fediverse to get traction.