Conversation
okay I'm kinda considering hosting my own instance now-

I just have the difficulty of "which server software should I choose?" because I wanna avoid Mastodon and all its forks, and I kinda want to host an Akkoma instance but then database rot is a thing and I need to stay below 100GB of disk usage-
(also, I kinda wanna try GoToSocial tbh)
9
1
2
@awoo as a chronic instance admin in relapse, having hosted 8 akkomas:

- akkoma: don't don't don't no back stop don't, However if you do follow my guide https://enby.space/blog/opinionated-akkoma/
- chuckya's fork of glitch's fork of mastodon supports akkoma-fe with a hack
- gotosocial is cool but doesn't support a lot quite yet
- iceshrimp.net is really promising!!! you should give it a try :>
2
0
3

@nbsp @awoo neofox_owo that blog post is interesting. im gonnya do that immediately

1
0
2
@starshine @awoo lmk if you need help moving back to config.exs, i've got the old snowdin.town config lying around somewhere still
1
0
3
fedi instance-related update
Show content

so, I’m currently stuck choosing between choosing either one of those:

  • Akkoma (even though multiple people have been like “don’t, no, stop, avoid that!!” - sorry peeps but I’m just very used to Akkoma at this point.)
  • GoToSocial (even though some features I’d like (like emoji reactions or following hashtags) are missing)
  • Iceshrimp.NET (even though it feels weird to have a fedi instance software in .NET in the first place, and configuring it using .ini files feels even weirder (on top of that, the frontend seems to still be incomplete so that’s going to be fun to use on a laptop/desktop then))

It has reasons why I avoid Mastodon (I absolutely do not like the direction in which things seem to go) and its forks (which often times make things more complicated to maintain, especially glitch-soc unfortunately), as well as Misskey and its forks (which all have a (frankly speaking) bloated frontend and no Mastodon-compatible API, meaning that I can’t use most of the mobile clients out there) so yeah-

4
0
1
fedi instance-related update
Show content

@awoo you can use netshrimp with like, standalone masto frontend like i have chuckya frontend on masto.jeder.pl and that works quite okay
but yeah

1
0
1
re: fedi instance-related update
Show content
@jeder ...the thing is, I don't really like the Mastodon frontend either, it's too simple (default FE) or too complicated (Tweetdeck-like FE) 🥴
2
0
1
re: fedi instance-related update
Show content
@jeder I'm basically like "give me something in the browser that works like Akkoma-FE and I'm happy"-
1
0
1
re: fedi instance-related update
Show content

@awoo @jeder would https://enafore.social/ be any good or is that also too simple? (it almost definitely is tbh)

1
0
1
re: fedi instance-related update
Show content
@starshine @jeder it's way too simple unfortunately
0
0
2
re: fedi instance-related update
Show content

@awoo i mean like, same but that’s what I have to deal with for a longer bit
and trust me, you will either find third party web clients good or absolutely bad, so like, chuckya is pretty much what you have to use and it’s somehow heavier than misskey frontend, I have no idea why or how but it is

0
0
1
@awoo blobcatgoogly everytime i hear Akkoma database rot, my eyes starts googling
0
0
0

@awoo if you consider hosting Fedi at home, be aware that it’s like DDoSing yourself :p

1
0
0
@amythegay I'm not hosting it at home but on some other server that I'm setting up for the purpose of hosting a fedi instance.
0
0
1

@awoo@femdom.solutions i know, hahaha misskey bad, but misskey is genuinely pretty good if you dont mind the web UI

1
0
1
@privateger I do mind the web UI because how else am I supposed to use it on the desktop?
1
0
1

@awoo@femdom.solutions mind being equal to liking it in this case ​neofox
id recommend mastodon-chuckya then (mastodon is still mastodon, but that makes it bearable)
id stay far away from anything pleroma/akkoma, database rot is just a pain in the ass and its hard to deal with in general

GTS was extremely unfinished and just felt bad when I tried it, maybe that changed in the meantime

1
0
1

@awoo@femdom.solutions dunno how mastodon database size develops over longer periods of time, i only host this instance in prod, so I have misskey numbers only

currently its at 55GB, with 41 million posts and 6 million files in the DB after over two years of runtime

0
0
1

@awoo i'm waiting for the iceshrimp net beta right now

1
0
0
@lunarna i'm just wondering what makes people consider Iceshrimp.NET tbh-

(like, so far I haven't seen much of a reason for myself to actually try it)
0
0
1

@awoo
Im running GTS and its great, yeah some missing features but tbh those are features that I don't use anyways
Can only recommend it

1
0
0
@89q12 I’m guessing that emoji reactions count as one of the missing features?
1
0
1
@89q12 even if so, I might actually want to try that for a bit to see how it is - if it’s good enough for me then I’ll set up my own instance ^^
0
0
1
re: fedi instance-related update
Show content

@awoo I mean, I absolutely love Akko, obviously. Seems like the best to me, but it’s up to you ofc

1
0
1
re: fedi instance-related update
Show content

@emma @awoo akkoma is obvious the superior choice imho

1
0
0
@nbsp
> however, the only current way to interactively add emoji to your instance is through admin-fe
Wrong, i never used admin-fe
1
0
0

@nbsp @awoo moving “back” neofox_nervous we started with database config and never really touched the config file (this was a terrible idea) (it almost bricked our instance when we upgraded)
i hope we can figure it out neofox_up

0
0
1
re: fedi instance-related update
Show content

@yassie_j @awoo @emma DB rot is an issue, but staying under 100GB isn’t at all. I’ve got a hell of a lot more then just Akkoma running at I’m only at 90Gb on a 50+ user instance, with large media uploads enabled.

0
0
1
@Jain are you using the filesystem on your server? that would be impossible to do unless you have ssh access to the server, and what i'm talking about here is specifically allowing mods to add emoji
if there is a web UI built into akkoma that lets you add emoji via user authentication that isn't admin-fe do let me know and i'll link it
1
0
1
fedi instance-related update
Show content

@awoo if web frontend is important to you i'd avoid gts, it has none (i've entirely switched to Tuba on desktop)

1
0
0
fedi instance-related update
Show content
@lnl I am aware that gts has none, that’s why I’m wondering if there are any good ones that one can use through the browser-
1
0
0
@nbsp Yes i do and yes you are right, mods cant just add emojis except on admin-fe. However i moved all emojis into a git repo and gave multiple persons access to it... Shouldnt be that hard to automatize git pulls
1
0
0
@Jain sure but that's a hack predicated on the fact akkoma's config structure is actually fucking concussed
1
0
0
@nbsp i disagree... Why do you think so?
1
0
0
@nbsp tbh, having emojis like misskey seems way more cursed to me
1
0
0
@Jain if there's anything that should be done in a database instead of with config files it's emoji management and grouping and that's the One Thing akkoma still does in the filesystem
the misskey approach of uploading them as arbitrary drive files and then linking them is . odd, yes.
to me the solution is to have a file structure much like akkoma's but without the pack.json files dictating what goes where. that should be done in db.
and also you shouldn't need to turn dbconfig on to Access Emoji. they're not even the same thing they're just grouped together in the frontend.
1
0
0
@nbsp when i started admin fediservers i had to learn that emoji management is one of the most cursed tasks ever. Reasons for this are very simple, any destructive work break posts. Means, you cant just rename or delete them and if one want to have a proper set, one has to check if they are allready added at some point. So tbh, this can have a complexity by itself that im in the opinion that i rather prefer raw files and jsons so that im able to manage them by helping tools so therefore i strongly prefer to not have them within a db at all
0
0
1