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!
https://writefreely.org/pull/1609
#WriteFreelyDev
@dev.social.musing.studio.ap.brid.gy
Dev notes from @musing, tooted away by @matt. Follow @write_as, @writefreely, @snap_as, @remark_as, and the rest for official announcements. #writeas […] [bridged from https://social.musing.studio/@dev on the fediverse by https://fed.brid.gy/ ]
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!
https://writefreely.org/pull/1609
#WriteFreelyDev
Okay #WriteFreely v0.17 coming before the end of the month, if all goes well 🤞
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 […]
@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 […]
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!
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 […]
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
Fixed a big bug in our (experimental) command-line #WordPress import tool, if you're using it.
https://github.com/writeas/wp-import
#WriteFreely
Going to revert the recent change that broke things, and add a new way to re-send any emails that might've failed to send while this bug existed.
https://discuss.write.as/t/temporary-email-issues/16632/4
In #WriteFreely news, I just have to wrap up SMTP support (https://writefreely.org/pull/1131) and then I think we can get v0.16 out finally.
Still had features like "require email on signup" on the roadmap for this version, but going to push that to the next release.
#WriteFreelyDev
Some weird things going on with email right now on @write_as... sometimes emails are sending while it's disabled on a blog; other times, we're not sending at all, after the other day when I put in some failsafes for the initial issue.
Probably going to add some better logging that everyone can […]
Adding the `fediverse:creator` tag on @writefreely posts: https://github.com/writefreely/writefreely/pull/1253
#WriteFreely #WriteFreelyDev
Along those lines, we could really use help reviewing these pull requests from anyone with Docker experience! https://github.com/writefreely/writefreely/pulls?q=is%3Apr+is%3Aopen+label%3Adocker
#WriteFreely #WriteFreelyDev
Finally able to get back on #WriteFreely development again. I'm working through some pull requests for our upcoming v0.16 release. Hoping to have this out by the end of the month!
If you're able to, would appreciate any help building and testing out everything on the `develop` branch! […]
If you had trouble building our command-line tool for migrating between @writefreely instances, we've just fixed that!
https://github.com/writefreely/wf-migrate
#WriteFreely #WriteFreelyDev
Was really planning on releasing @writefreely v0.16 in November, but had some life things get in the way.
Working on getting a few more features in now so I can put that out this month.
#WriteFreely #WriteFreelyDev
it might be too much to knock out in a week. there are issues like user quotas, server config for uploading bigger files, etc.
let's see if we can get image uploads in @writefreely v0.16 😬
if anything, could get some basics in -- custom avatars and uploading via the classic browser. but not sure how the management UI is going to work out
Another update in upcoming @writefreely v0.16: Archive pages! This makes it easy to see a full list of all posts you've ever made on your blog, sorted by year.
If you're able to, please help test and review this change: https://github.com/writefreely/writefreely/pull/1128
#WriteFreely […]
okay, on to more #WriteFreely code review
Just merged an important fix for official @writefreely binaries. They should work again on all platforms with our next release, v0.16!
https://github.com/writefreely/writefreely/issues/1064
#WriteFreely #WriteFreelyDev