Putting something on GitHub is really inconsequential if you’re making your project open source since anyone can use it for anything anyway,
Except for people in China (blocked in China) or people on ipv6 only networks, since Github hasn’t bothered to support ipv6, cutting out those in countries where ipv4 addresses are scarce.
So yes, it does matter. Both gitlab and codeberg, the two big alternatives, both support ipv6 (idk about them being blocked in china). They also support github logins, so you dob’t even need to make an account.
And it’s not a black or white. Software freedom is a spectrum, not a binary. We should strive to use more open source, decentralized software, while recognizing that many parts are going to be out of our immediate control, like the backbone of the internet or little pieces like proprietary firmware.
Sometimes I’ve seen people complain about people using asklemmy for not askreddit style questions, but I actually think that’s ok and I’m in favor of that as it means more discussion, content, and visibility.
Eventually asklemmy will reach “critical mass”, and split into more niche communities.
I find it odd, because debian does this by default, actually. They account for usecases like yours, and instead you have to edit a config file or use a command line flag to get it to not install recommended dependencies.
I guess someone is super happy they saved a few hundreds kilobytes of disk space though.
Yes. All the people basing docker images off if debian, and trying to get them as small as possible. The splitting up of packages, allows people to only pull in what they need.
Just like Eelco’s way of governing, it will likely have 0 effect on 99% of people using NixOS,
Flakes not being stabilized, or worked on by Eelco, despite him literally being the inventor absolutely has an effect on every single Nix user. The flakes-nonflakes aplit is part of why the documentation on nix is so poor. Some things only support one or the other, and it’s a pain.
The aux fork of nix (which idk what’s gonna happen to it) said they would stabilize the current implementation of flakes as v0. I hope this new council does the same, because it’s been far too long. So much of the community uses flakes that’s it’s basically official, but it being “experimental” means they can’t be mentioned in official docs, or included by default in the official installer. You have to edit a config file to enable flakes.
The worst part of this all, is that the Determinate Systems nix installer, only comes with flakes and no channels (old way) - and Eelco literally works for Determinate Systems. Despite all of this, flakes are still “experimental”.
I hope things change. Flakes are legitimately better, a minor addition in complexity, in exchange for making it easy to reuse code. And finally having unified documentation and tooling (if flakes become the main way) will probably be the best benefit.
I really hope this council moves flakes put of their “experimental” status. If so, then democracy has spoken: the users want flakes.
What stops companies from having a shell corporation use the code, and then that shell company rents “services” at a very low cost to a large corp?
I’m thinking something of the opposite if what Google does, where Alphabet (““located”” in Ireland) rents the Google logo to Google, allowing Google to say that their revenue is much less than it actually is.
That only applies to unstable distros. Stable distros, like debian, maintain their own versions of packages.
Debian in particular, only includes security patches and changes in their packages - no new features at all.* This means risk of breakage and incompatibilitu is very low, basically nil.
*exceot for certain packages which aren’t viable to maintain, like Firefox or other browsers.
I dunno, some of these are a pretty big deal, in particular:
Gitea repeatedly makes choices that leave Gitea admins exposed to known vulnerabilities during extended periods of time. For instance Gitea spent resources to undergo a SOC2 security audit for its SaaS offering while critical vulnerabilities demanded a new release. Advance notice of security releases is for customers only.
Gitea is developed on github, whereas forgejo is developed on and by codeberg, who use it as their main forge (also mentioned on that page). Someone dogfooding gives me more confidence in the software.
The comparison isn’t quite right because you can use git with any provider (Github, gitlab, etc), including multiple at once.
On the other hand, snap is hardcoded to only be able to use one store at a time, the snap store. To modify this behaviour, you would have to make changes to the snap client source code.
It’s more a EULA than an actual license. It prohibits a lot of stuff, and is basically source-available.
You agree not to create any product or service from any par of the Code from this Project, paid or free
There is also:
Sn1perSecurity LLC reserves the right to change the licensing terms at any time, without advance notice. Sn1perSecurity LLC reserves the right to terminate your license at any time.
So yeah. I decided to test it out anyways… but what I see… is not promising.
The two pacman commands are redundant. You only need to run pacman -Syu sn1per --noconfirm once. This also goes against docker best practice, as it creates two layers where only one would be necessary. In addition to that, best practice also includes deleting cache files, which isn’t done here. The final docker image is probably significantly larger than it needs to be.
It’s still building right now. I might edit this post with more info if it’s worth it. I really just want a command-line vulnerability scanner, and sn1per seems to offer that with greenbone/openvas as a backend.
I could modify the dockerfiles with something better, but I don’t know if I’m legally allowed to do so outside of their repo, and I don’t feel comfortable contributing to a repo that’s not FOSS.