• 0 Posts
  • 34 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle




  • whats_all_this_then@lemmy.worldtoLinux@lemmy.worldDo you use aliases?
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    5 months ago

    Oh boy, my time to shine:

    • mkd - Create directory and immediately cd into it
    • dei - docker exec -i
    • dps - docker ps
    • mdocker - Switch to minikube’s docker context
    • n - nvim
    • n. - nvim .

    Node package managers

    Exampes use pnpm but I have them for yarn, npm, and bun too

    • pi - pnpm install
    • pd - pnpm run dev

    fzf stuff

    • sdh - Search home directory (directories, recursive)

    Meme

    • fuckyou - git push --force
    • nano - nvim

    Misc

    createpgdb - Create a postgres db on the given container with the given name

    Usage: createpgdb "postgres container" "db name"

    I have similar ones for dropdb and pg_dump. Here’s the command:

    f() { local __user; if [ -z $3 ]; then __user=postgres; else __user=$3; fi; docker exec -i $1 createdb -U $__user $2; unset -f f; }; f'
    

  • I’m no cryptography expert but I don’t see how they could implement this with true anonymity or without it being spoofed in other browsers. There is currently no way to know with absolute certainty what browser/client web traffic is actually coming from and game anti-cheat devs will probably tell you it’s a nightmare of a problem.

    The way I see this working is making it a Mozilla account thing and not a Firefox thing through some sort of stateless cross-origin cookie the sites agree to support. But then, you’re giving up at least some privacy because even if the sites you visit don’t know who you are, you’ll still have to trust that Mozilla is logging anonymized visit counts and that some CEO 5 years from now isn’t going to change that for a quick buck.

    Maybe I’m just out of my depth here and someone’s gonna correct me (please do if I’m wrong).












  • I’ve had to debug a PDF viewer on a site once. Getting that to work across multiple versions of multiple browsers was a nightmare and I never managed to figure it out. Latest versions are mostly fine (except for mobile safari), but even 1yo versions of browsers are just broken.

    Maybe I’m missing something, but it got bad enough that one of the “potential solutions” I was considering involved figuring out how to compile a C based pdf renderer thingy into WASM and embedding it in the app.

    This was about 7 months ago.

    I agree though, add to cart should NOT behave differently across browsers in 2024.