The only one who is winning here is the Chinese government.
Dirk
joined 2 years ago
Exactly. With directly using certbot handling all and everything fully automatically I ran my old setup with a free dyndns subdomain for quite some time without any issues.
Since Let’s encrypt nowadays is basically implemented in every reverse proxy: certificates are an absolute no-brainer.
If someone manages to buy and configure a domain to serve selfhosted content, this person will also be able to either set up certbot or use the built-in functionality of their reverse proxy.
It's 2025. Not having "real certificates" is something admins intentionally do. Since there is Let's Encrypt available, all other solutions for non-paid certificates are obsolete.
There – of course – won’t be a singular official source stating “Hey guys, we’re open core now”. You need to put this together bit-by-bit.
Here are some links for research
- Official statement on the takeover
- Gitea Enterprise/Gitea Cloud hiding features behind a cloud solution and a paywall which makes Gitea itself open-core
- Open Letter to the new Gitea owners with a summary and a reply, signed by a lot of Gitea devs and FOSS scene people.
- As @gratux@lemmy.blahaj.zone mentioned: A fork under the name Forgejo was done due to new Gitea owners did not care much about the concerns. (Started as asoft-fork but with 10.0 it became a hard fork.)
- Gitea owners made it mandaroy to remove copyright headers and set the corporation as copyright holder. Here, here, and here
It falls under self hosted, at least. If it is still truly open source is highly debatable.
Never heard of 99% in that list.
Also, Gitea should not be there. It is a corporate -owned open core project that was hostilely taken away from the community.
That would be a wild experiment.
Dillo is 25 years old
Yeah, I can tell from the look and features. *scnr*
What's the use case for that browser? Daily-driving it to browse the web likely not, right?
Exactly. Your KVM switch need to support it, or your clients will always act like you unplugged the screen when you switch between them.
Check the manual of the switch if it simulates a connected monitor for the client.
Some clients are picky when it comes to unplugging monitors or booting without one.
Wayland also seems to do something weird when the monitor is off (I have some applications where the window becomes tiny when turning off the screen).
Basically "Someone said something I disagree with. Instead of dealing with it or ignoring this user, I want the whole instance to be nuked!".
I can't wait for Brodie to report on this!