To be fair, you picked a well-known tricky benchmark for LLMs: When working on an embedding spelling disappears after the embedding level. I imagine modern frontier models have tools that let them read back their input to work around this issue.
The classical solution to the secretary problem works under two very unrealistic assumptions: (1) you win only if you pick the best candidate. Picking a close second is worth nothing. (2) you have no prior information about the expected distribution of the skills of possible applicants.
So I am not sure we should really follow that heuristic in real life.
Yet by the active unique user numbers they have estimated sold at least ~168k copies and maybe upwards ~500k https://steamdb.info/app/280680/charts/ And that's Steam alone. I'd be really curious compared to this how many people click on the Donate button on the Krita homepage.
That's a lot of purchases imo for a project like this. I'm kind of ambivalent about the store cuts but they give a huge enough exposure to any game or software.
The huge UX drawback of password managers vs. passkeys is sites that have arbitrary requirements. "Your password must be between 9 and 12 characters long, and include at least two capital letters and a special symbol". Well, my password is randomly generated, and enforcing that there are two capital letters would just reduce entropy.
If sites fixed this issue instead of pestering me for a passkey I'd be happy.
Do I understand correctly that the main workflow is "pick the first Github repo returned by the search, check that it is legit by clicking the link, then install the app from it"? It seems very easy to make a mistake and install a malicious fork.
Yes, that is a weakness. But people have to do the same thing when they install F-Droid, or any other software directly from a developer's website. Maybe it is safer to trust an app store, but I've recently heard stories of hundreds of malicious apps getting past app store verification too.
SMS is a defacto carrier tech that people expect to work, people also don't expect e2ee or any kind of privacy scheme on SMS but it might be a place to hand communication off to a different tech. Whereas RCS leaks meta data to the goog or worse (I don't know the ins and outs of RCS) but by default I would trust it less then signal, who may also collect meta data leaked through the goog, so I guess the real solution is to be boring and assume there is no security or privacy for anyone of reasonable means.
Just because RCS can't be done without metadata doesn't mean it's a fruitless endeavor. Why not have someone use RCS to then get on Signal? That is so much better than plaintext SMS to Signal.
And for most people, RCS between Android <-> iOS is the biggest advancement in encrypted communication for the layman that I've seen since Let's Encrypt.
We've announced our plan to add RCS with Messaging Layer Security (MLS) for E2EE compatible with Google Messages and iOS. SMS/MMS will only be a fallback once that's implemented.
Google Messages is essentially the only remaining RCS client for Android and it's the only one with end-to-end encryption. It already works on GrapheneOS via a toggle for ICC authentication extending our sandboxed Google Play compatibility layer. We want to add support for it to our own Messaging app but that's not straightforward since it's not at all an open platform even to the extent of SMS/MMS.
I appreciate the update. I wish RCS was more open. I'm still astonished that it wasn't until 2024 that iOS adopted the protocol. Relying on everyone in your group chat to be all Android or all iOS (iMessage) wasn't helping anyone.
That is a positive progression for sure. I guess it sounds like RCS is gatekept behind a play store API on the android side so there isn't an open source solution quite yet? Mostly I'm lamenting that even with signal there's meta-data you can infer behavior from. I know Session messenger has a bit of a network shuffle (is it garlic routing?) That blurs metadata collection a bit, but then they watered down several of Signals' security/privacy choices. I'm constantly curious and overwhelmed at the choice of text communication platforms, just so many!
reply