It’s indeed not possible to sign into Mastodon as your Write.as account. And Write.as doesn’t provide profile management features beyond editing the blog description and setting the profile image via the favicon.
1 Like
Nope. They are completely separate accounts on separate servers.
so… if someone replies to my blog’s toot, where do the replies go? Can anybody read them?
The answer may well be in @matt 's posts above. But they’re a bit opaque to me. I’ll look at them again .
If someone replies to your blog’s toot the reply shows up only in the commenter’s Mastodon account and nowhere else.
ok, beginning to understand
Seems like this is close to release? 
It would make sense (to me) to run fediverse toot replies, to a blog’s fediverse toots, in the fediverse (ie Mastodon). But if, instead, fediverse replies are channeled into write.as space (as with a normal, non-federating blog) that’s rational, and workable.
@matt How will your average fedizen, replying to a write.as toot, know that the conversation has branched into another space?
The same way you know it’s federated with any ActivityPub server I expect: most folks don’t.
Some software (I know Akkoma does) shows the platform icon next to the username of a post, so that would make it clear that it’s not mastodon. I say Mastodon, because most folks using alternate platforms are a bit more aware of the various options.
Oh wait, mastodon just displays a post link anyway instead of the post content. So I guess that would be clear enough 
I personally like having replies/comments below a blog post - with me as the blog creator able to approve or remove posts as required. Threads of comments would be welcome, to me.
I don’t think this is working for me as expected. Here’s how the process is going:
- enable federation in settings for blog (Log in — Write.as)
- find on Mastodon by searching @shavian-text@write.as → profile appears empty, but this is expected due to long-standing issue with Mastodon itself. # of posts corresponds correctly with write.as blog
- follow @shavian-text@write.as on Mastodon, from my account @zoy@merveilles.town
- publish a new blog post → # of posts field on @shavian-text@write.as profile increases by 1, but new post is still not showing either on profile or in timeline, even when logged in as @zoy@merveilles.town
- find post on Mastodon by searching its URL (𐑓𐑮𐑪𐑥 𐑞 𐑢𐑷 𐑓 𐑞 𐑢𐑻𐑤𐑛𐑟, ·𐑣 𐑡 𐑢𐑧𐑤𐑟, 1898 — 𐑖𐑱𐑝𐑾𐑯 𐑑𐑧𐑒𐑕𐑑 (Shavian text)) → no search results in Tusky or Moshidon
What am I missing? As I understand it, step 5) here should always yield a search result on Mastodon, as long as federation was enabled before publishing the post.
Free account user here. I enabled federation, but trying to use it from, say, mastodon.social is throwing a 404:
https://mastodon.social/@trigonella@write.as
Update: issue resolved in matt’s comment below. Thanks!
1 Like
How are you publishing your posts, @zoyander? E.g. through the editor, or by importing posts? There is a known issue where imported posts won’t go out to the fediverse right now.
I believe you have to search for accounts to have them pulled into Mastodon initially (this is just the way it works on their end). I searched for your blog on mastodon.social (using its Write.as URL) and now that link seems to work!
1 Like
I’m publishing through the editor (honestly not automatically publishing imports seems intuitive to me, to avoid bulk posts on Mastodon)
Just published another post yesterday, through the editor - the posts # on the mastodon account is still 2, and still no posts are displayed.
Hmm, are you able to find other accounts like @blog@write.as? Otherwise, are you able to see the blocklist on merveilles.town (or ask your admin), and confirm that they don’t defederate from write.as? I’m able to see your post fine on our writing.exchange instance, so I’m wondering if something’s going on with the particular Mastodon instance you’re on.
I’ve tried from my Merveilles.town account and my assemblag.es account, and neither can see any posts on my write.as profile but they can see posts on other write.as profiles (even those that I don’t follow). Both have eventually updated the # of posts to the current correct number, but no posts are shown before or after following.
Did you try looking up your Write.as blog from these instances while still changing settings on the blog, e.g. URL, username, etc.? Also, are you able to find and follow the blog when you search for the blog URL instead of the fediverse handle?
I just noticed that markdown headings formatted like so:
### this is a heading
get converted correctly to html, but also the first word in the heading shows up in mastodon as a tag like so:
#this
even though there was a space between # and t in the markdown. Is this intended? It feels a bit weird if so.
Hi there! I’m Somnius, the admin of merveilles.town, where both Zoyander and another user I’ll mention are located.
I was troubleshooting with another user, Gendor, who has their write.as account at @gendor@gerritniezen.com, and he is experiencing similar issues—13 posts of his are not properly federated to our instance.
When I attempted to follow his local account on merveilles.town, I looked through the logs and found that actually caused a 500 error on write.as’s end. This happened at 1:05pm pacific time and was retried a few times, all causing failures. This is odd, since on other instances (e.g. mastodon.org) they have no issues seeing Gendor’s latest few posts. I’m wondering if something particular about our instance is causing issues with write.as.
It’s worth noting that we are using a Mastodon fork named Hometown, but there are very few changes made on there compared to upstream Mastodon. I’d love to know if this issue is on our end or not, and let me know if you have any questions!
Hmm, if it’s not working on your instance but posts are showing up fine on other instances, it’s possible something got messed up along the way. Are you able to pull up individual posts on your instance by searching the URL? Otherwise, are you able to refresh the Write.as profile from the admin interface on your instance, and see if that fixes things?
No unfortunately both refreshing the profile and searching for either individual posts or the profile doesn’t work, and delivery from that domain has been failing for the past 4 days. I don’t see anything in our logs that point to an obvious error on our end, just that we get a 500 response from write.as.