I know you're not being serious, but for anyone who may not realize that, it does more than disabling attachments. Lockdown Mode's "optional, extreme" protection substantially changes the experience of using your device. https://support.apple.com/en-us/105120
Where pwa.gripe cherry-picks and has an axe to grind, pwascore.com is intended to be a more thorough and dispassionate evaluation. I will add desktop browsers soon.
Click "Expand All" for a complete and detailed list. Click "How Scores Work" to understand the scoring heuristics.
Well the notifications on your web site doesn't provide the full idea of how limited it is in Safari. We have to ask users to install the shortcut before allowing notifications with Safari. Guess how many users actually go through with installing the shortcut? Nearly none.
If we had to ask users to go into their settings and switch the "enable notifications" flag we wouldn't call that supporting anything. The whole process of installing a shortcut to even get to the point where we can ask for notifications is even more convoluted on iOS.
The most significant effect is that experimental and non-standard PWA capabilities aren't reflected in the primary score. You can see raw/unweighted scores by hovering over the primary score. Chrome wins handily if you count experimental/non-standard features.
For standards-based features I used a 4-tier model, described about halfway through the README (which I should also add to About):
This weighting turns out to be reasonably conservative. For example, if you hover over the score for Firefox (the largest benefactor), you'll see that it bumps Firefox's score by 5.
I'm very open to feedback. This is a sincere attempt to quantify vendors' PWA support.
It's a classic case of optimizing the UX for the 20% use case rather than the 80% use case.
Most of the time, people have 2-3 work windows that they just want to swap between quickly, regardless of what "app" they happen belong to. The Windows alt-tab behavior captures that beautifully.
And yet your blog says you think NFTs are alive. Curious.
But seriously, RAG/retrieval is thriving. It'll be part of the mix alongside long context, reranking, and tool-based context assembly for the forseeable future.
I don't think RAG is dead, and I don't think NFTs have any use and think that they are completely dead.
But the OP's blog is more about ZK than about NFTs, and crypto is the only place funding work on ZK. It's kind of a devil's bargain, but I've taken crypto money to work on privacy preserving tech before and would again.
The issue I had with RAG when I tried building our own internal chat/knowledge bot was pulling in the relevant knowledge before sending to the LLM. Domain questions like "What is Cat Block B?" are common and, for a human, provide all the context that is needed for someone to answer within our org. But vectorizing that and then finding matching knowledge produced so many false positives. I tried to circumvent that by adding custom weighting based on keywords, source (Confluence, Teams, Email), but it just seemed unreliable. This was probably a year ago and, admittedly, I was diving in head first without truly understanding RAG end to end.
Being able to just train a model on all of our domain knowledge would, I imagine, produce much better results.
I have no interest in anything crypto, but they are making a proposal about NFTs tied to AI (LLMs and verifiable machine learning) so they can make ownership decisions.
So it'd be alive in the making decisions sense, not in a "the technology is thriving" sense.
> Of course you would have to set a temperature of 0 to prevent abuse from the operator, and also assume that an operator has access to the pre-prompt
Doesn't the fact that LLM's are still non-deterministic with a 0 temperature render all of this moot? And why was I compelled to read a random blog post on the unsolved issue of validating natural language? It's a SQL injection except without a predetermined syntax to validate against, and thus a NP problem we've yet to solve.
Just after that extremely gentle poke about a grift that died many years ago, you'll be pleased to see that I address the very silly claim about RAG in a straightforward, ad rem way.
> TL;DR They solved something to make post less expensive because they cut corners during production.
FWIW having watched the entire thing, they never blamed bad production staff or unavoidable constraints. Those are things that anyone working with others experiences when making anything, whether it's YouTube videos or enterprise software products. My TLDR is: "Chroma keying is an fragile and imperfect art at best, and can become a clusterf#@k for any number of reasons. CorridorKey can automatically create world-class chroma keys even for some of the most traditionally-challenging scenarios."
When you watch the video it becomes pretty clear why it wouldn't be able to do that, although it's fun to think about how a future iteration or alternative might be able to credibly (if you don't look too hard) mimic that someday.
reply