My masto instance had missing migrations, maybe why it wasn't working well, and why my timeline is so misordered in #fedilab
Note to self, set up https://github.com/emersion/emuarius with twitter.com as the domain for extreme hackiness
( or experiment with https://github.com/dtschust/fake-mastodon-instance )
Before you get too excited, the implementation is still in a very early state and will take a lot more time before its ready for production. We aren't even thinking about federation with other platforms yet.
I've been plotting filthy shenanigans with hostname resolution and #activitypub actor scripts to make my instance able to follow virtual @*@twitter.com accounts, since my twitter is very much a read-only data feed, when i remember it even exists
Ok I know I only just got my new instance up (and still haven't even managed to properly migrate from mstdn.io), but I'm already thinking of moving again, from mastodon to #pleroma. It looks so much more lean and hackable, and it can use the same frontend, with full feature parity. Am i missing something or is that a win win?
Once I finish the nix config for it it'll just be a case of figuring out how to move my data from one db to the other. (I gather masto dbs aren't exactly neat...)
Patiently waiting for yet another PR to merge so I can have spend yet another week trying to update #nixos on my raspi. It's only been a month or so since it last built properly...
Trying to migrate from my old instance to my personal one, but it keeps bugging out... I was formerly @firstname.lastname@example.org
Mathematician, Linguist, Software Engineer, Armchair Political Commentator, Something That Takes Five Words
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!