Glad I held back from suggesting Firefish for my wife. I’ve been slowly trying to convince her to jump to the fediverse for microblogging and figured to have her try Firefish simply because it’s prettier than Mastodon. Guess it’s back to ol’ Mastodon.
There are some. Mastodon has a lot of garbagey nonsense, but they do at least have a proper API which will let you make a non-shit front end if you wanted.
That’s not what I mean. Lemmy has two separate repositories: one for the backend, and one for the default frontend. New frontends can be written and straight-up hooked into the server’s backend instead of making all those API calls. For example, see https://photon.lemmy.dbzer0.com/ vs https://lemmy.dbzer0.com/.
Well, Lemmy’s front end talks to it’s back end via an API, which is pretty much how every web app of any scale works these days.
There’s really not any particular difference between a monolithic app vs a seperate front end in terms of “all those API calls” since everything is basically calling APIs at this point, if they’re not made by complete incompetents. (In the case of Mastodon, though, I suppose complete incompetent is possible.)
photon doesn’t directly communicate with the backend, it’s not intended for that. but even then, lemmy-ui is almost entirely client side (for some reason) and it makes its calls to the API
Glad I held back from suggesting Firefish for my wife. I’ve been slowly trying to convince her to jump to the fediverse for microblogging and figured to have her try Firefish simply because it’s prettier than Mastodon. Guess it’s back to ol’ Mastodon.
You can suggest Akkoma to her if you want a Mastodon alternative.
Thanks! I’ll check it out.
Closer to Firefish would be Iceshrimp, a fork of Firefish started when the writing started to appear on the wall.
Does anyone know if Mastodon have that “multiple frontends” thing Lemmy has?
There are some. Mastodon has a lot of garbagey nonsense, but they do at least have a proper API which will let you make a non-shit front end if you wanted.
That’s not what I mean. Lemmy has two separate repositories: one for the backend, and one for the default frontend. New frontends can be written and straight-up hooked into the server’s backend instead of making all those API calls. For example, see https://photon.lemmy.dbzer0.com/ vs https://lemmy.dbzer0.com/.
Well, Lemmy’s front end talks to it’s back end via an API, which is pretty much how every web app of any scale works these days.
There’s really not any particular difference between a monolithic app vs a seperate front end in terms of “all those API calls” since everything is basically calling APIs at this point, if they’re not made by complete incompetents. (In the case of Mastodon, though, I suppose complete incompetent is possible.)
Oh, I didn’t realize that.
photon doesn’t directly communicate with the backend, it’s not intended for that. but even then, lemmy-ui is almost entirely client side (for some reason) and it makes its calls to the API
Have you checked out Tangerine UI
https://github.com/nileane/TangerineUI-for-Mastodon
deleted by creator
See what I said above. I don’t mean clients, I mean frontends.
Sharkey might also be worth a look.