Write.as @write_as@writing.exchange

Getting ready to announce full support for #WebMonetization 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 #fediverse.

We've reached a point where we'd like to start #hiring developers to work on the #WriteFreely roadmap 💻

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 #Go / #Golang developer and want to work on a growing #fediverse project, I'd love to hear from you!

#FOSS #job #jobs

#ActivityPub 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: https://Read.as, built from scratch to be #SelfHosted and #FOSS.

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

https://github.com/writeas/Read.as

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

(They also support #CamelCase!)

Now you can fetch individual blog posts from the #fediverse

#Question: if you have a custom domain on Write.as, what should your #fediverse 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?