Hello there!

I’m also @savvywolf@furry.engineer , and I have a website at https://www.savagewolf.org/ .

He/They

  • 1 Post
  • 288 Comments
Joined 2 years ago
cake
Cake day: June 27th, 2023

help-circle






  • If you’re itching to test Orion for Linux, you’ll have to wait. No public builds are available yet, and when testing versions do arrive, they’ll initially be restricted to paid Orion+ and Kagi subscribers.

    If reading this has you itching to try it out, you’ll have to wait. No public builds of Orion’s Linux port are available for testing, and when available, the plan is to only give paid Orion+ and Kagi subscribers first dibs – crushing, but there is a reason for it.

    Seems they didn’t give it a proofread before publishing. :p




  • So the narrative is that Rust somehow, through being released only through one distro, is going to use that influence to force incompatible changes into other codebases. Despite the fact that any change to shell scripts that isn’t posix compatible brings opinionated people out the woodwork. And then they’re going to pivot to releasing a proprietary version of coreutils that somehow has killer features that the open source version lacks despite coreutils being 30 years old.

    Also the guy pushing for it once worked for a government so that means he can’t be trusted ever again.

    It’s just a fucking bunch of programs that act as thin wrappers around C functions. There’s nothing novel that needs protecting or is hard to implement.


  • Is it likely? No. Is it possible? Yes.

    If you want to make absolutely sure that Windows can’t spy on anything, you’ll need to physically remove the storage device containing Linux when booting.

    A more practical but slightly less secure approach is to enable full disk encryption on Linux. Then, if Windows does decide to get sneaky it’ll only see random data.

    This doesn’t prevent hostile code such as ransomware from destroying the data though. For that, you need to have good backup hygene.

    A good backup system is to have automatic daily backups to some online cloud storage provider, and weekly or monthly backups to a physical device you keep disconnected and safe.









  • Skipped to the “ugly” part of the article and I kind of agree with the language being hard?

    I think a bigger problem is that it’s hard to find “best practices” because information is just scattered everywhere and search engines are terrible.

    Like, the language itself is fairly simple and the tutorial is good. But it’s a struggle when it comes to doing things like “how do I change the source of a package”, “how do I compose two modules together” and “how do I add a repo to a flake so it’s visible in my config”. Most of this information comes from random discourse threads where the responder assumes you have a working knowledge of the part of the codebase they’re taking about.