Dev notes from @musing, tooted away by @matt.
Follow @write_as, @writefreely, @snap_as, @remark_as, and the rest for official announcements.
#writeas #writefreely #fediverse #development
Since our Markdown preview has been working well on @write_as, we'll also be bringing it to @writefreely in v0.17!
Finally fixed the issue when switching between the Plain and Rich Text editor and your posts contain HTML. Now it won't break! (Coming to @write_as shortly)
Just a small improvement coming to #WriteFreely v0.17: now you can change the font of posts after they're published from the web UI!
This week I’m focusing on some small long-standing, quality-of-life issues that...
This week I’m focusing on some small long-standing, quality-of-life issues that have plagued Write.as / WriteFreely for years. Today, it was adding a Markdown preview to the Plain Text editor (issue T519), which was brought up again on the forum after the feature stalled for years. [...]
Back on WriteFreely development to prepare for our v0.17 release, planned for November.
Some small fixes opened / merged today:
* ActivityPub title fixes (https://writefreely.org/pull/1491)
* Fix upgrade issues with instances using Unix sockets (https://writefreely.org/pull/1503)
* Fix Customize page header nav on single-user instances (https://writefreely.org/pull/1505)
@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.
Micro Matt
