Musing Studio Dev
@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/ ]
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/ ]
@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.
September 6, 2025 at 2:38 AM
@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 […]
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 […]
Original post on social.musing.studio
social.musing.studio
September 5, 2025 at 11:12 PM
@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 […]
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
It ends up putting us in compliance with the ActivityStreams spec, too, by making sure no markup is included in the `name` property.
#writefreelydev
Title fixes for ActivityPub by thebaer · Pull Request #1491 · writefreely/writefreely
This fixes some issues minor issues with titles on posts sent to the fediverse. It solves for the following use cases: Posts with a link (or any Markdown) in the title A short note published with ...
github.com
September 5, 2025 at 9:23 PM
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
It ends up putting us in compliance with the ActivityStreams spec, too, by making sure no markup is included in the `name` property.
#writefreelydev
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
https://github.com/writefreely/writefreely/milestone/27?closed=1
writefreely/writefreely
A clean, Markdown-based publishing platform made for writers. Write together and build a community. - writefreely/writefreely
github.com
August 25, 2025 at 8:39 PM
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
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).
⚓ T932 Always fetch fedi handle for verifying profile
todo.musing.studio
August 25, 2025 at 8:28 PM
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).
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.
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.
June 4, 2025 at 6:56 PM
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.
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.
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
https://discuss.write.as/t/temporary-email-issues/16632/4
Temporary email issues
Thank you, this is really helpful to know! I’m going to revert that latest change, so that should at least fix the issue going forward. Otherwise, I’m working on a new feature that’ll show you which posts never got sent as emails, and then let you manually send them again – so that should help make sure people still get those posts. Going to get that done tonight if possible, stay tuned!
discuss.write.as
February 19, 2025 at 12:13 AM
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
https://discuss.write.as/t/temporary-email-issues/16632/4
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
#WriteFreely #writefreelydev
January 24, 2025 at 8:56 PM
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
#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.
October 24, 2024 at 8:44 PM
it might be too much to knock out in a week. there are issues like user quotas, server config for uploading bigger files, etc.