hello google please let me sync my watch between android devices instead.

I haven’t used a stock launcher for a decade and haven’t noticed any issues… currently on KISS launcher.

John Oliver take on it https://youtu.be/gYwqpx6lp_s

and it’s potentially an existential threat.

I highly recommend installing fzf, and its shell integration. Makes your Ctrl + r magnitudes more pleasant to use!

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.

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

The sentiment of the first half of your comment is the cause of the problem you describe in the second half. Why /should/ the CI tool have any “steps” built in? Use a task runner, or script in your repo for any task you expect CI to do. Configure CI to run the same command you would run locally.

yeah, you can use any app, and they work fine… with, as you might expect some warts due to apps not being designed for that screen size. a common issue is with apps that have ridiculous fixed headers and footers, leaving you a teeny tiny sliver of space for content. there’s an option to make the viewport slightly bigger, since the screen extends down and around the outer cameras, and that helps sometimes, but then obviously the cameras might prevent you from hitting some buttons on that footer. this is not a very common situation though, and maybe almost desirable? I can use the outer screen to do quick phone interactions and put it back in my pocket without being too sucked in. if I want to doom scroll/get otherwise immersed, I’ll open the fold. i like that this needs to be an intentional action.

you can respond to messages and type on the outer screen, yes, using any keyboard as long as it’s Gboard.

yeah, I liked the z3c so much, I must’ve gone through like 4 copies of them, until a newly purchased one had the screen let go within a month of me opening up the box. I’ve been chasing for a modern version of that phone ever since, and the razr+ is the closest I’ve come

I think it’s more correct to say that non-flagship phones are cheaper. all modern spec small/compact phones in my recent memory have had a comparable price to their non-small counterparts ( e.g. Xperia compacts, Zenfone, whatever that small iPhone was called). the price of a device isn’t linearly proportional to its mass.

flip phone owner here! I love my razr+/40 ultra. the small screen is entirely reachable by my thumb, and is plenty big enough to read emails, messages, etc. i even use it to play passtime games, like into the breach, or attach it to an 8bitdo zero with a 3d printed case to use as a Gameboy.

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.

https://www.destroyallsoftware.com/talks/the-birth-and-death-of-javascript