Write.as Development @writeas_dev@abunchtell.com

@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

@Blort Absolutely, that mentality really holds a lot of projects back and keeps people away. Getting more people on board with FOSS, decentralization, etc. means being accessible to everyone, regardless of skill level. This is all stuff I'm very passionate about :)

@Satsuma @jalcine @write_as Indeed, especially just for understanding different capabilities of different platforms. But maybe with us introducing "no replies" some kind of standard for handling it will evolve.

Good morning. Goals for today:

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

@tomskee The feature isn't completely finished yet, but right now Write.as blog posts can be federated, that is, followed from federated platforms like Mastodon. For example, here's mine: @matt@write.as -- you can follow it here, get my posts, and favorite / boost them on your Masto account.

So the stats you're seeing on Write.as are how many blog followers you have in the "fediverse" / on Mastodon and similar platforms.

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.

@jalcine Thanks! Actually for this I'm trying to figure out how to reject ActivityPub replies, or notify platforms like Mastodon that a reply wasn't received by a user, as we don't support comments / mentions on @write_as right now (by design)

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.