I think you can link a second Whatsapp app, similar to the web client. your primary one needs a webcam to read the QR code though

A JavaScript VM in the kernel is inevitable.

not by any means modern, but I used to really like pal

More than that, your editor doesn’t run with root permissions, which reduces the risk of accidentally overwriting something you didn’t mean to.

it feels to me, like they’re less looking for new people to start doing this “work”, but more to connect with people who already happen to be enthusiastically going to events and showing off their laptops.

I use these two vim plugins for the same functionality without leaving $EDITOR:

• https://github.com/wookayin/fzf-ripgrep.vim
• https://github.com/ctrlpvim/ctrlp.vim

I’ve also started dabbling with using fzf in scripts for the team to use. Don’t sleep on the --query and --select-1 flags!

is that more or less cursed than cat image.img > /dev/whatever?

dd if=image.img of=/dev/disk/flashdrive is usually all you need

Definitely not what you’re talking about, but still: https://www.destroyallsoftware.com/talks/a-whole-new-world

The two factors at an ATM are possession of your bank card + knowledge of your pin. (it also takes your photo, for good measure)

GitHub will happily accept a smart card or whatever, if an extra plastic rectangle jives with you more than an OTP generator.

Your two factors shift to possession of your password vault + knowledge of the password to it. You’re okay IMO.

You also still get the anti-replay benefits of the OTPs, though that might be a bit moot with TLS everywhere.

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.

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!

something to consider here… Firefox lazy-loads out of focus tabs when you start it, so if you’re a tab hoarder, it’s nice for just the one active tab per window to load when you start the browser.

I’m not sure that you can get it to do the same with “out of focus” windows. or maybe I have a tab hoarding problem.

I didn’t like the random blinking and glitchiness the screen did as it changed resolutions. Most OSes, if you notice, do a little fade out and in but I was too lazy to make it gradual.

Eh, though you’re right, it’s a pattern I like a lot: define your “main” at the top, put all the supporting functions below, and call main at the end.

These days I’ve got a little bash task runner framework that I use for little scripts like this.

I have a stupid little script for this:

#!/bin/sh

setres() {
  output=$1
  width=$2
  height=$3

  xrandr --output $output --brightness 0 --auto
  xrandr --delmode $output better
  xrandr --rmmode better

  xrandr --newmode better $(cvt $width $height | tail -n1 | cut -d'"' -f3)
  xrandr --addmode $output better
  xrandr --output $output --brightness 1 --mode better 
}

setres "$@"