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/)V
Posts
1
Comments
105
Joined
3 yr. ago

  • just to give you the term to search for, these types of applications are called snippet managers. for example, https://snibox.github.io/

    there's a ton of them around. I don't have a particular one that I recommend, since it's not something I use in my workflow.

  • grep -r exists and is even more faster and doesn't require passing around file names.

     
        
    grep -r --include='*.txt' 'somename' .
    
      
  • Better than that, git config supports conditional includes, based on a repo URL or path on disk. So you can have a gitconfig per organization or whatever, which specifies an sshCommand and thus an ssh key.

  • (obligatory I'm not a network surgeon this is likely not perfectly correct)

    The article mentions network interfaces, DHCP and gateways so real quick: a network interface usually represents a physical connection to a network, like an Ethernet port or a WiFi card. DHCP is a protocol that auto configured network routes and addresses once a physical connection is established, like when you jack in via an ethernet cable, it tells you the IP address you should go by, the range of IP address on the network you've connected to, where you can resolve domain names to IP addresses. It also tells you the address of a default gateway to route traffic to, if you're trying to reach something outside of this network.

    You can have more than one set of this configuration. Your wired network might tell you that your an address is 10.0.0.34, anything that starts with 10.0.0. is local, and to talk to 10.0.0.254 if you're trying to get to anything else. If at the same time you also connect to a wireless network, that might tell you that your address is 192.168.0.69, 192.168.0.* is your local network, and 192.168.0.254 is your gateway out. Now your computer wants to talk to 4.2.2.2. Should it use the wireless interface and go via 192.168.0.254? or the wired one and use 10.0.0.254? Your os has a routing table that includes both of those routes, and based on the precedence of the entries in it, it'll pick one.

    VPN software usually works by creating a network interface on your computer, similar to an interface to a WiFi card, but virtual. It then asks the OS to route all network traffic, through the new interface it created. Except of course traffic from the VPN software, because that still needs to get out to the VPN provider (let's say, at 1.3.3.7) via real Internet.

    So if you're following along at home, your routing table at this point might look like this:

    • traffic to 1.3.3.7 should go to 10.0.0.254 via the wired interface
    • all traffic should go to the VPN interface
    • traffic to 10.0.0.* should go to the wired interface
    • all traffic should go to 10.0.0.254 via the wired interface
    • traffic to 192.168.0.* should go to the wireless interface
    • all traffic should go to 192.168.0.254 via the wireless interface

    whenever your os wants to send network packets, it'll go down this list of rules until one applies. With that VPN turned on, most of the time, only those two first rules will ever apply.

    If I'm reading the article correctly, what this attack does, is run a DHCP server, that when handing out routing rules, will send one with a flag that causes, for example, the last two rules to be placed at the top of the list instead of the bottom. Your VPN will still be on, the configuration it's requested the OS to make would still be in place, and yet all your traffic will be routed out to this insecure wireless network that's somehow set itself as the priority route over anything else.

  • The password to my password manager: a few randomly chosen words that will definitely just sound like nonsense dementia-talk probably.

  • Geocaching is free and usually lots of fun in cities. It's like a big database of dead drops - people hide small containers with pieces of paper to sign, and post their GPS coordinates online. Frequently they're hidden near points if interest, as well so you might find some cool shops or bars as a side effect.

  • That's the other one. The Rabbit thing is $200, which, not that I would buy one, is not too unreasonable for an AI tamagotchi

  • yep. they're still here. they got smaller, and we call them "tracking pixels" now.

    it's just an image, which, server side, you can count the number of times it got loaded. easy to embed and no js required.

  • That's interesting, okay. Is svn doing compression of those binaries for you?

    Not to say "you're holding it wrong", but I'm curious about your workflow here. You clone these binaries every time you come back to a project?

  • I don't get it, who in their right mind hosts development stuff on a Windows clunker?

    Same question, but Subversion. Switch to git. Import your repos with git-svn.

  • I'll take it over QuickTime

  • just to add a little more explanation to what the other posters are suggesting.... a hard drive, from the perspective of your OS is very very simple. it's a series of bytes. for the sake of this example, let's say there are 1000 of them. they are just a series of numbers.

    how do you tell apart which numbers belong to which partitions? well there's a convention: you decide that the first 10 of those numbers can be a label to indicate where partions start. e.g. your efi starts at #11 and ends at #61. root at starts at #61 and ends at #800. the label doesn't say anything about the bytes after that.

    how do you know which bytes in the partions make up files? similar sort of game with a file system within the bounds of that partion - you use some of the data as a label to find the file data. maybe bytes 71-78 indicate that you can find ~/.bash_histor at bytes 732-790.

    what happened when you shrunk that root partions, is you changed that label at the beginning. your root partion, it says, now starts at byte #61 and goes to #300. any bytes after that, are fair game for a new partion and filesystem to overwrite.

    the point of all this, is that so far all you've done is changed some labels. the bytes that make up your files are still on the disk, but perhaps not findable. however - because every process that writes to the disk will trust those labels, any operation you do to the disk, including mounting it has a chance to overwrite the data that makes up your files.

    this means:

    • most of your files are probably recoverable
    • do not boot the operating system on that drive, or any other that will attempt to mount it, because you risk overwring data
    • before you start using any data recovery tools, make a copy of the raw bytes of the disk to a different disk, so that if the tools mess up you have an option to try again

    ONLY after that is done, the first thing I'd try is setting that partion label back to what it used to say, 100gb.. if you're lucky, everything will just work. if you aren't, tools like 'photorec' can crawl the raw bytes of the disk and try and output whatever files they find.

    good luck!

  • Hey, thanks for that, I appreciate you sharing your list.

    One option you can consider with fairmail and gmail is to use an "app password" to authenticate to IMAP, instead of oauth. That might work better when backing up with neo backup?

  • Everything else wrong with Gmail and Google aside, those are the least reasonable complaints? You can use labels as folders. You can also disable conversation grouping, but I doubt you go more than a week before turning it back on.

  • That's an interesting suggestion, thanks! I might wind up trying that for android auto + google voice 🤔

  • Hmm, thanks for the suggestion... this looks like it might be mainly for only pixel devices? Or devices that have a LineageOS build? I might be frustrated enough with the problem to learn Nix, but I don't want to be limited to particular hardware.

  • Another way of writing '10'

  • I don't have a particular guide at the tip of my fingers, but I can share some recommendations based on my experience:

    • prefer a phone with USB-c if you plan on connecting USB things to it. the otg adapters for micro-b are kinda hit and miss when it comes to keeping the phone connected to power as well.
    • look out for clearances of those carrier locked prepaid phones from physical stores, you can get nice devices for nearly nothing
    • whatever you're running on the phone, make sure it starts at startup, so you don't need to go launching everything if you reboot for some reason
    • if the phone is"mission critical" e.g. random restart while in the middle of a print is unacceptable, turn off all the automatic updates and such.
    • a VNC server has been helpful, to remotely poke at the phone if I'm too lazy to go do it physically
    • get something that'll keep the screen off the phone on. I've encountered reduced performance regardless of what battery optimizations I've turned off without doing that but YMMV depending on ROM.

    I fully expect the screen thing and the batteries bring in there constantly charging to kill the phones I'm using eventually, but it's something I expect and accept. my octoprint phones have been fine so far, for a bit over a year 🤷‍♂️