Write.as Development @writeas_dev@abunchtell.com

Last night got the database schema worked out to handle everything that'll be in the MVP and versions after. Today have been adding the API layer and bringing over code I needed from Write.as.

It's been a long day, but I have enough energy for more coding if it's for pure fun -- a new project, a blank canvas. Let's see how far I can get on this tonight.

We're now sending out Update activities, but it seems Mastodon doesn't do anything with them, so titles and URLs won't update. Still, it'll work on any future platforms that do something with the event.

Blogs are now discoverable on #Pleroma, but following doesn't seem to work -- no request is made to Write.as -- and the URL to the blog isn't correct. Will keep picking away at it.

Now finishing testing on new Update activities being sent out. In the course of doing this I also figured out how to make scheduled posts work with federation, so that should be a really nice feature when it's ready.

Patched the go-webfinger library (https://github.com/writeas/go-webfinger) so it supports requests without the acct: scheme and that seems to make blogs discoverable on #Pleroma. Still needs more testing.

Going to make individual posts findable in the #fediverse via search

@ernie @cesaraovivo Agreed, there's a ton of different uses / specializations to fill still -- this is just one part

@0x1C3B00DA @write_as 👍 will do!

@konc It comes from the blog title (the big text box at the top of the blog setting page), but it is odd that it seems to be getting truncated in that toot. Might be an issue with the bot that posts them, because all it does is pull from the Read.Write.as RSS feed and that seems to have the correct title

@0x1C3B00DA @write_as @jalcine @Satsuma Great point, it does seem like the perfect place for it. I'll start thinking of what that should look like that'll be useful to others, too

@readwriteas @konc yep, was thinking the same thing. Hoping to do that soon.

@konc Right, but once you follow the blog from any given instance it'll show up on the federated timeline for everyone, since it knows about it after that.

@konc No worries, you'll find them by searching for them from Mastodon, e.g. just type in @blog@yourdomain.com

By default your name will look like that, but if you go to your blog settings it'll show you what your handle is and let you change it to whatever you'd like.

Now that #federation is live, time to get things working with other platforms. Next up: #Pleroma

@tomskee Yep! Exactly. So now people can find that handle in the fediverse

Okay, latest changes deployed. Included:

- Support for federation on custom domains
- Fixed avatars (some were off-center before)
- Users on custom domains are now excluded from NodeInfo stats on Write.as
- "Published" times on Create activities in the API

Doubt it'll be an issue, but have a bit more work to do to prevent overlap between blogs on Write.as and on custom domains (especially around account discovery) before I can deploy these changes. Will finish up tomorrow.

Now just double-checking all endpoints and #ActivityStreams data -- have to verify sites on write.as/*/, *.writeas.com, and custom domains.

✅ Blogs on custom domains are discoverable
✅ You can choose your handle for your custom domain blog (default: @blog@example.com)
✅ Custom domain blogs have NodeInfo showing them each as a single-user "instance"
✅ AP endpoints should be future-proof for when you can eventually self-host your blog
✅ Posts federate from blogs on custom domains