My worse fear has materialized.
This is why I've never used an external Obsidian plugin and only my own plugins.
It was only a matter of time before some malicious code ended up in one.
Can you clarify what you mean?
The example is to show concretely the computation. It works as long as you have the basic setup for shamir secret sharing (and other linear secret sharing schemes actually but I didn't go into that in the article)
You aren't the only one that has alerted me of framer-based sites crashing on iOS.
I'm trying to find a resolution but it appears to be a framer problem. I asked one of my friends and he was able to access the article fine.
Most explanations just give formulas and no intuition. I tried to give intuition and a concrete example. If you email me, I can share the images that help with the intuition without the rest of the blog post.
This looks great but how does it differ from the many wallet services that offer link sharing built-in without the subscription? As many wallets support tokens across many chains these days, link sharing is essentially a feature and no longer its own product.
You can still derive a lot of info without having possession of the data through the use of PETs. There's a reason why companies like Google and Tik Tok make heavy use of PETs for their advertising products.
This article is kind of hilarious to read.
This is my life since getting a dog (and I've been doing versions of it before my dog too) but this guy just discovered the way Europeans have been living for hundreds of years and wrote a whole article about it.
I guess this is also one of the great things about the internet. Another person's mundane thing is another person's discovery.
> Unexplainable security features are just marketing materials.
I feel this way about a lot of hardware-based security solutions like TPMs, and TEEs. These are actually useful solutions that can help solve problems that we have (as evidenced by this article) but unfortunately, these solutions tend to be poorly publicly documented. As a result, we rely on academics to do the work for us in order to learn how to better contextualize these solutions.
My counterargument for that is that LLMs need to communicate not only between themselves and humans but LLM to LLM communication. We will get more niche and domain specific languages designed for LLMs as a result.
One thing that many of these kinds of articles don't really talk about but that also emphasizes their point is that there will be an increase in interfaces/languages for software developers to do increasingly specialized for work. As such, there will be more compilers, vms, dsls, etc which means that there will be more of a demand for developers who have this skillset. Ideally, this should lead to more folks becoming developers or at least acquiring skills that professional developers have in order to make effective use of these tools.
Working on an MPC stack to make it easier for devs to integrate privacy into their stacks.
As normal folks increasingly value the privacy of their data, developers will need to think about how they can build apps while guarding their users' data. We provide tooling for them to do this.
Still WIP but we are getting our first audit in the coming days!
I hadn't done a ton of research on them but I skimmed their paper.
That's a really cool find. I'm curious to see how it compares to TikTok's suite of 2PC protocols for advertising measurement and Google's use of TEEs for ad auctions.
I didn't know that. I encountered these emails recently from the Tech Emails X account and figured I'd share here because 1) it's very timely considering the NYC mayor elections and 2) HN is a great place to read about people's thoughts on topics like these outside of where I usually hangout.