2y
Really I just want to gut the backend and replace it with something else.

Keep the akkoma fe for familiarity but not have that bloated db and crappy admin interface.
❤1
4
0
0
1
User avatar
Stefan (Sharkey Edition) @stefan@shark.lightnovel-dungeon.de
2y
@norm I do have to say keys admin-interface is really nice compared to admin-fe which is a convoluted mess at best. I dunno how well maintained admin-fe is. We all know its jank...
1
0
0
0
User avatar
Stefan (Sharkey Edition) @stefan@shark.lightnovel-dungeon.de
2y
@norm Generally I do like akkoma and its frontend. But man some stuff is just weird. Sadly I lack the knowledge to make it better ​:neocat_sad:​
1
0
0
0
2y
@stefan I have ideas but currently not the time or energy
1
0
0
0
User avatar
Stefan (Sharkey Edition) @stefan@shark.lightnovel-dungeon.de
2y
@norm It really is a shame pleroma/akkoma are written in that obscure language sometimes...

I do still have massive respects for floati taking this on.
1
0
0
0
User avatar
Stefan (Sharkey Edition) @stefan@shark.lightnovel-dungeon.de
2y
@norm tbh I would love to have like key-backend with a modded akkoma-fe that exposes the admin-features of key.
1
0
0
0
2y
@stefan I have kinda thought about moving to iceshrimp once the c# rewrite moves along more
1
0
0
0
User avatar
Stefan (Sharkey Edition) @stefan@shark.lightnovel-dungeon.de
2y
@norm do they have an option for different frontends?
1
0
0
0
2y
@stefan I do know that akkoma-fe was ported over to iceshrimp though that is with their older nodejs backend

They do seem to be prioritizing mastodon API support so I don't think it's unreasonable to try having akkoma's frontend on that
1
0
0
0
2y
@stefan I do also kinda want to have the option for a misskey like frontend too
1
0
0
0
User avatar
Jeder neocat_floof_googly_woozy neocat_flag_agender 🔜 eth0 @jeder@miau.jeder.pl
2y
@norm @stefan i mean akkoma-fe on iceshrimp is unmaintained, it was like one of those short-term hyperfocuses by people that don't work on it anymore
❤2
1
0
0
2
User avatar
Jeder neocat_floof_googly_woozy neocat_flag_agender 🔜 eth0 @jeder@miau.jeder.pl
2y
@norm @stefan and anything that was made with it, is on an unmaintained branch
❤1
2
0
0
1
User avatar
Stefan (Sharkey Edition) @stefan@shark.lightnovel-dungeon.de
2y
@jeder @norm Thanks for the infos! I did see that iceshrimp is API-compliant with Mastodon so all its clients work there as well.

I don't mind keys frontend on desktop per se. Just for mobile I would need something a bit less fat. Sharkey/Misskey did improve their PWA massively in that regard but it stills feels a bit sluggish at times.

Now a proper misskey-mobile client would be a solution here. Still unsure what I want use going forward.
⭐1
1
0
0
1
User avatar
Jeder neocat_floof_googly_woozy neocat_flag_agender 🔜 eth0 @jeder@miau.jeder.pl
2y
@stefan @norm i should probably also say that sharkey(and misskey 13 in general)→iceshrimp migration is very problematic to say the least, there's the "remove createdAt" Misskey migration which isn't reverting properly from what i can understand
1
0
0
0
User avatar
Jeder neocat_floof_googly_woozy neocat_flag_agender 🔜 eth0 @jeder@miau.jeder.pl
2y
@stefan @norm like, it's possible but someone would have to find a way to properly introduce createdAt column in all the db tables, since all the down function of the migration does rn is, it just creates it with nothing inside it
2
0
0
0
2y
@jeder @stefan I think in general doing a bunch of reverts to migrations is fraught with peril, I remember reversing the foundkey stuff to move to firefish was pretty tough as well.
1
0
0
0
User avatar
Jeder neocat_floof_googly_woozy neocat_flag_agender 🔜 eth0 @jeder@miau.jeder.pl
2y
@norm @stefan well, that, compared to the problem we have here, is way easier to deal with
❤1
0
0
0
1