Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)T

trevor (he/they)

@ trevor @lemmy.blahaj.zone

Posts
0
Comments
480
Joined
3 yr. ago

Hello, tone-policing genocide-defender and/or carnist 👋

Instead of being mad about words, maybe you should think about why the words bother you more than the injustice they describe.

Have a day!

  • April Project Goals Update

    Jump

  • I cannot wait for cargo-script to stabilize.

  • Deleted

    Read Elias Rodriguez’s Leaked Chats

    Jump

  • This is also true for most "Democratic" politicians. MAGA isn't unique in being genocidal scumfucks.

  • Mullvad Leta a privacy focus search engine

    Jump

  • Not really. IMO, the determining factor for this is how "sticky" a given service is.

    Leta is a public search engine that you don't have to pay for their VPN to use, and switching search engines is quite trivial, making this a very easy switch in the event that either service is unsatisfactory.

    That said, I have no idea why anyone would want Google search results in 2025 because their search engine is terrible, but more power to anyone that does.

  • Rust Coreutils 0.1 Released With Big Performance Gains - Can Match Or Exceed GNU Speed

    Jump

  • GPL is more freedom for users and developers. MIT is less freedom for users because it grants more "freedom" for some company to exploit the developer's labor by taking it to make something proprietary with it.

    If you want to use GPL code, pushover licenses are incorrect because they protect the user and developer from this nonsense.

  • Rust Coreutils 0.1 Released With Big Performance Gains - Can Match Or Exceed GNU Speed

    Jump

  • If the other projects are licensed with a GPL, there is no issue doing any of these things (except using them for proprietary purposes later), which is the point. If you licensed your project incorrectly, that isn't the GPL-licensed project's fault.

  • Rust Coreutils 0.1 Released With Big Performance Gains - Can Match Or Exceed GNU Speed

    Jump

  • Precisely. The Rust community should stop using pushover licenses.

  • Deleted

    Permanently Deleted

    Jump

  • I use vertical tabs because horizontal tabs use more screen in wide aspect ratios (16:9 or greater) and I want to optimize my screen usage for the actual content, rather than the tabs.

  • Passwords are okay, impulsive Internet isn't

    Jump

  • Actually yeah. You're right. Even better 😌

  • Passwords are okay, impulsive Internet isn't

    Jump

  • A lot of incorrect assumptions in this article. If you don't like the idea of a key exchange over passwords, I hope you use password auth when you SSH into things 😁

    The word passwordless is nonsense. In most cases, most passkey implementations, you need a PIN to unlock your private key to authenticate. PIN = password, except it's numbers only. Nonsense. Passkeys simply obfuscate the problem and move it somewhere else, most often into a PROPRIETARY key management tool. For example, Microsoft wants you to use THEIR authenticator app. Not just any app that adheres to the standard. Nope. This effectively means super-vendor-lock-in. Absolute nonsense.

    You can argue that the term "password less" is nonsense, but there is literally nothing about the spec that prevents you from using passkeys as they were designed: with hardware keys that support the open FIDO2 authentication protocol. Yes, you still need a second factor to verify the authentication attempt (via a PIN), but unless you're mailing that key to hackers, the private key generated by your SoloKey, NitroKey, or another open source hardware key, is more secure than any password ever will be.

    Passkeys usually require a phone - this is a single point of failure, and one that gives the big companies extra control over you. Phone, number, SIM, and so forth. A beautiful bevy of data. The whole idea of actually having to use your phone as an identity vector is horrible.

    Phones support storing passkeys. Phones also support storing passwords. In no way does this mean you must use them for this. You can either use hardware keys, or you can use your favorite open source password manager to store passkeys where you should already be storing your passwords anyway.

    You need "biometrics" to supposedly prove you're you to unlock your private key. Biometrics are a form of password, except you can't replace it, and it also gives yet more of your personal data to the big companies. More nonsense.

    This is literally a direct contradiction of what the author said in their first bullet point. Use a PIN if you don't like using biometric auth.

    The implementation of passkeys is fragmented, vendor-specific, and complicated. Only diehards who love technology can use this. The same kind of people who were "all in" when IoT/cloud crap came out, and now they see their smart homes slowly go offline as big vendors almost arbitrarily cut support for old gadgets and effectively kill products. Because cloud.

    Most of this is actually a fair critique. The FIDO Alliance is still working on the spec, and I think they should require any implementation of passkeys to follow the spec to a tee without adding any kind of nonstandard bullshit to their authentication.

    However, most advancements in tech begin with only appealing to enthusiasts and later become adopted by wider audiences. It doesn't make them bad that they aren't immediately popular with everyone.

    Passkeys only solve one use case - phishing where the user inputs their password and MFA into a fake site.

    I'm glad the author can at least recognize that there's at least one thing that passkeys solve that passwords can't. But it's not the only thing. When you enter a password on a site, you're hoping like hell that the service you're using hashes it and hashes it properly. When you authenticate with passkeys, you're sending the site a public key. This key will have way more entropy than any password will, so anyone trying to crack a hashed public key is in for a long, miserable time (obviously not impossible though). But even if they wasted their time doing that, it's a public key. Who cares?

    Any service you use passkeys with instead of passwords won't put you in another leaked password database. The public key just needs to be invalidated and you can move on with your life.

  • Palm Springs Bombing Kills 1 and Damages Fertility Clinic, Mayor Says

    Jump

  • What is the opposite of thoughts and prayers? Apathy and ill will?

    Thoughts and prayers. It has the exact same effect as apathy and ill will.

  • Introducing oniux: Kernel-level Tor isolation for any Linux app

    Jump

  • Other than the example uses provided in the article, does anyone have any interesting ideas for how this could be used? The RUST_LOG=debug one looks like it'll be particularly useful as an easy way to see what network requests a given binary might be making.

  • Deleted

    Permanently Deleted

    Jump

  • Gross.

  • New week, new feature - Proton Docs Homescreen

    Jump

  • They mean light mode. I think "flashbang mode" is pretty apt though.

  • Flattening Rust's Learning Curve | corrode Rust Consulting

    Jump

  • I just use Arc::clone() now that I know I can just throw the problematic data types on the heap easily. I'm sure there are "better" ways to do it, but ¯\_(ツ)_/¯

  • Flattening Rust's Learning Curve | corrode Rust Consulting

    Jump

  • As someone whose only other language was very beginner-level Python before learning Rust, the part about not treating the borrow checker as an adversary, but as a companion, mirrors the point at which I began rapidly improving.

    I like to say that the Rust compiler rules are like having a senior engineer over your shoulders to help you avoid writing (certain kinds of) bad code.

    There are still times when the borrow checker becomes my adversary (like needing to share data in threads), and it is painful, but they become less frequent over time.

  • Snap bad

    Jump

  • My issue with snaps is also the power that Canonical has to fuck you over one day, because of the centralization that you mentioned, but also that their shitty fucking packaging format sucks ass and breaks everything but the most basic of apps. I've wasted hours trying to help people with their broken applications that were hijacked when they typed apt install whatever and "whatever" was actually a fucking broken snap package.

    Flatpaks and AppImages actually do the fucking things they're supposed to. Snaps don't, and Canonical is pulling a Microsoft by hijacking your package manager.

    Also, Snap sandboxing only works with AppArmor, so if you were hoping that all the breakage was worthwhile because you get sandboxing, you don't if you're on anything but a handful of distros 🙂

  • De-radicalizing parents' algorithms?

    Jump

  • Does anyone know if there's a more up-to-date blocklist? This is great, but it's 4-5 years old.

  • Forbidden Fish

    Jump

  • Friendly Interactive SHell

  • Btw, I use Arch (via EndeavourOS*)

    Jump

  • Fuck that. The Linux gate is wide open! Anyone that wants to use Linux, come on in!

    And for your own sake: use anything but Ubuntu and their buggy Snaps.