dc396

Mostly agreed. In a previous life, I used to write code, then got Peter Principled upwards to the point where I "trusted" the engineers under me to do their job. Did I understand all the code my team wrote? Of course not. Even if I wanted to review all the code written by 20+ developers to the point where I could stay I understood it, there simply wasn't enough hours in the day to do so.

I figure what is happening is (human) software engineering as a discipline, at least on large scale projects, is rapidly and irreversibly mutating to software project management. But instead of managing teams of people, you're managing teams of agents. Where I disagree with your comment is in the assertion that everyone "can move one level up the system hierarchy." Some folks can't, so they'll stagnate. Welcome to the Peter Principle World.

Elections have consequences. I doubt anyone rational would have thought it would be a useful expenditure of time to get into this particular pissing match, but here we are. Maybe in the next presidential election the 87 million eligible voters who chose not to vote in 2024 might choose to participate.

This is a troll, right?

This would argue that change of ownership of a domain should be treated equivalently to creation of a domain. Of course, given GDPR (or rather how the registrars have chosen to interpret GDPR to reduce their legal liability risk), ownership information is now unavailable, so all you have to go on is the registration modification timestamp. Unfortunate.

I'm curious: can anyone provide an interpretation in which this agreement does not boil down to surrender by the US?

California has 11x the population of Utah, with California having around 250 people per square mile and Utah having 40 people per square mile. This probably plays more into the fire risk than the number of pine trees.

> And why is California uniquely fire prone?

Combination of CA's climate (mediterranean), which leads to hot/dry summers exacerbated by global warming, natural ecology that evolved to handle that climate and fires (e.g., lodgepole pines can't reproduce unless a fire cracks open pine cones to release seeds into ash beds), the topology that funnels winds off the deserts, and probably most importantly, people, either because of building in places that have lots of fires or because they cause the fires directly or indirectly (transmission lines not buried, lack of control fires, arson, etc.)

Science? Maybe in an ideal world. However, how science actually gets done has always been at the mercy of social, cultural, institutional, and/or economic pressures.

Congress neutered itself, largely because it has been politically less risky to let the Executive branch do whatever they want, then either cheer it on or rage against it depending on party and what drives donations so congress members can get reelected.

The system is fundamentally broken.

No. It's been a while, but I believe if you use multiple TXTs, resolvers can reorder them as they see fit. For example,

label IN TXT "foo " IN TXT "bar " IN TXT "baz"

You can have any number of TXT RRs with a label, allowing up to 65,280 bytes. However, resolvers can reorder those 3 TXT RRs.

If you put the text strings in quotes in a single TXT RR, e.g.:

label IN TXT "foo " "bar " "baz"

You'll get "foo bar baz" and each of the strings can be up to 255 bytes. I think (but I'm too lazy to verify) that the maximum length of a concatenated string is implementation dependent.

"The length limit of a DNS TXT record is 255 characters."

Nope. That's the maximum length of a TXT record string. TXT record strings with the same owner name get concatenated together. The maximum for a TXT record is 65,280 octets (which may or may not translate into characters depending on encoding).

Also, you probably want to think about the implications of caching and TTL.

Seems the Trump administration is trying to use 1984 as a how-to:

“And if all others accepted the lie which the Party imposed—if all records told the same tale—then the lie passed into history and became truth.”

My understanding is that this NDA is far broader in scope than CUI. CUI restrictions only apply to information explicitly marked or identified as CUI.

The draft NDA would apply to “confidential government information,” defined much more broadly than CUI to include non‑public internal operations, personnel matters, deliberative or pre‑decisional materials, and other information an agency deems sensitive, whether or not it falls under existing CUI categories -- it's an open-ended personnel instrument defined by the administration rather than an information handling regime tightly anchored to statutory/regulatory bases than span administrations.

In other words, it's a tool to allow the administration to go after someone who leaks anything the administration doesn't want leaked for open ended reasons.

[oops. That was intended as a response to Jtsummers]

For one version of this, see: https://en.wikipedia.org/wiki/Eternal_Sunshine_of_the_Spotle...

How many people in NYC that are buying raw milk do you think are doing so to make cheese or kefir?

If DJB is "hated", it isn't because he's a lone author (Linus Torvalds was once a lone author and I don't think he was hated). It's because he can be an asshole. To quote George Bernard Shaw, “The reasonable man adapts himself to the world: the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.”

Oh joy. Now the volunteers maintaining the IETF RFC tools get to waste their time trying to prevent folks who think it's cute to litter all over the IETF drafts.

I suppose it was inevitable. Another reason why we can't have nice things...

I was hoping someone had just shown that DNS was Turing complete (extending https://web.cs.ucla.edu/~todd/research/hotnets21.pdf). Using the DNS as a remote file store isn't as interesting.

Some quibbles:

- TXT records were intended as a catch all for stuff that didn't have a resource record officially defined. Their use in email authentication came (much) later and, arguably, for bad reasons (there was a record defined for one form of email authentication, SPF, but folks in the IETF thought it was too hard to have client libraries and DNS server user interfaces updated to support it, so they decided to use TXT instead).

- You can fit more than around 65,280 bytes in TXT records, not "about 2,000 characters of text" (Maybe the 2000 limit is a limitation of Cloudflare?)

- If you control the authoritative server, you could, in theory, chain an unbounded number of names within a zone, e.g., 000001.example.com, 000002.example.com, etc., to store an unlimited amount of data.

- Or, you can use open resolvers as a file store (https://blog.benjojo.co.uk/post/dns-filesystem-true-cloud-st...)

See "inflation". Look at the outcomes of countries who remove controls on printing money (e.g., Zimbabwe, Venezuela).

You mean the ones that are the result of experience through controlled clinical trials with statistical analyses and error bars, yep, sure. I guess I have a bit more faith in those leaflets and the testing regimes that generates them than the word of some gymbro or influencer who injected themselves and didn't immediately fall over dead.

> Ok, and?

According to our new AI overlords, a short synopsis of potential risks of BPC 157 based on mechanistic and animal work to date (don't know human risks because there haven't been sufficient clinical studies):

* Possible pathologic angiogenesis (abnormal blood‑vessel growth), which theoretically could support tumor growth or inflammatory and autoimmune processes. * Modulation of nitric‑oxide pathways that, at high levels, might contribute to anemia, altered drug metabolism (CYP enzyme activity), and possibly neurodegenerative processes in theory. * Concerns that its pro‑healing, pro‑growth signalling (e.g., FAK–paxillin) could encourage cancer spread if malignant cells are already present; this remains theoretical, with no proof in humans. * Possible liver and kidney toxicity suggested in some commentary and extrapolated from preclinical work, but not well characterized in people. * Immune reactions or allergic responses, including fevers, rash, hives, muscle aches, or systemic inflammatory responses

These do not appear to be results that would appear overnight. It would be "nice" if the folks injecting random shit into their bodies also disclaimed any subsequent medical intervention as a result of said shit, but that I suspect that's unlikely.

> It is very safe and tolerable.

Can you point to the clinical trials that demonstrate this?

> Doctors seem to be giving GLP peptides out like candy and those are injected.

There have been several _thousand_ clinical trials that have shown GLP-1s to be safe and effective.

Loans, mostly.

Artemis costs about $4 billion per mission, with around $90 billion already spent. The war in Iran is costing the US about $1 billion per day, so (as of today), $35 billion spent.

The US debt is $39,000 billion ($39 trillion). So, combined, the entire Artemis program and war in Iran represent .32% of the US debt.

/remind me after the 2026 elections.

This is a bit like saying sound waves have no attribution layer for music.

The Internet is a transport medium. It sounds like you are asking if it possible to (somehow) associate universal, intrinsic, and immutable attribution metadata with some or all (not sure what "viral" distinguishes in this context) Internet _content_ and have all receivers of that content accept the implications of that attribution metadata.

I think the failure of pretty much all the various digital rights management efforts applied on a MUCH smaller scale to infinitesimal subsets of content types that are now being schlepped across the Internet would suggest that no, there are no technical approaches that would realistically work.

And music, film, and television ownership/credit being tracked carefully? In certain law abiding environments, it's possible the owners/creators get a small fraction of what they believe they are entitled to, but in the majority of the world, not so much.

Was wondering how long it'd take you to come in and trash talk DNSSEC. And now with added FUD ("and once you press that button it's much less likely that you're going to leave your provider").

At least you're consistent.

I signed up for a Pro account yesterday, now when I try to access it, I get shuffled off to the 'create a new account' page.

Trying to access a human in support to understand wtf has been going on, perhaps unsurprisingly, has been a study in infuriation. Their AI support bot has been as useless as most other AI support bots.

Sending email to their support email address triggers the same AI support bot. It suggested waiting 24 hours and trying to access my account again. And then closed the issue after 4 hours.

Probably not related to the email delivery issue (I keep getting the link via, it just redirects to the create new account page), but perhaps indicative of something seriously broken and a lack of interest in actual support (even for paying customers).

As others have pointed out, using 'tmptest' works until someone buys tmptest -- unlikely, but people will buy anything these days.

I always use the ISO-3166 "user-assigned" 2-letter codes (AA, QM-QZ, XA-XZ, ZZ), with the theory being that ISO-3166 Maintenance Agency getting international consensus to move those codes back to regular country codes will take longer than the heat death of the universe, so using them for internal domains is probably safe.