Unless of course your adversary can count. But if they can count they can also just count the number of keystrokes they hear, especially if you're recording it and they can spend time post processing the audio.

As a general rule, if you have an adversary that cares that much you’re probably doomed.

Presumably they’re capable of buying a $5 wrench to physically use against you.

Unless they want to compromise you secretly.

Then spear Phishing is almost certainly more economical.

Or just plugging a device into your laptop while you’re not looking and stealing all your session state for browsers.

Fortunately I'm using Qubes OS, so this attack will not work.

I feel like livestreaming is a good example of an unusual situation where one might consider changing defaults that are otherwise good for the majority of users.

Also, I think the vulnerability of knowing that someone's password is exactly 19 characters long is low enough to be worth the tradeoff. Especially since someone on a livestream can also figure that out by listening for the keypresses.

Even in my internal company tech support line they play that "higher than expected call volumes" message, but their website also has counter on it that tells you just how many people are on hold and even when it is just one (me) it plays that message.

The only ones I believe are the ones that tell you the estimated wait time or number ahead of you (most of which offer to call you back).

It is funny to hear "our wait times are higher than average, your wait is estimated to be zero minutes".

Easy for that to be true: just set your expectations to zero.

The question is how much of that data do they sell to data brokers.

Google also "Doesn't sell your data to data brokers"

Because they sell "insights" or "access" or "marketing" or whatever.

Some of it may also be neighborhoods where solar contractors went door to door selling the systems. Even if you don't buy from that salesman you get the numbers in your head and start to realize it isn't some exotic tech for elite weirdos.

My sister was just such a representative going door to door in Connecticut. This was likely a factor. The southern coast of Connecticut, being in the shadow of New York and thus dense with rich exurban homeowners, is a prime market for such contractors.

I clicked on the link for the "Yuppie button" and confirmed that the guy is a nut. The amount of effort required to create and install a device that flashes all of your tail lights at a tailgater is not something an average person is going to do.

Would you say old DOS applications like Borland's Turbo series of compilers were not TUIs? They ran in the console but had menus, mouse support, dialog boxes, etc...

How about those text games that used ASCII art and you typed in commands like "look" and "go north"?

I would say using text mode is the primary requirement for a TUI. The other requirement being some kind of human-machine connection, IE a User Interface.

I've been working with notcurses recently and it is a full TUI that handles mouse events just fine. Runs over slow SSH connections and everything. The nice part is that you can fully operate applications built on top of it with the keyboard if you so choose, the mouse is just a shortcut.

Sadly the project is not really in a usable state at the moment. The documentation is incomplete riddled with errors, the code has some pretty glaring bugs, and it's close to abandoned. It's a shame because you can do some really amazing stuff with it.

The question was about forwarding as I understand it, not address resolution, and there simply won't be any forwarding, since the 32 bit only sending host won't be able to address the 128 bit receiving one.

It's kind of annoying that the 3D viewer on their website keep you a respectful distance away from the object like you might try to touch it if you got too close.

It appears they arbitrarily limit the zoom such that the object stays within the browser frame. On my gigantic monitor I can get super close. Lame that they set it to stop like that

It works really well with the AR viewer on mobile Safari.

Interesting, on desktop Firefox I can barely zoom in past the point that the object fills the FOV.

I want to be permitted to navigate up close to a point where I can see the pixels and triangle meshes, as if I was a millimeter away from some brush stroke or chisel mark, and then back out just a bit.

For anyone wondering, you can access this by tapping the button showing a 3D cube at the bottom left of the 3D viewer. The button may be cut off if you're viewing in a web view in another app like I was.

The AR viewer runs with a much higher frame rate and you can get closer to the model. However the lighting is significantly worse, which ruins the appeal. The in-browser viewer is choppy and I can feel my phone getting a little warm, but it looks a lot more like viewing the real artifacts.

Doesn't seem to be an option on Firefox android

The AR viewer is using ARKit on iOS which is a default system “app”. I don’t believe Google provides the same kind of built in viewer experience with AR Core being surfaced as an app.