It doesn’t make a lot of sense for LetsEncrypt to spend time adding support for such certs, since both a domain name and a cert from another CA are cheaper than buying an IPv4 block
It doesn’t make a lot of sense for LetsEncrypt to spend time adding support for such certs, since both a domain name and a cert from another CA are cheaper than buying an IPv4 block
certificates can only be obtained for domain names
That is not true, nothing prevents it on the technical side, and even some trusted CAs sell them under certain conditions
you can also accomplish that by turning off city’s electrical grid
You can’t read documentation if there is no documentation
This comment is posted through my personal private instance :)
Acquiring knowledge about the product takes time. Upstream has a better position just by being the one to create it and having all the knowledge about the product immediately, not after some time. Someone who decides to rebuild that would either have to fully maintain their own fork (and open source their work as well if the upstream has copyleft license), or upstream their changes, since reapplying bug fixes and new features requested by clients on top of the original codebase will take more and more time with each upstream change. Upstream can also restrict the use of their trademark, which would add a burden of marketing to downstreams as well.
if I develop some special software for dentists or whatever, and I open source it, all I get is that someone else builds the code and distributes it for free so I can’t easily sell it anymore.
Are there a lot of industries that would accept a piece of software that comes without techical support and/or liability?
Inaccurate, this error fits on one screen
Their clunky and unpleasant Ui, but mainly this
A series of VPSes running AlmaLinux, I have a relatively big Ansible playbook to setup everything after the server goes online. The idea is that I can at any time scrape the server off, install an OS, put in all the persistent data (Docker volumes and /srv partition with all the heavy data), and run a playbok.
Docker Compose for services, last time I checked Podman, podman-compose didn’t work properly, and learning a new orchestration tool would take an unjustifiable amount of time.
I try to avoid shell scripts as much as possible because they are hard to write in such a way so that they handle all possible scenarios, they are difficult to debug, and they can make a mess when not done properly. Premade scripts are usually the big offenders here, and they are I nice way to leave you without a single clue how the stuff they set up works.
I don’t have a selfhosting addiction.
I would recommend Porkbun, been using it for almost 1.5 years after I had to migrate from Namecheap. Wouldn’t really recommend the latter
The check $LEMMY_HOSTNAME == http*
will give a false positive if (for whatever reason) the domain name starts with http
Here, it isn’t open source.