Day 18 of the #100DaysTo Offload Series:
One of the features that I most liked about write.as was the simplicity of the platform. I could have self hosted with WriteFreely, but I elected instead to pay for a “Pro” account so I could leave all the technical hand waving to the people who know the platform the best.
The next thing that drew me to write.as was it's integrated federating using ActivityPub. _In theory a Pro account allows for following the blog on any ActivityPub platform, like Mastodon. Considering I spend pretty much 100% of my social network time on Mastodon, that was a “killer feature” for me.
I configured the @email@example.com account to be my blog and away I went.
That worked great! Up until April 29th. I posted my Two Space Or Not Two Space article and it worked fine, but on April 30th (or more fairly the wee hours of May 1st), when I published my National Poetry Month article, it didn't federate.
I know my poetry is bad, but I didn't think I would break the whole system.
A few details here.
- The posts are being published on my blog.
- The generic write.as account @firstname.lastname@example.org appears to be working.
- There are people that seem to see it at @email@example.com.
This is were you guys come in. For anybody that reads this and has managed to get this far into my word salad, if you're seeing this on @firstname.lastname@example.org, please reply to that post and copy my @email@example.com account. If you look at @firstname.lastname@example.org and the posts unceremoniously end on the 29th of April (or some other date), please message me at my @email@example.com account and let me know.
I'd love to get a nice cross section of people from various instances. I'd love it if you'd boost the post if you're on another instance so more people can see it, but that seems oddly self serving beyond this one issue.
Thank you all for your help, and hopefully we can get this resolved here soon.