JCBird1012

In my opinion, all of these open source/free/open document signing tools are neat on paper (and technically fulfill the goal of being able to verify a document's chain-of-custody/signature provenance) - but won't take off in any meaningful way legally because there's no entity behind them taking the responsibility for accuracy and culpability.

DocuSign/Adobe/whomever is trust anchor, it's an entity you can sue or subpoena if something goes wrong. Someone who's actually on the hook for making sure whatever's signed is accurate and truthful (outside of the reputational risk of fraud completely obliterating any trust in your platform)...

No amount of cryptographic verification substitutes for having a legal person on the other end who can be held accountable for actually verifying the document was signed accurately/process was followed.

And just when I thought the DPE system couldn’t get any worse.

CarPlay and Android Auto were engineered from the start to be as agnostic to the car's hardware as possible. Your car's stereo is really just a dumb screen (i.e. just a display and input/output interface) with the phone doing most of the rendering + a few other things (i.e. providing some car instrumentation, like fuel remaining, if the manufacturer enables it) - the hardware requirements aren't really strict from a performance standpoint (minus CarPlay Ultra, and even then, that's just a tighter integration).

It depends on the airport! Some smaller airports (like Corona Municipal Airport where the story is based) - are untowered, meaning that there's no central ATC to chat with when taking off/landing - everyone announces what they're doing as they're doing it and there's a traffic pattern/flow that everyone follows to ensure there's no conflicts - it works surprisingly well.

In the US, you can get shockingly very far without having to chat with ATC.

I'd recommend changing your tagline -

> Share secrets from your terminal. One-time only. No accounts. No backend. No BS.

A server sure sounds like a backend to me.

It’s there - just built into the binary. ;)

but yeah that was upsetting - I was hoping they’d push them to a registry and make them… more available.

1. This is an official Docker image/container from Ubiquiti themselves - no more relying on LinuxServer.io/jacobalberty, etc...

2. With the "UniFI OS" branding, the door is open to the possibility of being able to run Talk, Protect, Access, etc... on your own hardware in the future.

And don't downplay how much of a role politics can play at making those facts/performance metrics harder/easier to achieve - and some companies are excellent deluding themselves into thinking it's not the case.

I know the intro video is a render - but the folding of the purple sheet looks so... unnatural (to put it lightly) - like the cloth physics do exactly what is convenient for the video and don't reflect reality.

Don't picture them as OTA firmware updates. Picture them as OTA navigation data updates (i.e. maps, charts, waypoints, airport info, etc...) - that's much easier to pull off.

The process right now is pulling out an SD card from your Garmin/Avidyne/BendixKing whatever every 28-days or so (that's how often the FAA updates the navigation database backing these avionics), popping it into your PC, using software/webistes that could be... much better designed (to put it lightly) and then going back again. It's not exactly the hardest thing in the world, but it's not exactly a walk in the park either (especially for less-technically inclined pilots, who just let it lapse, and click out of the big expiration warnings every time they start up their planes).

I can see what was meant with that statement. I do think compression increases Shannon entropy by virtue of it removing repeating patterns of data - Shannon entropy per byte of compressed data increases since it’s now more “random” - all the non-random patterns have been compressed out.

Total information entropy - no. The amount of information conveyed remains the same.