For an internal project that’s fine, and under semantic versioning you can basically break anything you like before v1.0.0 so it’s probably valid

Date based version numbers is just lazy. There’s nothing more significant about a release in two weeks (2025.x.y) than today (2024.x.y).

At least with pride versioning there’s some logic to it.

Single player blackjack against the dealer is a good choice.

The basic rules of the game are easy to implement so the payoff is quick and you can extend it later with additional complexity if you like.

• Aces as 1 or 11
• splitting doubles
• Betting
• Random card, single deck, multiple decks etc
• Dealer logic as AI
• Player AI with card counting

How does migrating go codeberg solve the issue of false star ratings?

I think is the logic used for Linux kernel versioning so you’re in good company.

But everyone should really follow semantic versioning. It makes life so much easier.

Written in bash?! Superb effort but I can’t help wondering why you’d choose bash?

Which everyone will ignore.

Do websites come under the remit of self hosting?

Personally I host static websites with GitHub, cloudfront, netlify, onrender etc. Trivial to setup, more reliable and better cdn distribution. Anything dynamic lives in a data center rather than a self host setup.

Fair, but you were asking how people approach security for self hosted solutions and I guess I’m challenging why anything needs to be public. Self hosting is typically for your own services which can usually be hidden behind a VPN.

The exception I guess is email, but I never understand why people attempt self hosted mail servers

Don’t expose anything publicly, instead setup wireguard for every VM. Connect your phone, PC etc to the VPN so you have full access without publicly exposing anything.

You may have touched on this but your post was way too long so I only read the headings

Indeed, that’s why I use the AGPL license. Corporations hate it because it forces them to give back.

That’s actually pretty reasonable. I’d be happy to make my open source projects compliant for a company - but they can damn well pay me for the effort.

Why do so many projects ignore semantic versioning? It’s so much easier to comprehend changes when versions are major, minor or patch

Is there a Lemmy community for /c/ShitAmericansSay

What a terribly written article. I got half way through and just gave up.

Actions have consequences. It’s important we have precedents that the world is just

Why would you want any of that in a text editor…?

This thread might be the fastest I’ve ever seen discussion devolve from “that could be interesting” to just incomprehensible screaming.

But only, if you know what you are doing, or if you want to learn about it.

This is the crux of it though. Sure you can tweak your system but the average users doesn’t know what they are doing or where to learn more.

I’m not even convinced OP knows what problem they’re trying to solve

It’s ridiculous we’ve been over complicating matters for so long. It’s far easier knowing legal arguments can be determined simply by who’s more willing to jerk off the administration.