splendidHaiku

Same here. I was carefully planning and rationalizing my usage :/

But then the metadata, e.g. gps coords, time of the recording, etc. of the recorded video will not match with what is displayed. So it would be an obvious fake.

Everything will be considered fake unless it is proven authentic.

How do we prove authentic? Same way we prove that a website we visit is authentic. Every recording made will be signed/hashed and be able to validate of the public key of the recording device (every phone will have a key). White House, News Orgs, etc. all will use cameras with public keys so everyone can validate. As soon as only one pixel or frequency changes, it will be invalid/fake.

In the end, all will be even more trustworthy than today (there will be some kind of signed/verification label on every video/audio/media that is original/valid).

For me too. Only thing I sometimes struggle with, is figuring out how to place error catches. Wrap each async functions body in a try catch? Or always attach a catch handler to the calling function? But what if I forget to do that? Should the caller or the callee handle the errors or can both?

Does not always work like that. Did people „want“ cars when there were only horses. Or Facebook when there was just email. Sometimes you build something and only after people realise that they want built thing.

Overall it had no positive spin - so no. Also there is a difference between "This was nothing to be glad about" and "There was nothing to be glad about".

I thought about changing my slightly verbose react state updates to immerjs but your lib looks even simpler. I dont think it can be simplified any further, really great, thank you.

leave sending station above ground. send down hot ice melting probe (no drilling) attached to long cable.