@aelaraji@aelaraji.com gotosocial is epic
So… I wanna take a stab at the #ActivityPub bee hive, but I’m not sure what to pick up, a #Gotosocial pocket knife or a #Snac2 bamboo stick? Any thoughts?
@kat@yarn.girlonthemoon.xyz lack of RAM, or weak CPU? I run GoToSocial too, on a 1GiB RAM VPS. 😅
CAN MY FEDI INSTANCE STOP CRASHING
(it is running gotosocial which is like one of the lightest fedi servers out there. the machine it runs on is as old as a high schooler. guess the root problem)
@prologic@twtxt.net Gemini has an answer for you:
This is a conversation thread from a twtxt network, detailing a user’s (movq) frustration with the Mastodon “export data” feature and their consideration of self-hosting a fediverse alternative. Here’s a summary:
- movq’s initial issue:
- movq is concerned about the volatility of their data on their current Mastodon instance due to a broken “export data” feature.
- They contacted the admins, but the issue remains unresolved.
- This led them to contemplate self-hosting.
- movq is concerned about the volatility of their data on their current Mastodon instance due to a broken “export data” feature.
- Alternative fediverse software suggestions:
- kat suggests gotosocial as a lightweight alternative to Mastodon.
- movq agrees, and also mentions snac as a potential option.
- kat suggests gotosocial as a lightweight alternative to Mastodon.
- movq’s change of heart:
- movq ultimately decides that self-hosting any fediverse software, besides twtxt, is too much effort.
- movq ultimately decides that self-hosting any fediverse software, besides twtxt, is too much effort.
- Resolution and compromise:
- The Mastodon admins attribute the export failure to the size of movq’s account.
- movq decides to set their Mastodon account to auto-delete posts after approximately 180 days to manage data size.
- Movq also mentions that they use auto-expiring links on twtxt to reduce data storage.
- The Mastodon admins attribute the export failure to the size of movq’s account.
That’s a great idea. I am running GoToSocial in a local server (like Raspberry Pi) and it’s working fine.
@kat@yarn.girlonthemoon.xyz Oh, yes, it’s probably going to be something like gotosocial or snac. It’s got to be as lightweight as possible. (I call this whole thing “Mastodon”, but you’re right, that’s not quite correct. 😅)
@movq@www.uninformativ.de mastodon is probably the worst fedi software to self host tbh, you might wanna check out gotosocial? not to like pull you in another direction but idk masto is just suuuuper heavy lol
Wow, GtS keeps getting better! Re: https://docs.gotosocial.org/en/latest/admin/domain_permission_subscriptions/#fun-stuff-to-do-with-domain-permission-subscriptions
@kat@yarn.girlonthemoon.xyz i’m reading this and i already have a gts server that i could secure with this but i’m thinking it’d be best for most of my public sites https://ovelny.sh/blog/a-complete-guide-for-your-gotosocial-server/
GoToSocial snapshot has gained “editing statuses” capabilities (and the ability to see the update trail as well). That was one of the things I wanted to most to be implemented. Actually, that sits at the top of my wish list. Next is push notifications.
@prologic@twtxt.net that “little database that could” is simply amazing, isn’t it? I run Conduwuit (nevermind, this one is RocksDB), and GoToSocial using it as a backend, no issues. And, of course, sqlite is the database of choice for a lot of things under iOS.
@bender@twtxt.net I have nothing against GoToSocial, but:
GoToSocial stores statuses, accounts, etc, in a database. This can be either SQLite or Postgres.
snac
is simpler. Some JSON files and that’s it. I can read them with jq
and less
. I can use tar
to back them up. I can hand edit them in a text editor.