For a while, users weren't able to follow Write.as / WriteFreely blogs from Mastodon if their instance's "Authorized Fetch" feature was enabled.

We just fixed that on Write.as, so now you shouldn't have any trouble following blogs! We could also use your help reviewing and verifying this fix in : writefreely.org/pull/439

Getting ready to announce full support for on Write.as today!

I should also have a post on @matt around how we implemented it, and thoughts on distributing via different channels like the .

We've reached a point where we'd like to start developers to work on the roadmap 💻 :writefreely2:

This would be remote, contract-based work for now, with a chance to go full-time later in the year (assuming all continues going well). You'd be creating free / open source software.

I'll have more details soon, but especially if you're a / developer and want to work on a growing project, I'd love to hear from you!

support on Write.as was just the first part of what I wanted to create for the :fediverse: Next, I wanted a place to read everything in peace.

Here's just the start of that second part: Read.as, built from scratch to be and .

Soon you'll be able to create an account on the Read.as instance, and follow platforms like and that federate long-form articles — for now it just needs to be run locally.

github.com/writeas/Read.as

Now posts sent to the include any you've added, so they'll show up in searches 🔎

(They also support !)

: if you have a custom domain on Write.as, what should your handle be?

Examples:
@blog@example.com
@me@example.com
@example_com@example.com

others? Do you want to be able to choose it yourself, instead of having a default?

Writing Exchange

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!