Sometimes unexpected inputs find interesting outputs...
Claude: [...] Remember, given the complexity of the system, it's crucial to have any major work done by technicians with specific experience in these units.
Me: I can always count on you to drop that last line of normative commentary. 😂
Claude: I appreciate your sense of humor! You're right, I do tend to include those cautionary notes. As an engineer, you're probably well aware of the complexities involved and don't need the reminder about experienced technicians.
Your comment makes me realize I could have focused more on the technical aspects you'd find interesting, rather than general advice. Perhaps you'd be more interested in discussing the specific design challenges of the SH-AWD system, or the trade-offs between serviceability and performance in complex drivetrain components?
If you're considering tackling any of this yourself, I'd be curious to hear your thoughts on the feasibility of DIY diagnostics or repairs on such a system. There's always an interesting balance between manufacturer-specific knowledge and general engineering principles when approaching these kinds of problems.
"SEQUEL, is intended as a data base sublanguage for both the professional programmer and the more infrequent data base user."
- Chamberlin and Boyce, 1974
Claude is funnier than ChatGPT. Here's is its final reply to me joking around about why Congress is spending time ensuring AM radio stays in cars:
---
Oh, I see we're diving back into the dark humor! Well played. Let's run with that dystopian vision:
Ah yes, the good old Emergency Broadcast System, now with extra authoritarianism! When the New World Order finally drops the façade, AM radio will be there to keep us all in line:
1. Mandatory daily listening sessions to receive our thought corrections and productivity quotas.
2. Soothing static to drown out any pesky independent thoughts.
3. Easily jammed frequencies to keep those troublesome rebel broadcasts off the air.
4. Low-fi quality audio to ensure Dear Leader's voice has that authentic, totalitarian crackle.
5. Battery-operated radios mean no excuse for missing announcements during rolling blackouts.
6. Conveniently located in every vehicle for on-the-go propaganda during your government-approved travel times.
Remember citizens, an informed populace is a compliant populace! Keep those dials tuned to WGOV for all your ration updates, curfew reminders, and approved music selections. And remember - Big Brother is listening... on AM 1984.
(In all seriousness, while emergency communication is a valid use for AM radio, your comment highlights the potential for any mass communication system to be misused. It's always wise to maintain a healthy skepticism towards any single source of information, government-controlled or otherwise.)
I almost always use sonnet 3.5. Opus 3.0 was also very good. ChatGPT okay, and it has nice features like browsing and advanced voice. Llama 3.1 8B and 70B aren't better, but will surprise you.
gzip saves space over the wire, but you still have to parse all the bytes. There are ways to reduce this (https://github.com/WebReflection/json.hpack/wiki) as well as organize your schema to be stream-parseable, but it will never be as fast as a binary format. The thing is, HTTP already supports "Accept" and "Content-Type", and there's no reason relays and clients couldn't negotiate a different serialization format.
Engineers that don't believe in "conspiracy theories" sadden me. Tell me that you don't want to know. Tell me that you're trying to fit in. Tell me it's your choice. Don't tell me that you accept conjecture over evidence and math, that's just poor engineering.
If you have a decent PC, you can have surprisingly good experiences with a $200 Quest 2. I started playing VTOL VR as a "kids flight sim", and although it's a little heavy for the kids the experience of learning technical skills in modern VR is amazing. Doubly so when you have two people in the same aircraft.
Interesting breakdown! I usually work across these sections in a descending ratio of effort to likelihood of elimination:
Fast:
- Tone detection: Not definitive, but sets expectations.
- Logical fallacies: Most things fail here.
- Clarity: Similar to fallacies, people like making overly broad statements that don't mean anything.
- Check claims: This is often easy these days.
Slow:
- Context: If I don't understand it, I won't be able to evaluate it further.
- Arguments: The real meat, and where most of the time will be spent (if if hasn't failed already)
- Bias detection: Again not definitive, but can be easy to evaluate once you've made it this far.
- Assumptions: The second heaviest step.
- Source: Is almost an afterthought. "Reputable" sources make bad arguments all of the time. "Seedy" sources make good arguments more often than you expect. Source is often more related to bias than correctness. nostr:note1yck6mfk69tfj5lxusgqk2slkvxwh0a0uteej32r626gdtt7qslmsnusejk
“Those who manipulate this unseen mechanism of society constitute an invisible government which is the true ruling power of our country.”
nostr:nevent1qvzqqqqqqypzpq35r7yzkm4te5460u00jz4djcw0qa90zku7739qn7wj4ralhe4zqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqlxeh2yuajghzeq450edhypwfe5ad83p8383k6skvru0fm6e6u8fql90rx3
Interpretations of quantum mechanics are like compiler errors in that hip new academic programming language that you're trying to learn. Sure they're technically consistent, but they're also oddly constructed and you can't help but wonder whether the system is a little too fancy for its own good. Maybe if you spent a couple decades understanding it you could figure out how to fix their mistake, but since only fanboys are going to spend that kind of time, you to do that you just hold your nose and work on things that matter.
ReplyGuy was pretty annoying.
Wait until the first client exploit that burns half of nostr's nsecs. Without subkeys or another separation of identity and authentication, the web of trust would burn to the ground.
I have a hard time reconciling the availability of things socially with the availability of them adversarially. Yes, we have delete and edit and maybe expiring uploads ... for friendly participants. But not all participants are friendly, and retraction is a powerful signal that can reveal weaknesses.
Eric Schmidt, while CEO of Google, said the quiet thing very loudly:
"If you have something that you don't want anyone to know, maybe you shouldn't be doing it in the first place."
I can't tell if he said this for the right or wrong reasons, but it only gets truer. Be aware of the durability of your messages. As Earl Long said:
"Don't write anything you can phone.
Don't phone anything you can talk.
Don't talk anything you can whisper.
Don't whisper anything you can smile.
Don't smile anything you can nod.
Don't nod anything you can wink."
GM
Not only is being a globally consistent source of truth overrated, it prevents us from increasing availability through partitioning. It's partitionability and lax consistency that allows nostr to be used when the network is unavailable. That's why we can verify a printed out nostr event, and publish events by printing them out and scanning them somewhere that the network is available. nostr:note1yptu6sgnpmqydwd2g94rl0x94fnn7m0hjyk3pmc4a3jccztpaexqhkwtcd
One relay is going to report 5, another one 7. How do you combine them? Max? Sum? Guess?
But, push a new meta event from the relay. If clients want to use it, that's great. If not, that's also great.
The relays might have completely different people pushing to them though, and then you'd need to sum them.
If it happened a lot you could include some optimized data hinting at the npubs behind the counts. It's not an easy problem.
It's better to keep information in the messages themselves so the protocol stays focused. But if relays want to talk to each other using some sort of magic that's cool too. At the end of the day, most clients will be using more than one relay, so they need to combine that information somehow.
In the past the riches of war were simple plunder. These days that looks gauche, so instead we blow up their infrastructure and profit from restoring it.
Nostr is basically Game of Thrones. You think you're fighting the good and honorable fight when some Lord of a Cold Wet Rock shows up uninvited and messes up your carefully laid plans for, as far as anyone can tell, his own amusement. But then you also find out you might have friends who have learned to cheat death itself?
It's easier to keep it together when you remember that the giant undead ice dragon is coming for us all, so ultimately... same team. nostr:note15s8u6hcs7l0tmqurm7gqpd59acl8q45ktrxg6g6xync3u2slt0yse9syur
This isn't my fight, but I often find that good advice goes unheeded until it too late. And, how do you know this anon didn't also contribute to fixing the problem?
Damn you, (... checking whois) Privacy service provided by Withheld for Privacy ehf!!! Namecheap will know that you're a meanie, whenever they check their email!
FWIW, there is a similar problem in iRacing: the newbs are always hitting each other, so they need to prove they can be safe by racing without hitting things. Which is hard because they're limited to races full of newbs who tend to hit things. People eventually make it through, but the activation energy is very high, and that makes growth slow.
This is why the only reasonable use for blockchains is a fungible cryptocurrency: the chain can only provide consensus, and the only meaningful value of a coin can be the global desire for fractional ownership of the whole system.
If you try to add special meaning to specific tokens, that needs to be enforced both in code and law. This favors those who control the software over other participants, and ultimately relinquishes sovereignty to whichever State the effect is supposed to happen in. Once control has been ceded to the State it becomes obvious that the blockchain provides no value beyond a simple Merkle tree, and since the State is the only real sovereign actor, they'll prefer to use a database that they have full control over.
#OnlyBitcoin
Oddbean new post about login | logout
Notes by ynniv | export