I mean no harm.

  • 2 Posts
  • 109 Comments
Joined 1 year ago
cake
Cake day: July 4th, 2023

help-circle






  • 100% Nope: A episode from supernatural, where ghouls half way succeed to eat Sam. (I consider it as the most gruesome horror I have ever seen, and I don’t think I have the stomach to see it ever again. The blood draining is a … no.)

    Yellow brick road on otherhand hits the weird places spot of SCP, which I can’t get enough. (not horror really, but still)







  • Python is just a pile of dicts/hashtables under the hood. Even the basic int type is actually a dict of method names:

    x = 1
    print(dir(x))
    ['__abs__', '__add__', '__and__', '__bool__', '__ceil__', '__class__', '__delattr__', '__dir__', ... ]
    

    PS: I will never get away from the fact that user-space memory addresses are also basically keys into the page table, so it is hashtables all the way down - you cannot escape them.





  • permanently attached USB SSDs are supposed to be mounted

    Just mount them somewhere under / device, so if a disk/mount fails the mounts depended on the path can´t also fail.

    I keep my permanent mounts at /media/ and I have a udev rule, that all auto mounted media goes there, so /mnt stays empty. A funny case is that my projects BTRFS sub-volume also is mounted this way, although it is technically on the same device.


  • For example, the new .config directory in the home directory.

    I hope slowly but surely no program will ever dump its config(s) as ~/.xyz.conf (or even worse in a program specific ~/.thisapp/; The ~/.config/ scheme works as long as the programs don’t repeat the bad way of dumping files as ~/.config/thisconfig.txt. (I’m looking at you kde folks…) A unique dir in .config directory should be mandatory.

    If I ever need to shed some cruft accumulated over the years in ~/.config/ this would make it a lot easier.


  • They could be very well using the earth’s orbit around the sun to get better resolution - two data points from opposite sides of the orbit. What I know is that the largest “virtual” radiotelescope is literally the size of earth. The data points are synced with atomic clocks (or better), and a container of harddrives gets shipped into a datacenter to be ingested. Thats hundreds of streams (one per antenna) of data to be just synced up, before the actual analysis even can begin. (I’m just guessing after this) At this point, you have those hundreds (basically .wav files) lined up at timepoints they were sampled (one sample, one timepoint column). So row by row, so you can begin to sort out signal phase differences between the source rows.

    I.e to put it shortly: an image is not taken, it is inferred and computed. Not that you even could in the first place, it’s a blackhole after all.


  • I have begun to see that YT is being hostile to adblocker users - and this worries me. I assume YT is already probing the clients to see which are circumveting the ads.

    I had an (let’s say unconventional) idea at one point: an add-on which only purpose is to show the YT ads in the background which uBO blocked. All of the blocked ads would be played (eventually) - except that the user can just ignore this happening in background and wouldn’t be actually seeing the ads. I.e. the browser would just move playing the ads into a background container not visible to the user.


  • Jokes on merge… when a rebase editing goes wrong after +15 commits and six hours, and git hits you with a leadpipe: “do it. Do it again, or reassemble your branch from the reflog.” I.e. you commited a change very early, went over bunch of commits resolving/fixing/improving them and at middle way forget if you should commit --amend or rebase --continue to move forward. Choose wrong, and two large change-sets get irreversilbly squashed together (that absolutely shouldn’t), with no way to undo. Cheers. 👍