

It’s the directory that needs to be writable to delete files, not the file itself.
Although the immutable bit (if that’s what you’re talking about - I thought you meant unsetting the write bit) might change that, I’m not sure.
Hello there!
I’m also @savvywolf@furry.engineer , and I have a website at https://www.savagewolf.org/ .
He/They
It’s the directory that needs to be writable to delete files, not the file itself.
Although the immutable bit (if that’s what you’re talking about - I thought you meant unsetting the write bit) might change that, I’m not sure.
The home directory would need to be immutable, not bashrc.
I don’t think that actually works; the attacker could just remove .bashrc and create a new file with the same name.
In an ideal world, a search engine will point to this thread, where the answer is the topvoted comment.
With the death of Stackoverflow and Reddit, hopefully Lemmy can fill the void of an information archive. :P
What improvements are you thinking of? I can see that reasoning with something like the Linux kernel where there’s a lot of complex and integrated code, but ultimately individual coreutils commands are really simple. There’s very little you can do to extend something like ls
… And if you do, you can just make your own superls
command and not have to deal with any licensing restrictions.
With regards to AGPL vs GPL, none of the coreutils programs have network connectivity, so I’m not sure what the network requirement actually adds?
getting rid of the gpl is the motivation behind e.g. companies sponsoring clang/llvm so hard right now.
Is it? As I understand it, LLVM is much easier to work with than GCC, especially given their LLVM IR and passes frameworks.
here, take my stuff and don’t contribute anything back, that’s totally fine
I mean, yeah? They are probably fine with that and think that software should be distributed without restrictions. You may not agree with it, but it’s their choice. Not really stealing if they give it away willingly.
I cannot fathom any FOSS project not using the AGPL anymore.
I mean, most of them that want to use a GPL-like license use the GPL or LGPL rather than the AGPL. :P
why are developers even agreeing to this?
Are they? Last I checked this wasn’t as much of a plan as much of it was just a developer thinking out loud. And even if it was a real plan, developers should continue doing what they should be doing anyway: Write their scripts without any GNU/uutils/whatever-microsoft-calls-their-evil-uutils-fork extensions. Then their scripts could run across all platforms, including GNU, uutils, FreeBSD and BusyBox.
At any rate, if Microsoft really wanted to make their own coreutils fork (if they haven’t already), they’re not really that complicated tools. They could devote like maybe a year of engineering time and get it pretty much compatible.
Yep, borgmatic encrypts it before it sends data to the server.
Was anything else installed on the 21st? Might have been pulled down as a dependency of something.
I recently bought a storagebox from Hatzner and set up my server to run borgmatic every day to backup to it.
I’ve also discovered that Pika Backup works really well as a “read only” graphical browser for borg repos.
Firefox is licenced under a copyleft license. Mozilla can’t stop distros packaging it even if they wanted to.
They’d need to replace the branding, but that’s not a big deal.
I’m a Firefox user and I’m not really that bothered about this tos changes. If they do mess things up I’ll probably just switch to some fork that doesn’t do the fuckery.
Wouldn’t be surprised if Mint packages Firefox with it (whatever “it” is) disabled, since they build Thunderbird without telemetry.
I have a custom theme for Cinnamon/GTK… But they recently updated it and the new default theme doesn’t actually look that bad… But using the default theme will make me a sheep. ;_;
All three are web based frontends for git repositories; you use git to send and receive code to/from them for storage and sharing. They all also provide other things useful to developers such as issue tracking, wikis and such. They are different products that fulfill the same role.
what software does github.com use?
It’s all proprietary software (presumably) written in-house. We don’t have access to it.
whats the difference between them (pros/cons)?
Github:
Pro: Wider reach, everyone knows about Github.
Con: Proprietary; your code is hosted based on the whims of Microsoft.
Forgejo:
Pro: Open source, selfhostable. There’s a big instance on https://codeberg.org/ which a lot of open source projects are starting to move to.
Con: It’s smaller and not as well known as Github. In theory it may also lack features, but I’ve not seen any that have gotten in my way.
Gitlab:
Pro: It’s… I guess in second place in terms of popularity? It’s also selfhostable.
Con: It’s one of those open source projects with paid closed source features, so not really appealing to either group. It’s also had questionable management decisions recently.
what about self-hosting? Possibilities/Preferences?
If you want to selfhost a git server, I’d recommend Forgejo; it seems to be the most friendly towards the open source and selfhosting communities.
I know people have been investing a lot of work into getting Nvidia into a state where it Just Works, but if you don’t need any fancy Nvidia features and are starting from scratch I’d honestly just recommend getting an AMD card just so you don’t have to worry about it.
What games are you thinking of running and what resolution/frequency monitor do you have/want?
Mint explicitly goes out of its way to disable snap in favour of flatpaks.
https://linuxmint-user-guide.readthedocs.io/en/latest/snap.html
Nobody seems to be putting the effort into making ATProto federated apps, sadly. The main people who would do it are also the type to stubbornly stick with ActivityPub.
I like to see companies design their software such that their main financial incentives are tied to the quality of their product. This usually involves being open source; if someone can fork it, your paywalled version better have extra features that open source people can’t make easily. I also like to see them trying to avoid vendor lockin; if it’s easy for you to switch, then they need to actively work on not letting that happen.
For example, Bluesky. They have an open protocol and (I think) you can easily transfer data between instances. If they start fucking people around, you can just jump to another ATProto app.
For Kagi, the only thing you’re paying for is search… So if they fuck that up, you can just crawl back to DuckDuckGo.
Obsidian is an interesting case. It’s not open source, but the files it works on are just markdown. If they go totally wild, I can just easily switch to VSCodium to edit my files.
As a general rule, AI can only really perform easy monotonous tasks. Anything that requires creativity or intuition is generally not doable with AI.
The most a GPT AI could do is steal some instructions from some blog somewhere on how to configure a kernel or install some distro, then generate a list of packages.
For my main desktop I use Mint because it just works, widely supported and Cinnamon is good (sadly no Wayland yet. ;_;). I also use Home-manager for my configuration because it allows me to easily just specify my config as a set of files I can check into git.
For my server, I use NixOS, because having all my configuration in a few text files is very nice to get an overview of what my server is doing.