At some point it’s good to let things die
At some point it’s good to let things die
In that case, i recommend step-ca, which is a certificate authority server with acme support anyone can self host. The setup took a while but it’s been running for months now without problems for me.
No proper CA should give out a certificate for an IP, that’s a no go by the common rules.
The background is that certificate revocation is a broken system and having short lived certificates makes the problem go away. You don’t need to worry about how to tell people that some certificate is bad if it’s only valid for a few days.
Ideally, certificates would only be valid for a few days, it should be automated anyway. This has other downsides as I can imagine, like creation of more traffic. My self signed CA for my home LAN has 4 days as standard, and it works perfectly fine.
While true I feel like your comment misses the point. A raspberry pi is just a computer, not a magic solution box that’s kept maintained and updated by some guy. Their product isn’t a service, it’s just the device.
Logseq is good but it doesn’t have all the obsidian features: it handles markdown a bit differently, does not just use the file tree and has no tags.
Synfonium is the only thing that I could get to work with my selfs hosted jellyfin server and with downloading of music. I haven’t had any problems with it though.
Japanese has been an open issue for months now, so it’s a nope from me.
I use audiobookshelf. You need to have some (self hosted or not) server to use the client, but I find that software incredibly well made.
Why do you think so? I see it as a strength in diversity and a great driving force for a proper server api
In Germany at least, I hear that banks have weird law requirements for these weird security things, like photoTAN.
I’d be much happier if they’d just let me do my usual setup with password, totp and my hardware token.
Yes. And if possible message them with encrypted messaging, like signal or at least Whatsapp, not discord. Then again, the credentials are already public.
It’s not about supporting new and interesting stuff. Everyone wants to work on new and interesting stuff. Public funding is more about keeping the old boring stuff that nobody wants to maintain usable.
It’s a hard fork by now, but the switch should still be pretty painless.
In what way? Works for me
Forgejo actions is basically GitHub actions. The difference in my ci scripts is a single line and you can even use GitHub action templates or whatever they’re called.
You just need to add some runners to your server, which is pretty easily doable by just using some docker container and deploying that multiple times
So why do that? Seems like you’re just piping the output to null?
So if you have to get it working on Wayland, I don’t think it works flawless. What exactly did you do?
That’s correct, but it still can be separated without too much effort, unlike if it would just be one thing.
I found open-ssl to be much harder to use. Do you just manually make new certificates with the CA in CLI?