Write.as Development @writeas_dev@abunchtell.com

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

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

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

Good morning. Goals for today:

- Finish UI for enabling federation
- Experiment with rejecting replies
- Build onboarding flow for new users who want federation

Something I'm looking forward to: non-technical users seeing this new setting on their blog and asking me what it means. I have no doubt it'll be confusing to the uninitiated, so it'll be nice to hear everyone's questions, and figure out how to explain federation in a way that makes sense to them.

Based on that, I can tweak the UI so more people understand what's going on right away. Enough of that, and more people will be able to join the fediverse without the whole learning curve.

Actually it'll be something like this in the "Publicity" section for everyone, with a textbox that appears when "Custom domain" is selected.

Okay, custom domains are discoverable and have all endpoints in place. Now just need to let everyone choose their handle. This will go in a new "Federation" section on the blog settings page -- a page that's starting to get a little long I think, so I'll have to redesign it a bit in the near future.

One thing I want to do is make sure replies from the #fediverse are gracefully handled / rejected, since they don't go anywhere when replying to blog posts right now. Not sure how to do that, but I'll try a few things before the full roll-out.

Now I'm working on making blogs on custom domains discoverable in the fediverse , then adding a setting for all users to enable #federation.

Turns out boosting does work, just not on #writingexchange for certain accounts of mine I was testing with and broke on that instance (like @matt@write.as).

Only major bug I've found was with following multiple Write.as blogs -- the second or greater blog you followed didn't save in our database correctly.

That's fixed now, and I've reconstructed the missed follows via the server logs, so you should still be subscribed. Still, please double-check the blogs you're following, and if you see an hourglass icon where the follow button normally is, do the ol' unfollow/follow-again to get things right.

Now you can see how many #ActivityPub followers your blog has on your Stats page (though we don't divulge who individuals are -- again, goal is #privacy for readers, too)

Noticing some failed follow attempts from... Hubzilla? I believe. Going to see what I can do about supporting these other platforms next.