I’ve been running Akkoma on a system with decent CPU, tons of memory, fast disk and fast upstream. It seems to have issues where things don’t happen quickly enough, giving images that don’t load and even occasionally blank web pages. Something’s not quite right, and if nothing else, the idea that a request can fail within ten seconds just doesn’t make sense.
I’m looking forward to trying snac2 because it seems much more lightweight and has a much more reasonable dependency list. I’m also quite interested to see whether the loading problems go away, since I don’t know enough about Akkoma to really diagnose it.
The TODO is worth checking out to see if you’d miss any of those features. gotosocial and honk are some other lightweight options depending on where you want to be on features vs minimalism.
I don’t know how it compares to snac2 but gotosocial takes about 300MB including full support for media transcoding for thumbnails and previews and stuff. (used to be closer to 200MB before they added the media features) I’m not sure how to measure its CPU consumption because I’ve never been able to see it show up in top for more than a fraction of a second.
I wrote about my instance on my blog; it’s very easy to set up and I’d recommend it to anyone interested in running their own server. I used to run a pleroma server (which akkoma was forked from) and even contributed some features to pleroma, but IME gotosocial is a lot easier to operate.
A +1 for GotoSocial (although I’m only using it for my bots because Pleroma appeared first and I cannot be bothered trying to decode the horrible[0] GTS code to fudge in post importing for moving my main across.)
[0] It’s the “ABSTRACT EVERYTHING” style of Go code that has interfaces and layers like a mille-feuille made by a master pastry chef. Despite working exclusively in Go for nearly 10 years, I find the Akkoma Elixir source easier to read than the GTS source.
They seem to allow CSV file imports, so if you can get Pleroma to export something, you could probably massage the export into the correct format. They call it Mastodon export CSV, so it might even be something ready-made for Pleroma->Mastodon. It doesn’t seem to import everything, eg. posts.
Another route if you have a file dump is to peek into the database (SQLite or Postgres) and simply massage the file into a set of SQL queries for you to INSERT. The database tables might be easier to grok than the Go source code. This route will (in theory) allow you to import everything.
I think that’s only for things like followers, following, etc., not post content. Which is the faffy bit because I would want to migrate the posts across and keep the IDs, etc., to avoid any data loss.
simply massage the file into a set of SQL queries for you to INSERT
Yeah, that might be the route I go if I ever drop Akkoma in favour of standardising on GTS.
Not that I have anything against change and forks per se, but looking at Pleroma and Misskey especially, even when trying to keep track, new forks keep popping up all the time, it’s bit weird. Not even sure if I had looked at Akkoma before.
Misskey has loads of forks to the point where it’s a running gag, but IIUC the situation with Pleroma/Akkoma is more comparable to gogs/gitea where the fork has really taken over and I’d strongly recommend against running the original.
I’ve been running Akkoma on a system with decent CPU, tons of memory, fast disk and fast upstream. It seems to have issues where things don’t happen quickly enough, giving images that don’t load and even occasionally blank web pages. Something’s not quite right, and if nothing else, the idea that a request can fail within ten seconds just doesn’t make sense.
I’m looking forward to trying snac2 because it seems much more lightweight and has a much more reasonable dependency list. I’m also quite interested to see whether the loading problems go away, since I don’t know enough about Akkoma to really diagnose it.
Development seems quite active, too. Good stuff!
The TODO is worth checking out to see if you’d miss any of those features. gotosocial and honk are some other lightweight options depending on where you want to be on features vs minimalism.
I don’t know how it compares to snac2 but gotosocial takes about 300MB including full support for media transcoding for thumbnails and previews and stuff. (used to be closer to 200MB before they added the media features) I’m not sure how to measure its CPU consumption because I’ve never been able to see it show up in
topfor more than a fraction of a second.I wrote about my instance on my blog; it’s very easy to set up and I’d recommend it to anyone interested in running their own server. I used to run a pleroma server (which akkoma was forked from) and even contributed some features to pleroma, but IME gotosocial is a lot easier to operate.
A +1 for GotoSocial (although I’m only using it for my bots because Pleroma appeared first and I cannot be bothered trying to decode the horrible[0] GTS code to fudge in post importing for moving my main across.)
[0] It’s the “ABSTRACT EVERYTHING” style of Go code that has interfaces and layers like a mille-feuille made by a master pastry chef. Despite working exclusively in Go for nearly 10 years, I find the Akkoma Elixir source easier to read than the GTS source.
They seem to allow CSV file imports, so if you can get Pleroma to export something, you could probably massage the export into the correct format. They call it Mastodon export CSV, so it might even be something ready-made for Pleroma->Mastodon. It doesn’t seem to import everything, eg. posts.
Another route if you have a file dump is to peek into the database (SQLite or Postgres) and simply massage the file into a set of SQL queries for you to INSERT. The database tables might be easier to grok than the Go source code. This route will (in theory) allow you to import everything.
I think that’s only for things like followers, following, etc., not post content. Which is the faffy bit because I would want to migrate the posts across and keep the IDs, etc., to avoid any data loss.
Yeah, that might be the route I go if I ever drop Akkoma in favour of standardising on GTS.
Regarding swapping out software, see https://socialhub.activitypub.rocks/t/switching-ap-server-software-on-the-same-domain/4508
Few ActivityPub tools seem prepared to adopt the previous style, and few peers seem prepared to adopt a changing URL scheme.
Snac2 probably takes less than few MB for lightweight instance.
Not that I have anything against change and forks per se, but looking at Pleroma and Misskey especially, even when trying to keep track, new forks keep popping up all the time, it’s bit weird. Not even sure if I had looked at Akkoma before.
Misskey has loads of forks to the point where it’s a running gag, but IIUC the situation with Pleroma/Akkoma is more comparable to gogs/gitea where the fork has really taken over and I’d strongly recommend against running the original.
Is there a snac that preceded snac2?