Currently, it involves writing updates as markdown files, then passing the file to a local script that does some conversion and posts it on Mastodon. Non-replies are then crossposted to Twitter from there.
Ideally, this would have a posting interface that pushes markdown files to a git repository, which has hooks to convert and syndicate each update to the correct location, depending on its contents and what it replies to, for example.
@jkreeftmeijer You could instead host your own Mastodon instance ...
@mvz I might publish from there through ActivityPub eventually.
I didn‘t start my own instance because I didn’t want to have to keep it running. Right now, all updates are in a git repository, and that page is statically generated. Also, I’d like to post updates that only get syndicated to a single place, and not necessary to Mastodon (like Reddit, for example).
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!