3·
4 months agoDidn’t he just win the Euros at 17
- 0 Posts
- 13 Comments
Joined 1 year ago
Cake day: June 22nd, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
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
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.
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
Don’t kid yourselves, regardless of all your ideals open source only works because it’s free from a monetary perspective.
Companies work on patches to Linux or other software because it primarily benefits themselves, and they only use Linux because it’s free. Companies create hardware on Linux because it’s free. They can manufacturer cheap devices and people will buy them because they were low cost primarily because of the use of FOSS software.
Nearly all of FOSS is funded by corporations whether you like it or not, for the reasons you want to hear or not. The only thing that drives people is money.
36·1 year agoLemmy itself! Can’t say what because I’ll doxx myself since I’m doing the fixes under my IRL name but yeah it’s nice contributing.
The only thing which F-Droid reports is that it uses jawg.io for visualising the map tiles and that is considered non-free is because it is… commercial?
This is the quote from the Streetcomplete github:
Personally I don’t care that much about FOSS/non-FOSS but IMO a reason like that is least of my concerns when looking at open source. If they’re providing a free (as in money) service to an open source app then that’s perfectly fine.