Musing Studio Dev @dev@musing.studio

@julian yeah, just for Notes, not Articles. I'm wondering if I should just leave `name` empty for Notes to prevent that. Especially not sure how anything besides Mastodon handles it.

@thisismissem @smallcircles I'm not sure... This only applies to the `Note` type, not `Article`. On Mastodon, Article titles always show up fine.

But also don't think it looks too bad by manually adding the title to the body of the Note, like if you pull this post up in Masto: https://matt.writefreely.dev/note-title-fix-test

Just opened a PR for this: https://github.com/writefreely/writefreely/pull/1491

It ends up putting us in compliance with the ActivityStreams spec, too, by making sure no markup is included in the `name` property.

#WriteFreelyDev

Realized that the way we do notes on #WriteFreely doesn't work with #Mastodon, if you include a title. They don't show up!

So I'll see how it looks if we include it in the body of the Note.

#WriteFreelyDev #ActivityPub

Everything is pretty much ready to go, code-wise on #WriteFreely v0.16! Now just updating the docs and this should be out this week.

https://github.com/writefreely/writefreely/milestone/27?closed=1

The fediverse:creator tag doesn't work perfectly -- you'll need to use your fediverse @-handle in the Verification field to get it to show up right. But we'll fix that in the next version (https://todo.musing.studio/T932).

Moved two new additions into our upcoming #WriteFreely v0.16 release:

- fediverse:creator tag (https://github.com/writefreely/writefreely/pull/1253)
- Export email subscribers (https://github.com/writefreely/writefreely/pull/1258)

At long, long last, a bug with hashtags on @writefreely instances running MySQL 8+ is getting fixed in our next release, v0.16.

https://github.com/writefreely/writefreely/pull/1461

#WriteFreely #WriteFreelyDev

Making some small housekeeping updates to our #Writeas / #WriteFreely command-line client. I'd like to add a lot of basic missing functionality to it, so it's much more useful for everyone.

https://github.com/writeas/writeas-cli

Finally figured out what was going on with the heavy load on our Gitea instance, https://code.as -- a ton of spammers coming in, when I thought we'd closed registrations.

I've cleaned them up and put in some new protections, so should be able to keep the site up now for the repos we host there!

@ernmander ah nope, we have the ability to silence people's accounts when they're abusing the platform. Some people get caught up in that (you can see the questions on our forum https://discuss.write.as), and we just need a better way to handle that.

You would really think when you have 5 years to implement a feature, you'd squeeze it in there somewhere. But here we are!

Either way, implementing the 5-year renewal stuff now will also come with some new experiments I'm excited to try, as far as benefits for our most loyal writers.

A few priorities on the @write_as list, but this week it's two areas that I really need to address:

- Giving users who were silenced more insight into the reason, and a smoother way to appeal. This is taking up a ton of my time right now, especially as we're seeing more spammers complain, but I still need to sort them out.

- Letting 5-year subscribers renew their subscription. For many reasons, I'm way overdue on this 🙃

as always, deploying on Write.as and then opening PRs for @writefreely.

will probably get these changes in v0.16, our next release that's been delayed for a while

Working on some #fediverse things in @write_as today.

- New `preview` property on our Articles, so future supporting platforms can fall-back to a short-form representation of blog posts

- Interop issues with #Ghost