jwatzman

6 ms·

1.
by jwatzman 2mo ago
No — the victim app is code signed and the permissions and keychain access are tied to the cryptographic identity used to code sign. Replacing or wrapping or whatever here must happen with a different cryptographic identity (unless you actu
2.
by jwatzman 2mo ago
Not sure I understand the risk here, and seem to agree with Apple this is a non-issue. You already have code execution in order to exploit this. You don’t get the cryptographic identity of the victim app so you can’t steal keychain secrets.
3.
by jwatzman 3mo ago
There are a few others. “Quite” comes to mind — “I am quite hungry” or “that meal was quite good” can mean opposite things, depending on the speaker region and even voice inflexion if spoken.
4.
by jwatzman 3mo ago
My prospective co-founders and I were pitching to a VC firm that was, on paper, a really good fit for what we were trying to do. The partner we were pitching to was, 15 years ago, briefly my manager's manager -- some work relationship
5.
What's Up with Monomorphism? (2015)(mrale.ph)
1 points by jwatzman 8mo ago|0 comments
6.
by jwatzman 1y ago
Yeah, the docs are open-source, but aren't running anywhere. https://github.com/getcord/cord/tree/main/docs/server/routes
7.
by jwatzman 1y ago
In Rust, it's considered a bug for any code which isn't using `unsafe` to encounter a memory error (e.g., to segfault). That bug might be in some underlying library (which is itself using `unsafe`), or more rarely in the compiler,
8.
by jwatzman 1y ago
For do not disturb, you can: settings -> focus -> do not disturb has a section at the top for allowing specific apps or specific people.
9.
Do you hate Dino Dini's Soccer? One tiny bug, a world of hurt [video](youtube.com)
2 points by jwatzman 1y ago|0 comments
10.
by jwatzman 2y ago
Can you elaborate on the complexity here for syscall entry on x86_64? (Or link to what you were reading?) Another commenter linked to Linux's own "nolibc" which is similar to, though simpler than, the Google project in the OP
11.
Exploring LLM Weirdness: How We Built It and What I Learned(cord.com)
2 points by jwatzman 2y ago|0 comments
12.
by jwatzman 2y ago
Glad you liked it! My co-author and I spent some time trying to find a good spread of questions covering different aspects of LLMs. And we were also surprised by how hard it was to convince GPT-4 that Queen Elizabeth II had died a lot of th
13.
by jwatzman 2y ago
(co)-author here. It was really interesting putting this together. We had some idea what LLMs/GPT-4 would and would not do well with, but were still surprised ourselves with a number of things. In particular, we knew it would really st
14.
Exploring LLM Weirdness: A Quiz Game(quiz.cord.com)
4 points by jwatzman 2y ago|4 comments
15.
by jwatzman 3y ago
There are a bunch of online tests that help you see if you, with your ears and equipment, can tell the difference. http://abx.digitalfeed.net/ and http://abx.digitalfeed.net/list.lame.html was on HN some ti
16.
by jwatzman 3y ago
League of Legends (a similar game) does this -- no booths, only noise-cancelling headphones, for its large tournaments. There have been several major tournaments where the players have complained afterwards that they could not hear anything
17.
by jwatzman 3y ago
The article discusses constructors and how to make them work under "Linking the C++ standard library". I wonder if placement new would run into the same linker problem that the article mentions -- I'll have to try it at some
18.
by jwatzman 4y ago
Indeed his videos are amazing . My recommendation though would be to start with the "beginner" video -- which is completely 2D but at least gets some ideas across. Then watch https://www.youtube.com/watch?v=PGtv-d
19.
by jwatzman 4y ago
> if this was your point, the example is terrible. Yeah, I addressed this in another comment here. I attempted in the last section to separate the ideas of "I heroically dived in" and "I took an opportunity in front of me&
20.
by jwatzman 4y ago
> The more interesting one though, is that sometimes high-impact work is "just there" to be done, if you're looking. Author here. Yes, this was exactly my point! > But the best way I've found to detect promising ju
21.
by jwatzman 4y ago
Author here. For what it's worth, I (mostly) think you're right! IMO heroics were a huge problem at that company, and are a huge problem at the company I work at now too. The gruntwork is really really important. I tried to get at
22.
by jwatzman 4y ago
Author here -- thanks, glad you enjoyed it!
23.
by jwatzman 6y ago
Original source: https://twitter.com/EmilyKager/status/1313303791186268160
24.
by jwatzman 6y ago
Along with the above fantastic comment, I found https://apenwarr.ca/log/20170810 an interesting (if inflammatory/divisive) essay on the subject and its history.
25.
by jwatzman 6y ago
> The concept of an application 'supporting a (specific) file system' sounds slightly ridiculous to me. This concept is actually way less ridiculous than you might think, for any application which needs any guarantees about dat
26.
by jwatzman 6y ago
If you're looking to buy the card in the article, I just got one of these https://www.aliexpress.com/item/4000958505670.html which looks to be exactly the same card, and doesn't require scouring eBay. I haven
27.
by jwatzman 6y ago
I'd not heard about van Emde Boas layout before, and it sounds super cool! I wish the author had included a simple example before focussing on the general case -- I find it hard to get an intuition for the general without a specific ex
28.
by jwatzman 6y ago
OP here. Explicitly-annotated fallthrough was still allowed; I codified a particular annotation that the analysis tool understood and allowed. I removed implicit fallthrough, but explicit fallthrough can be quite useful sometimes.
29.
by jwatzman 6y ago
Author here. Yeah, you can't just mechanically insert the breaks :) I carefully went through each instance where my rule tripped, looked at the surrounding code, and figured out the right fix. Trying to automate that would indeed have
30.
by jwatzman 6y ago
Post author here. One of the nice advantages we had in using our static analysis tool for this, with real code intelligence, instead of a simpler linter, was that we could do a much more clever check. The actual rule was "every case mu

More ›