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/)JA
Posts
2
Comments
123
Joined
2 yr. ago

  • Sure it's terrifying, but you can start a sparky plasma show in a resilient enough container and keep it going for hours and the microwave won't break. (except maybe overheat.) The microwave will be fine as long as the arcs don't reach the waveguide cover. (which would risk burning/shorting the magnetron.)

    I have done the microwave grape plasma trick myself and started an arc in a microwave. The current between the two objects goes through a very narrow point, which is enough vaporize the contact point to plasma. This then can grow as the microwave continues to pump more energy into the spark.

  • hardmode: I did a fresh install on a HDD that is on verge of being dead. Every-time this thing boots it's a miracle. Somehow dd blanking the disk, plenty of smartctl offline disk surface scans and finally putting btrfs with data in DUP profile resurrected the HDD. I have run btrfs scrub daily or else the os install may bitrot and well.. expire. :D

    Edit: Todays catch, I was too late and now I have fix 3 files:

     
        
    Error summary:    read=112
      Corrected:      109
      Uncorrectable:  3
      Unverified:     0
    
      
  • No mention of KDevelop? ;__;

    I like it because it is the pretty much only FOSS graphical IDE where the edit-compile-debug cycle works. I'm been using it for last 10y for C/C++/Python, and it recently gained LSP support. (ported from Kate)

  • The \EFI\BOOT\BOOTX64.EFI is the only file the UEFI standard says it is required automatically lookup from an EFI system partition. There can many EFI partitions but the UEFI is only required to find a single file per such a partition.

    efibootmgr -u can show all bios auto created boot entries (don't touch those, the bios can/will reset them at whim) and the manually created entries that don't launch a BOOTX64.EFI named file.

  • I intended this an sarcastic example; I think it's worse than putting the main outside of the branch because of the extra indent-level. It does have an upside that the main() doesn't exist if you try import this as an module.

  • Btw, ld.so is a symlink to ld-linux-x86-64.so.2 at least on my system. It is an statically linked executable. The ld.so is, in simpler words, an interpreter for the ELF format and you can run it:

     
        
    ld.so --help
    
    
      

    Entry point address: 0x1d780

    Which seems to be contained in the only executable section segment of ld.so

     
        
    LOAD 0x0000000000001000 0x0000000000001000 0x0000000000001000
         0x0000000000028bb5 0x0000000000028bb5  R E    0x1000
    
    
      

    Edit: My understanding of this quite shallow; the above is a segment that in this case contains the entirety of the .text section.

  • I would put my code in a def main(), so that the local names don't escape into the module scope:

     
        
    if __name__ == '__main__':
        def main():
            print('/s')
        main()
    
    
      

    (I didn't see this one yet here.)

  • True Arch: you write the image to the usb stick yourself, boot it on bare hardware, and don't use archinstall. This is the minimum requirement BTW. If you use archinstall you can only use "btw" in lowercase. /s

  • I'll just comment about one thing that keeps popping up in the discussions: grid-level storage. There is no such thing yet really that would last a full day cycle, and the 100MW or so units we are building are mostly for frequency stabilization and for buying enough time to turn on a base-load plant when the renewables drop out. I'm not arguing against storage - it is absolutely needed.

    The problem is the scale, which people don't seem to get. Largest amount of energy we can currently repeatedly store and release is with pumped hydro, and the locations where this is possible are few and far between. Once the batteries reach this level-of-capacity, then we have a possibility to use them as grid-level storage that lasts a few days instead of hours.

  • Send it through the earth, you can reduce it theoretically to 42.5ms

    This isn't as ridiculous as it sounds and you just need a neutrino-beam... which has a horrible bandwidth (of 0.1 bits/s) plus the ridiculous upfront cost of running two particle-accelerators for a full-duplex link. (Google it up, this exists.)

  • Programmer Humor @programming.dev

    Removing API dependency from a plugin.

    Lemmy Shitpost @lemmy.world

    Login in from /dev/null