manbash

I would love to try this out. Thanks for all the effort :)

P.S. happy to see other "critters" around here.

It doesn't mean that it's nonexistent. The news story is about one company that provided fake sources for a past article.

Rent-a-friend/family in Japan seems like a real thing.

One actual use-case of DARPA ("The Military") is to deploy such robots in disaster-stricken areas instead of risking human. For example, emergency maintenance in a power plant that has suffered a nuclear meltdown accident.

> The switch fits in a 14mm square hole (apart from the protruding wires), which is the same size as a Cherry MX switch, but the total height from the bottom of the switch to the top of the keycap is almost twice as large, about 45 mm vs 25 mm [...] This directly translates to increased keyboard height, so it would be good to cut this down as much as possible. I should be able to lose 2 mm from the wire support at the bottom of the switch, and another 1 or 2 mm in the height of the leaf spring attachment, but there's no way it's going to be as thin as the Cherry MX.

It's a nice concept but the design of the switch doesn't intend this project to replace your keyboard.

A nice design nevertheless :)

I am thinking the same now. The OP solution requires a server to do the the processing, but I am not sure this is the case for the Zoom client.

The Zoom client also requires minimal hardware requirements from the processor iirc.

Great read! I am curious then why the Linux client doesn't supports this, if all it takes is to send out our webcam stream data to be processed server-side?

P.S. What happens when they do e2ee on the webcam stream?

From a look at the github, there is a sudden "surge" or commits, likely to prepare to present it to hackernews. But overall this github doesn't seem to be maintained and users issues are sitting there unanswered.

https://github.com/susam/texme/commits/master

You can pass the NFC card, which is different from biometric. Unless you mean implants?

I agree. A toy widget with a simple input and output of the font would've been preferable.

> Should that happen, how would you respond and revoke the lost SSH key? Do you have an accounting of the keys which have been generated? Do you rotate SSH keys? How do you manage that across an entire organization so consumed with serving customers that security has to be effortless to be adopted?

The problem presented above and the solution they offer seem like miles apart.

The number of ssh keys is likely finite in an organization. It shouldn't be hard to keep track on those.

Instead, you're supposed to integrate a complex process?

Encrypt your data, add a passphrase to the key, have admins keep record.

Does CF have little faith in admins?

Why is the following still open then? https://gitlab.com/gitlab-org/gitlab/issues/34833

Are those not conflicting each other? Genuinely curious.

Languages evolve, and in this case it's for the better.

Topic aside, what is going on with the mobile UI of this article? This is an abomination!

This seems to be around since 2017. What am I missing?

I was thinking the same thing: logsitics-wise, it seems more efficient to stack all the material flat in the trailers rather than have a premade box with a lot of unused space (the room's interior).

On the other hand, having the ability to construct everything at the factory helps overcoming issues such as waste of material and lost time due to conatruction error, not to mention the health of construction workers not depending on weather conditions as much.