Seems like it. That's sad, because it seems to be a very nice project and I'm still waiting for a FOSS keyboard that supports german and japanese input in one.
Well, it's open source, so anyone can continue working on it.
No, it's about Americans always thinking they come first. I was told so many times that "rEdDiT Is aN AmErIcAn wEbSiTe"... But now, they can't pull that shit any more.
I like both. But many people don't even realize that nano has quite a lot of configuration options. To me, they're text editors, not code editors. For code, I use VSCode (or "code", the FOSS variant).
I think, the default docker-compose.yml and lemmy.hjson state that the PostgreSQL password and the pictrs API key have to match? If I remember correctly, they both have something like {{ postgres_password }} as default. I found that weird, but I also didn't question it.
What do you do if one service requires PostgreSQL 15 and another service requires an older version or something like that? Again, if I remember correctly, Lemmy devs recently downgraded PostgreSQL in the default setup for some reason.
I don't want to fact check what I said right now, because I'm in the bathtub. I'm just talking from the top of my head.
Don't get me wrong, I use a similar setup for my homelab, because I hate spinning up several instances of entire database servers just to get a service running. But I'd be lying if I claimed that I never ran into issues with that setup.
That's a pretty bad point you made there. Imagine having to google for each app on your smartphone and tell me how that's better.
What about the scammy search results that point to malware infected sites?
What about stability and security updates for the software you obtained that way? Every software will have it's own update mechanism, if there's one at all.
How is it not better to install or update all software on the computer with a single click or command?
That happened due to the emoji vulnerability. One mitigation step admins had to take is rotate JWT secrets, which essentially deauthenticated everyone's sessions.
Lemmy-UI and some 3rd party applications didn't know how to react to that, as this is not an official Lemmy feature (it required a database query), so they stayed in that limbo state you're describing here.
Just log out and back in. If the problem persists, delete the cookie for your instance and try again.
Seems like it. That's sad, because it seems to be a very nice project and I'm still waiting for a FOSS keyboard that supports german and japanese input in one.
Well, it's open source, so anyone can continue working on it.