Macy's now has a Toys Я Us branded toy department.

I don't know. I'm typing this in a razr 40 ultra with a shattered outer screen. on one hand, it sucks that it's shattered. on the other hand, I'm happy it has a second screen as a point of redundancy?

... but there is a way, and it has been proven.

One of the more memorable physics classes I've had went into the history of discoveries that led to our understanding of relativity. The relevant story here, starts with how sound travels though air.

Let's say you're standing at the bottom of a building shouting to your friend peeking out a window on the 5th floor. On a calm day, that friend will hear you at pretty much the same time as someone standing the same distance away, but on the street. However, if it's windy, the wind pushes around the air through which the sound of your voice is traveling, the friend up in the window will have a slight delay in receiving that sound. This can of course be verified with more scientific rigor, like a sound sent in two perpendicular directions activating a light.

Scientist at the time thought that light, like sound, must travel though some medium, and they called this theoretical medium the Aether. Since this medium is not locked to Earth, they figured they must be capable of detecting movement of this medium, an Aether wind, if you will. If somehow the movement of this medium caused the speed of light in one direction to be faster than another due to the movement of this medium, measuring the speed in two directions perpendicular to each other would reveal that difference. After a series of experiments of increasing distances and measurement sensitivities (think mirrors on mountain tops to measure the time for a laser beam to reflect), no change in the speed of light based on direction was found.

Please enjoy this wikipedia hole: https://en.m.wikipedia.org/wiki/Michelson–Morley_experiment , and please consider a bit of caution before you refer to things as facts in the future!

Are you using PersistentVolumes? If your storage class supports it, looks like there's a volume snapshot concept you can use, have you looked into that?

Not sure what you're doing, but if we're talking about a bog standard service backed by a db, I don't think having automated reverts of that data is the best idea. you might lose something! That said, triggering a snapshot of your db as a step before deployment is a pretty reasonable idea.

Reverting a service back to a previous version should be straightforward enough, and any dedicated ci/cd tool should have an API to get you information from the last successful deploy, whether that is the actual artifact you're deploying, or a reference to a registry.

As you're probably entirely unsurprised by, there are a ton of ways to skin this cat. you might consider investing in preventative measures, testing your data migration in a lower environment, splitting out db change commits from service logic commits, doing some sort of blue/green or canary deployment.

I get fairly nerd-sniped when it comes to build pipelines so happy to talk more concretely if you'd like to provide some more details!

Not even Chrome is blocking some of the add-ons...

is that something you know for sure? or has Google quietly complied with similar requests, without making a statement like Mozilla has here?

I do this with my xreal glasses sometimes when washing dishes or whatever. Connected to phone in my pocket with a desktop mode, set a black wallpaper, and drag the video into a corner.

It's nice for situations like that, where you're doing something with your hands and can't reasonably place a screen in a way where you wouldn't have to constantly strain your neck to look at it.

Right. So why does my phone also need to be a part of surveiling others?

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

I personally disabled the feature on my phone when it popped up as available. I don't have much of an interest in contributing to a weird surveillance network.

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

it could explicitly be a reasonable deterrent. if you double your price, but lose half your customers, you've made the same amount of money for half the work.

"Hi, I just sent the ransom payment to the Bitcoin address you provided.
"Now you'll unlock my data, right?
"...... right?"

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.

that's a good call actually. I got pretty hung up on domain objects being mostly data classes, but one approach is to have them perform business logic themselves.

Not a security scientist, but in my interpretation, it's the "categories" of the factors that matter. Ideally, you use some two of three of:

• something (only) you know - generally represented by passwords
• something (only) you have - most commonly represented by some device. you prove that you have the device by providing a token only that device can generate.
• something (only) you are - generally represented by biometrics

the goal then is maintaining the "only"s.

if you tell someone your password, or they see you type it in, or they beat it out of you with a wrench, it's no longer something "only" you know, and it is compromised.

if you use the same password on two websites, and one website is compromised, the password is compromised.

OTPs from a key fob or yubikey or something are similarly compromised if the device that provides them is left out in public/lost/stolen/beaten out of you with a wrench.

biometrics are again, are compromised if it's not "only" you with access to them - someone scans you face while you're asleep, or smashes your finger off with their wrench.

having multiple factors in the same category, like having two passwords, or two otp tokens, or two finger prints, doesn't significantly improve security. if you give up one thing you remember, it's likely you'll give up more. if one fob from your keychain is stolen, the second fob on that keychain is of no additional help.

you can start shifting what categories these things represent though.

if you write down your password in a notebook or a spreadsheet, they become thing you have.

OTPs can become something you know if you remember the secret used to generate them.

knowing many different things is hard, so you can put them in a password vault. the password vault is then something you have, which can be protected by something you know. so although your OTPs and passwords are in one place, you still require two factors to get access to them.

you still need to protect your "only"s though. and don't put yourself in situations where people with wrenches want your secrets.

I use passwordstore.org/ as my password manager, including for my otp codes. It's backed by a git repo. I get a backup of it on every device it is cloned to.