Also Black here!
(My keyboard doesn't have emotes, but pretend this is the black hand waving hi)
Edit: ππΎ
Pip in a venv doesn't get you non python tools.
Conda also has venvs, for seperate environments for stuff as well.
This reminds me of kasmweb, but fully open source.
No way to protect emails, google chats, or many other things AFAIK. Yeah, I hate it too.
Why is SSPL not considered FOSS while other restrictive licenses like AGPL and GPL v3 are?
So I have an answer for this. Basically all of the entities listed that relicensed their projects to the SSPL, also relicensed their projects using the dual licensing scheme, including one proprietary license. That's important later.
The SSPL's intent is probably that the deployment framework used to open source this software must be open sourced. I like this intent, and I would consider it Free/Libre Software, but it should be noted that another license, the open watcom license, which requires you to open source software if you simply deploy it, is not considered Free Software by the FSF. I don't really understand this decision. I don't count "must share source code used" as a restriction on usage cases. It seems that the FSF only cares about user freedom, whoever is using the software, and views being forced to open source code only used privately as a restriction.
Now, IANAL... but the SSPL's lettering is problematic. What is part of the deployment system? If I deploy software on Windows, am I forced to open source windows? If I deploy it on a server with intel management engine, am I forced to open source that? Due to the way it is worded, the SSPL is unusable.
And a dual license, one proprietary and one unusable means only one license β proprietary. There's actually a possibility that this is intentional, and that the intent of the SSPL was never to be usable, but rather so that these companies could pretend they are still Open Source while going fully proprietary.
But, for the sake of discussion, let's assume the SSPL's intent was benevolent but misguided, and that it's intent was not to be unusable, but rather to force companies to open source deployment platforms.
Of course, the OSI went and wrote an article about how the SSPL is not an open source license but that's all BS. All you need to do is take a look at who sponsors the OSI (Amazon, Google, other big SAAS providers) to realize that the OSI is just protecting their corporate interests, who are terrified of an SSPL license that actually works, so they seek to misrepresent the intent of the SSPL license as too restrictive for Open Source β which is false. Being forced to open source your deployment platform still allows you to use the code in any way you desire β you just have to open source your deployment platform.
Is there some hypothetical lesser version of SSPL that still captures the essence of it while still being more restrictive than AGPL that would prevent exploitation by SaaS providers?
AGPL. There's also Open Watcom, but it's not considered a Free Software license by the FSF, meaning software written under that wouldn't be included in any major Linux distros.
I think in theory you could make an SSPL that works. But SSPL ain't it.
Of course, there are problems with designing an SSPL that works, of course. Like, if you make it so that you don't have to open source proprietary code by other vendors, then what if companies split themselves up and one company makes and "sells" the proprietary programs to another.
I just use termux + the simple http server built into python
You could do open source engine, proprietary assets. Like the original doom 1, 2, and 3. You can get the engine for free, but have to pay for the art assets.
https://en.m.wikipedia.org/wiki/List_of_open-source_video_games#Open-source_games_with_non-free_data
Fun fact: you don't need to add the nixpkgs channel for the determinate systems installer, even when using channel commands or other things since it adds an option to your nix.conf to reference the nix flake for nixpkgs.
I don't know how to update this flake though.
Zotero is a citation manager, with a firefox extension to save an article (but really, a tab) with one click.
It also has fulltext search. You can search snapshots of everything you save.
"But I can't save all my tabs at once"
(There are some solutions, but nothIng official)
Save as you go. Computers simply don't have enough ram for 2000 tabs.
Anyway, it also seems to be able to run javascript plugins, and I saw you have some experience with that.
It also has support for folders, so you can organize it a bit better than tabs work for that.
There's also the needy users that create tickets for every prompt, dialog, message, delay.... Pretty much anything that could happen at all ever, whether it affects their ability to do their work or not.''
This could be weaponized incompetence. "Oh I keep having issues with my computer that interfere with my work, so I can't work and IT is incompetent and can't help me, look at all these tickets and how long IT takes. I just can't get any work done!"
You could say the same thing about sudo. Sudo's codebase is massive, compared to alternatives like doas, but it comes with many features doas does not have, like being able to ask a remote LDAP server if a user will be able to escalate.
I find it absurd that we have just simply accepted the idea of a setuid binary with built in networking code, as our primary admin escalation tool. 100,000+ lines of C code, code that has had multiple buffer overflow exploits*, in a setuid binary, just for temporary admin privileges. Does that seem necessary to you?
Polkit provides an alternative to that. If you don't need the features, then fine, you don't have to use run0 β but then you can't use sudo without being a hypocrite. No longer do I have to have rely on a setuid binary that tries to do everything in one program when I really need sudo's features, instead polkit handles authentication (including asking remote resources if an action is okay), and run0 handles actual escalation.
In another comment in this thread, you mention sudo being lightweight β which is outright false. Compared to doas or su, it's extremely heavyweight, and with that complexity comes more risk of vulnerabilities. You also mention pkexec, for executing with polkit, but pkexec is also setuid, and has many of the same pitfalls.
*Buffer overflow exploits in sudo:
Wikibooks, wikiversity, for learning resources. There are also other wikimedia projects like wikivoyage for travel resources, or wikinews which you already put.
Libretexts for learning resources.