Today I stumbled upon Epicyon:
Epicyon is an AGPL licensed ActivityPub protocol compliant federated social network server suitable for hosting a small number of accounts on low power systems requiring minimal maintenance, such as single board computers. It’s the ActivityPub equivalent of an email server, storing posts as human readable JSON on file, rather than in a database. It also uses only a small amount of RAM.
This is right up my alley. No weird Ruby code like Mastodon. No new stuff like Elixir. No database! I work with databases all day long and that’s why my wiki also doesn’t use a database.
Yay! I might try this myself.
Continued: 2019-11-09 Epicyon needs Python 3.6 which needs a Debian upgrade.
2019-11-09 Epicyon needs Python 3.6 which needs a Debian upgrade
#Epicyon #Mastodon #Social Media
(Please contact me if you want to remove your comment.)
⁂
Now that I have it running, I noticed:
– Alex Schroeder 2019-11-09 22:27 UTC
---
I edited `/etc/systemd/system/epicyon.service` to set `--registration` to `closed` and reloaded it all by running `systemctl daemon-reload`. I *think* the subsequent `systemctl restart epicyon` wasn’t necessary.
– Alex Schroeder 2019-11-10 12:34 UTC
---
Well, I’ve added some issues. And I’m still struggling with remote following.
– Alex Schroeder 2019-11-10 21:31 UTC
---
Another aspect I dislike is that basically whatever CPU Quota you give Epicyon, that’s what it takes. What’s it doing? Somehow I was expecting it to not do anything if other instances didn’t contact it.
– Alex Schroeder 2019-11-12 21:13 UTC