Show newer

Oof our slug-generation library used in @writefreely is way out of date. Will switch to upstream, since our one change was merged, anyway.

github.com/writefreely/writefr

Really want to finish up fediverse replies on @remark_as / @write_as, so we can push that out and announce that we're finally fully integrated with the . Will see how far I get today.

I'm looking at that again today, and seeing if there's any way we can adapt it to Read Write.as and multi-user instances.

Show thread

I'd really love to have an actor for read.write.as that natively sends out posts from all the writers there.

We actually started working on this in 2019 (w/ @qwazix) with our project: github.com/musingstudio/pherep

Bridging this account to now, if you're over there: @dev.social.musing.studio.ap.brid.gy

This has been one interesting use case that I haven't really seen anywhere else in the . Basically, it'll let you reply to a short-form post (e.g. Mastodon) or long-form post (e.g. ) with your own full blog post.

That post could either exist on its own out in the fediverse, or become a published post on your @write_as blog, while also being part of the conversation in the fediverse.

Show thread

Still dealing with some old fraudulent accounts created on Write.as last month, so today I’m developing some tools to more quickly manage those users. Hopefully I can get back to the real work soon 😅

Our next release (v0.15.1) will fix support for following WriteFreely blogs from @gotosocial! There was a bug before that prevented this. github.com/writefreely/writefr

We're hoping to have that out to everyone next week!

#WriteFreely #GoToSocial #WriteFreelyDev

Cleaning up more PRs and issues, starting with dependencies.

Some I'm merging into `develop` for a future release, and more urgent ones are going into our v0.15.1 branch so we can release that soon.

...and many more places that needed updating. Closed this issue (github.com/writefreely/writefr) and updated the CLA to reflect our current legal name.

Show thread

Plenty of mixed naming happened because many product ideas and initiatives happened before going open source (@writefreely) and formally rebranding as Musing Studio (@musing).

Now everything is much bigger than Write.as, so I want our infrastructure / online presence to reflect that.

Show thread

I'd messed up our Phabricator install a while back, so I had to get that up and running again.

Just started from a new dedicated server, and put it on our Musing Studio domain, to again bring everything under one roof. It's now at todo.musing.studio

Show thread

Lot of moving things around the past week or so.

Moved most of the accounts on our old "A Bunch Tell" instance over here, to our Musing Studio instance.

Can't bring our many years of posts unfortunately, but at least brought our followers.

Musing Studio

A social space for Musing Studio projects.