Skip Navigation

Redjard

@ Redjard @lemmy.dbzer0.com

Posts
3
Comments
222
Joined
3 yr. ago

  • Hair rule

    Jump

  • It's all mine!

    Jump

  • You'd either need to use microwaves to get the heat in deeper, or go with a lower temperature and longer time while somehow preventing dryout, maybe steaming it somewhat.

  • Deleted

    Google Play Store begins enforcing new age verification checks

    Jump

  • Do they work with split apps yet?

  • How stupidly easy file recovery is on Linux

    Jump

  • I could do a script if I knew what I was gonna do ahead of time, or would write one later if I was gonna do it more often.

    A variable in the shell is fine, but I still have to skip over it to change the first command, it still breaks up the flow a bit more than not having that "$file" in there at all.Also if I interrupt the work (or in this case have to let it run for a while), or if I wanna share this with others for whatever reason, I don't have to hunt for the variable definition, and don't run any risk of fetching the wrong one if I changed it. Getting by without variables makes the command self-contained.

    And it still maintains the flow of left to right, it's simply easier to take the tiny well-known packet of cat file and from that point pipe the information ever rightwards, than to see a tail, then read the options, and only then see the far more important start of where the information comes from, to the continue on with the next processing step.Any procedural language is always as left to right as possible.

    If you really want to avoid the cat, I have yet another different option for you:< /dev/nvme0n1 strings | grep -n "text I remember"< /dev/nvme0n1 tail -c -100000000000 | head -c 50000000000 | strings | grep -n "text I remember"< /dev/nvme0n1 tail -c -123456789012 | head -c 3000 > filerec

    This ofc you can again extend with ${infile} and ${recfile} if the context makes it appropriate.

  • How stupidly easy file recovery is on Linux

    Jump

  • It makes the command easier to edit here. Put the various forms across my use next to each other and it becomes apparent:

    cat /dev/nvme0n1 | strings | grep -n "text I remember"cat /dev/nvme0n1 | tail -c -100000000000 | head -c 50000000000 | strings | grep -n "text I remember"cat /dev/nvme0n1 | tail -c -123456789012 | head -c 3000 > filerec

    compare that to

    strings /dev/nvme0n1 | grep -n "text I remember"tail /dev/nvme0n1 -c -100000000000 | head -c 50000000000 | strings | grep -n "text I remember"tail /dev/nvme0n1 -c -123456789012 | head -c 3000 > filerec

    where I have to weave the long and visually distracting partition name between the active parts of the command.The cat here is a result of experiencing what happens when not using it.

    Worse, some commands take input file arguments in weird ways or only allow them after the options, so when taking that into account the generic style people use becomes

    strings /dev/nvme0n1 | grep -n "text I remember"tail -c -100000000000 /dev/nvme0n1 | head -c 50000000000 | strings | grep -n "text I remember"tail -c -123456789012 /dev/nvme0n1 | head -c 3000 > filerec

    This is what I'd expect to run across in the wild, and also for example what ai spits out when asked how to do this. You'll take my stylistic cats over my dead body

  • How stupidly easy file recovery is on Linux

    Jump

  • Oh right I misunderstood.I didn't do that because I was planning to switch out strings in that line. First inserting the tail and head before it to hone in on the position, then removing it entirely to not delete "non-string" parts of my file like empty newlines.

    cat /dev/nvme0n1 | strings | grep -n "text I remember"cat /dev/nvme0n1 | tail -c -100000000000 | head -c 50000000000 | strings | grep -n "text I remember"cat /dev/nvme0n1 | tail -c -123456789012 | head -c 3000 > filerec

    This would be the loose chain of commands I went through, editing one into the next. It's nice keeping the "constants" like the drive device that are hard to type static. That way mentally for me the command starts only after the first pipe.

  • How stupidly easy file recovery is on Linux

    Jump

  • I don't like to use < in combination with pipes, I find it harder to read. One is left to right the other right to left, and < is also just plain weird in its specifics.cat is a stylistic choice avoiding needless notational complexity

  • How stupidly easy file recovery is on Linux

    Jump

  • Last time I deleted a plaintext file I just grepped for it.cat /dev/nvme0n1 | strings | grep -n "text I remember"

    Had to hone in on the location with head -c and tail -c after I found it, then simply did a cat /dev/nvme0n1 | tail -c -123456789012 | head -c 3000 > filerec and trimmed the last filesystem garbage from the ends manually.

  • As Microsoft Forces Users to Ditch Windows 10, It Announces That It’s Also Turning Windows 11 into an AI-Controlled Monstrosity

    Jump

  • Wine can actually beat native in latency, since it's a pretty thin translation layer and windows is ... windows.I'd give it a shot just in case.

  • Leak From the Sky: It Turns Out a Lot of Satellite Data Is Unencrypted

    Jump

  • Steadily improving. I set up my webserver with ech which is the next step, hiding even the domain. A solid chunk of the internet uses cloudflare as an intermediary, which also has ech and only leaves "someone connected to some cloudflare page at this time for that amount of data".

    As more places roll out deep package inspection, I'm sure in due time more randomization for package sizes will follow, making even the amount of data uncertain.

    Most web metadata is at the http layer anyway and has always been hidden by https.

  • Pithon

    Jump

  • Oh my I must have recited it wrong from memory, my bad

  • Pithon

    Jump

  • Yep, exact copy of the first 35 lines from the 100,000 Digits of Pi website, the spaces are still in

  • Deleted

    Permanently Deleted

    Jump

  • There is also an unreadable (due to compression) watermark under to it, how would I know it is actually an artists signature?I assume then it is, and of an artist you recognize to be credible?

  • Vibecoding is the future

    Jump

  • Oh you want the code not rendered into html!Drops the code in javascript when it is received from the backend.

  • Deleted

    Permanently Deleted

    Jump

  • Ok but has this actually been proposed by an archeologist in accordance with the evidence we have? Is this a possible recreation or has it in effect already been disproven with what we know?

    There's a big difference between "in 2024 an archeologist asked an artist to paint this" and "someone on ticktock ai generated this".

  • Deleted

    Permanently Deleted

    Jump

  • That graph does contain bees among wasps.

    To be specific, bees are a "Cladistically included but traditionally excluded taxa" of wasps, since they are within Apocrita.

    The common-language definition of wasp is literally "A member of Apocrita ... except bees (and ants)".It's the same situation as saying a chicken is a dinosaur, and why the field often uses "non-avian dinosaurs" instead for clarity.

    This wikipedia diagram from the Aculeata article is a bit more concise:

    Take now for example Stephanoidea, "a superfamily of parasitic wasps within the Apocrita". Clearly wasps, yet equally closely related to yellow-jackets and honey-bees.

    Edit: mixed up Aculeata and Aulacidae. Edit2:

    If you go further into Apoidae, even there you still find plenty more "clearly wasp" type species:

    Take Sphecidae:

    Or Philanthidae:

    All on the same level as actual bees (Anthophila).

    I think also in terms of vibes it feels right to call bees a subset of wasps.

  • Deleted

    Permanently Deleted

    Jump

  • Bees are technically a kind of wasp.

  • Mirror spelling mistake

    Jump

  • Parnets

  • Got Em!

    Jump

  • Export the apk via adb and then install it from the file on future devices?