writing.exchange is one of the many independent Mastodon servers you can use to participate in the fediverse.
A small, intentional community for poets, authors, and every kind of writer.

Administered by:

Server stats:

325
active users

For federated comments on @write_as, I'm gonna start with just exposing Remark.as comments to the fediverse. This should at least get the basic data there, though you still won't receive replies from Mastodon etc.

Then I'll work on receiving replies from the wider fediverse, and finally moderation tools. We'll see how it looks with replies showing up in the Remark.as UI, and then maybe move to showing comments on blog posts themselves.

Matt Baer

Maybe we can start collecting basic stats on likes and boosts from the fediverse before getting to full comment support. That'll at least be easier -- won't have to worry about abuse and spam.

Just not sure where to show those stats. Maybe just to the author on their posts, like we do with views.

Made a bunch of progress on this today — now we're accepting and tracking the number of likes you get from the on @write_as!

It's just not displayed anywhere. So that's the question — where do you want to see the number of likes you've received?

I know many people use / Write.as to *avoid* likes and normal social media stuff. So should we just display the number on your stats page? Only to you on the post (e.g. next to "views")? Only in social spaces like Read.Write.as?

@matt Will this also apply to WriteFreely? Please…?

@12pt9 Absolutely! I just generally develop this stuff on our Write.as instance first so we can gather feedback and quickly improve, then bring it over to .

@matt Only to the blog owner next to "views" would be good.

@matt @write_as I also think it's better on the Stats page, only to the Owner

@matt @write_as If I follow a blog via my Mastodon account, is each blog post going to appear in my Mastodon timeline like any other post?

If yes, and "likes" on a blog post are equivalent to "favourite" on a Mastodon post, and since favourites on a Mastodon post are public, I'd make the "likes" public too.

@matt @write_as What about only on the stats page by default, with an option to expose the data publicly authors can enable?

@matt @write_as would you consider import from Micro.blog?

@andreas @write_as Yeah absolutely! Just need to figure out what their exported data looks like

@matt @write_as Have seen other pieces of software with a "disable gamification features" option, or something similarly titled. Maybe you could include something like this from the outset for people who don't want to look at that kind of thing as writers?

My understanding is that usually this _hides_ the information instead of making it outright unavailable, but not certain on it.