> You make subtle mistakes in how you perceive the world, the interlocutor makes similar mistakes
And the LLM makes subtle mistakes perceiving what you were trying to say, and I make subtle mistakes perceiving what the LLM generated.
It's interesting that you seem to think an LLM would be better than you at understanding what someone was trying to say. I have complete, 100% certainty that if a personal friend of mine was having trouble expressing themselves and was concerned about being misunderstood, I would understand what they were trying to say better than any existing LLM. (I suppose the exception would be if the friend was referencing some factual matter I'm unaware of but that the LLM has memorized, like a pop culture reference I didn't get or something.) Do you find that ChatGPT has more emotional intelligence than you?
The WIT types don’t seem random or Rust-centric to me, they’re basic types common to every major current-generation language, not just Rust but also Swift, Kotlin, even Zig. It’s true that languages with type designs from the 90s can’t take full advantage of WIT types, but WIT does seem perfectly capable of representing types from older languages, which seems like the only possible sensible design to me—older languages are supported, but that support needn’t burden interop between modern languages.
You seem to be implying that these goals were optional, but I don’t understand how #2 cross-lang interop could ever have been optional. Isn’t running non-JS languages the entire point of WebAssembly?
Given that, do you really think goal #1 non-Web APIs really added much additional delay on top of the delay necessitated by goal #2 anyway?
Are you pretending you didn’t even have an LLM help you reword it before publishing? Because that would be an obvious lie. If you were to propose a sufficiently trustworthy way to prove one way or another, I’d bet $1,000 on it.
Specifically there’s a lot of clickbaity constructions like: “setup: payoff” or “sentence fragment, similar fragment, maybe another similar fragment”.
This paragraph has both:
> The symptom is familiar: a stream that occasionally "locks up" briefly before catching up, jitter in audio or video, or a latency spike that appears to come from nowhere, a "hang" in the application when it gets blocked waiting for a packet. It comes from a single packet forcing the entire pipeline to pause. The underlying network recovered quickly; TCP's ordering guarantee is what made it visible.
So does this!
> WireGuard's protocol is a fundamentally different design point. It's stateless — there's no connection to establish upfront, no session to track, and no certificate authority in the picture. Two keys, a compact handshake, and you're encrypting. And unlike TLS, WireGuard's cryptographic choices are fixed: Noise_IKpsk2 for key exchange, ChaCha20-Poly1305 for authenticated encryption. There's nothing to misconfigure.
Does it bother anyone else when an article is so clearly written by an LLM? Other than being 3x longer than it needs to be the content is fine as far as I can tell, but I find the voice it’s written in extremely irritating.
I think it’s specifically the resemblance to the clickbaity writing style that Twitter threads and LinkedIn and Facebook influencer posts are written in, presumably optimized for engagement/social media virality. I’m not totally sure what I want instead, I’m pretty sure I’ve seen the same tactics used in writing I admired, but probably much more sparingly?
What is it that makes tptacek’s writing or Cloudflare’s blog etc so much more readable by comparison? Is it just variety? Maybe these tactics should be reserved for intro paragraphs (of the article but also of individual sections/chapters might be fine too) to motivate you to read on, whereas the meat of the article (or section) should have more substance and less clickbaiting hooks?
In theory they try to get people hired for their competence rather than their network. A widely-cited anecdotal example of this reportedly working well is the Rooney Rule: https://www.espn.com/nfl/playoffs06/news/story?id=2750645
This thread also has a lot of anecdotal examples of failure modes of 'diverse slate' rules, though, such as people who have already decided who to hire still interviewing women candidates just to appease the rule, thus wasting everyone's time.
key features implemented in a multi-process architecture, using plenty of C++ and Rust written modules
Which is exactly the point—the UI is written in HTML/CSS, not the native platform language, and the high-performance modules are written in C++ and Rust, also not the native platform language.
There are no second chances in the court of public opinion, no punishment severe enough, no act of restitution sincere enough.
This just isn't true. Look into how Dan Harmon gave a genuine apology and accounting for his wrongdoing and was forgiven. Can you point to Sabatini doing anything that even arguably rises to that level of contrition?
If learning that Cloudflare took action against literal, self-identified Nazis—who praise Hitler, deny the Holocaust, and drove a car into a crowd and killed a woman—made you worried that Cloudflare might take action against you, you're really telling on yourself.
I strongly disagree with the analogy between CDNs and ISPs. ISPs operate on the user-side, they have no business filtering what the user sees. CDNs operate on the server-side, they have the power and responsibility to decide who they want to do business with, and to not provide services to harmful customers—I'm sure we agree ISPs shouldn't provide services to harmful customers either (spam, malware, phishing, etc).
This is so overwrought. We're not talking about Embrace, Extend, Extinguish here, where Microsoft wanted to exploit their OS monopoly to bend the Internet to its will. Cloudflare's products are popular because they solve real problems; Cloudflare is not responsible for the popularity of outsourcing SSL termination, the difficulty of implementing SSL properly is, and if Cloudflare ceased operating tomorrow there would still be vendors and customers for SSL termination aplenty.
That's what domain fronting is for, and even though the GFW attempts to filter by SNI, genetic algorithms like Geneva are able to find workarounds: https://geneva.cs.umd.edu/papers/foci21.pdf
• a quick search for "refuting bell's theorem" will turn up attempts in 2000, 2007, 2011, 2012, 2017, etc, so let's take this with a huge grain of salt
• Europhysics Letters is a reasonably old journal (1986) but an impact factor of ~2 is pretty low; I wouldn't consider this a major journal
• As the Reddit discussion notes: "Just because you call your model locally realistic doesn't mean it's actually locally realistic. Calling it "contextual" doesn't change that. ... That part where the "context" of photon 1 changes the polarization of photon 2? That's not local.": https://www.reddit.com/r/Physics/comments/nig8d5/bells_theor...
The recent spike in homelessness, the health insurance coverage gap, rising economic inequality, we are facing many major urgent crises. But there is a severe lack of imagination to suggest that our problems as a society or species can't or haven't been far, far worse.
A homeless woman today in any major American city (which generally require hospitals to provide emergency care even to people without health insurance) is safer giving birth than a queen a few centuries ago. A homeless person today in any major American city is safer from cholera, tuberculosis, any antibiotic-treatable disease than a king a few centuries ago.
Society and technology have made us much better off overall, it's not close. The fact that we still have major problems today does not contradict the fact that we have also solved some major problems, too, thanks to science and technology.
http://github.com/laughinghan