Give that tester a raise bro

Didn’t he just win the Euros at 17

Nginx is owned by F5 now which is an American company so it’s not RU anymore

They should’ve stuck to v0.X versioning until it’s ready. Makes no sense to up to v1 if it’s still in alpha/beta

And your way to look at things that “all apps must be 20 mb or less otherwise they are unoptimised” is better because?

Your phone has bigger problems if it cannot take 170mb apps, this isn’t the 1990s

Dumb comparison

That’s regarded

Not OP but I’ve accidentally fingered another key a split second before hitting enter a few times. It’s not implausible.

From what I’ve understood SSPL is a ridiculously ambiguous license, it’s extreme copyleft. It’s not just “open source the tooling you use to host the software”, it can also be interpreted to mean “open source all the hardware and firmware you use to host the software”. No one wants to risk going to court for that so corporate wants to use SSPL licensed software.

AGPL is the best license you can go for IMO.

Shift + right-click will override all this BS in Firefox.

Obsidian is one of those applications I sooo want to install because everyone loves it, but to me if I’m going through the pain of selfhosting I want to go FOSS only. Argh!

In very basic terms - GPL means that any modifications you make to a code base and distribute to public, you need to keep the license as GPL and open source all your modifications.

Once cloud started becoming a thing, the cloud vendors went “Well ackchyually🤓, the code changes we’re making are hosted on OUR server so we’re not technically distributing them to the public. So fuck you we have no obligation to make them open source”.

Which is why AGPL exists so even server side code needs to be public. Since the application in question here is a backend service, it’ll always be used server side and so any forks need to be open source.

Normally a breaking change means after you apply the change it’s not easy/straightforward to rollback to the older version if you want to do that for whatever reason.

For example, a new version is released and underlying database table or structure changes. You upgrade properly, and find the new version has some bugs (or you simply don’t like it). If you want to use the older version again until the newer one is fixed it’s not a matter of simply point to old version.

As the database structure has fundamentally changed underneath in the new version, when you put back the old version it simply doesn’t understand the new structure and might stop working. You need ways to be able to make the DB structure compatible with the older application.

If the application is stable the devs might provide ways to do this. But since this is an alpha… You’re on your own.

TL;DR it means the older and newer version of the application aren’t strictly compatible with each other

I thought this was about FIFA

that would mean anyone going to http:// will perceive as the server being down so what you are saying will not work in practice

Funniest thing I’ve ever seen is the docs for Nginx do the same, no http to https redirection. I mean, you would hope that the maintainers for the biggest web server in the world would be able to manage that but somehow… No they don’t.

How do you not do research on the dimensions of anything before buying something big like a TV?

This is still reasonable IMO, unless people are binge watching a Netflix release in the entire day they can wait for the next day to download subs.

I’m not an expert but in theory it doesn’t sound like a bad thing as long as you allow people to change it whenever possible. It feels like people change jobs, phone numbers, usernames, locations, genders, names and yet it’s extremely unlikely that they will out and out delete their old email address so it’s always something to personally identify someone by. And of course it’s always going to be unique unless you’re 0.0001% of the population who fuck around with self hosting email or something.