So how can you verify correctness of transcription and summary in a way that is repeatable over time?

That's the job of the provider. There's no other way to actually verify the accuracy of the note. You can't actually engineer humans out of the loop, the loop revolves around humans.

How does the provider verify the accuracy if they don't have the transcript or the original recording?

Agreed. That sounds like a recipe for "we don't know how 'the algorithm' came up with what it did" kinds of excuses when, inevitably, inaccuracies are found. It also seems, conveniently, to make the processing system practically unimpeachable.

Any thoughts on https://news.ycombinator.com/item?id=47896064 ?

We need to draw the line somewhere. Later is better.

Re: point 2. It was all possible until the MBAs came along. Companies were private.

Less total sales, but who cares? You build a quality product and everybody is happy.

Except with using Rust like this you're using it like C#. You don't get to enjoy the type system to express your invariants.

That's the risk you take on.

There are 2 things to consider:

    * Time to market.
    * Building a house on someone else's land.

You're balancing the 2, hoping that you win the time to market, making the second point obsolete from a cost perspective, or you have money to pivot to DIY.

I agree. PR merges for me are bisect points. That's when changes are introduced. Individual commits don't even always build.

And I don't rebase or squash because I need provenance in my job.

I have the feeling a lot of people take Macs because the other option is a locked down Windows, and Linux is not offered.

This. I ran Linux at work until last year, when it was finally disallowed. I went with locked-down Mac over locked-down Windows.

The hardware for a Linux laptop right now is not great. Especially for an arm64 machine. Even if the hardware is good the chassis and everything else is typically plastic and shitty.

That is a surprising sentiment. Most dell and Lenovo laptops work just fine and are usually of reasonably good build quality (non-plastic chassis etc.).

arm64 is however mostly bad. The only real contender for Linux laptops (outside of asahi) was Snapdragon's chips but the HW support there was lacking iirc.

They give us Dell Linux machines from work. They suck so bad and we have so many problems. Overheating, camera is terrible, performance is bad relatively to the huge weight of the device. Everything is a huge step down from Macs.

Whenever I see Linux people comparing Linux and Mac I'm amazed at the audacity. They are not in the same league. Not by a mile. Even the CLI is more convenient on the Mac which is truly amazing to me.

How is the Mac CLI more convenient? There isn't even a package manager in the box, they ship loads of old outdated tools too. Plus there's the whole BSD/GNU convention thing you have to watch out for.

I don't find my ThinkPad running Linux overheats, nor is it particularly heavy. And performance is comparable to the similarly priced MBP at the time. Camera sucks, but compared to my Surface so do the Macs...

Prefer my Konsole setup on KDE and I use both interchangeably all day tbh. Camera yea. The irony is heating issues become less of an issue with arm.

We are lucky in that we can choose our machines (within reason, and no real support if things get broken) and run an arch flavour.

I use thinkpad x1 carbons and have nearly 0 issues. The hardware is not quite as nice as a macbook but it does the job and is nice enough.

Recently an article on HN front page was about a guy who had to file down his MBP because the front edge of it was too sharp and resting his wrists on it hurt his hands. At least two people in the comment section noted how the sweat on their hands over time caused the sharp edge of the MBP chassis to pit and it caused it to turn in to a sharp serrated edge that actually cut their hands.

You can say other laptops are "plastic and shitty" all you want, but Apple's offerings aren't necessarily the best thing out there either. I personally like variety, and you don't get that from Apple. I can choose from hundreds of form factors from a lot of vendors that all run Linux and Windows just fine, plastic or not.

I specifically don't update the version in Cargo.toml in the codebase. I patch it in just before cargo publish, otherwise all other PRs now need to change.

But there is a way to do this encrypted, so that when the notification is received on your iPhone, the process itself needs to decrypt it.

Except you need an entitlement for that, because it requires that your app has the ability to receive a notification without actually showing it (Apple checks this).

Your app gets woken up, decrypts the message, and then shows a local notification.

Apple also by default backs up your apps to the cloud.

But it backs up the WHOLE package / folder / whatever terminology they use, including cached and redownloadable data. So if you have a game that has 10GB of cached data, it WILL upload that. Edge for me was >3GB.

And then they have the following user-hostile 'features':

    1. They offer a paltry 5GB. Hasn't changed since inception, but app sizes have ... tripped? I have 2GB of health data now. 
    2. They don't tell you that you're backing up data that can be retrieved elsewhere.
    3. The popup when storage is full shows only 'buy more' or ignore (no link/mention to disable individual app like described above)
    4. No way to backup to a NAS
    5. No way to backup to a computer automatically. You have to provide you passcode every time.

The Apple backup strategy is purposefully broken. I’m already paying for 50GB of iCloud and it often claims that it cannot backup my iPhone despite having multiple gigabytes free. It turns that that during the backup process it operates on a file level, so if you happen to have a large file it will require both copies of the file to fit within your storage limit before the backup can complete. And guess what, several third party apps I use store all their data in a single multi-gigabyte SQLite database that’s written to every day.

As for cached and downloadable data, I have long ago turned off backups for many apps where the data is stored on a server anyways. Backing up these apps never makes any sense.

That's on app developers (I suspect mobile game developers are not the most competent of the bunch). My entire iPhone's backup is 4.6 GB, and my YouTube downloaded videos alone are way more than that.

> That's on app developers (I suspect mobile game developers are not the most competent of the bunch). My entire iPhone's backup is 4.6 GB, and my YouTube downloaded videos alone are way more than that.

While it's the app developers that need to make the change, it should be enforced by Apple. After all, that's why there is a walled garden, and that is the premium we pay for when using Apple.

But for Apple to enforce this means less popups on screens telling people that storage is full, which means less sales.

And again, we get to Goodhart's law.