gojomo

Poe's got enduring relevance for our era of unreliable narrations. His 1845 short story 'The System of Dr. Tarr and Prof. Fether' – set in a private mental institution – popularized the adage, "Believe nothing you hear, and only one half that you see."

In our era of generative AI, that needs a small update – "Believe nothing you see or hear, and only half of that over a strongly-authenticated channel from a reliable source". But the story's themes of communities-of-mental-illness and blurred boundaries between doctor and patient (or between therapy and enablement) still resonate.

Is there a risk that other projects that may be using the same cyphernet-labs/netservices.rs code, like Nym & Farcaster, have also been expecting authentication & encryption where it hasn't been happening?

And having a 0.3mg (300mcg) group - the dose many meticulous online self-experimenters have found sufficient, a mere 15% of their lowest-tested 2mg.

Would a headline "morning coffee found to cause stomach problems and anxiety" be reasonable, if the smallest dose tested was 7 cups – and that dosage fact was omitted from the attached abstract/story?

If people are complaining about Anthropic (on an only-vaguely related thread) rather than simply switching to a suitable competitor, then Anthropic clearly has some 'monopoly' power over the specific capabilities the complainer wants from them.

War of the Worlds is culturally-prominent enough I doubt any commercial AI would make this same mistake (or let the error slip through, if they'd asked the AI to fact-check the article).

Because I think readers should take this as an illustrative example of how often people/institutions draped in such quasi-credentials are carelessly wrong on basic things.

Even if some typo of 'malevolent' becoming 'benevolent' was how this error initially created – & I have my doubts! – how many people had to be asleep at the wheel for the truth-reversing error to get published, & persist for months? Does no one at the CBC – with pride in its work & any familiarity with these topics – read CBC's slop?

Have you independently checked all the other allegedly "factually correct" info in this article, with other sources that are actually diligent in getting the details right? What's the incremental value of a news source where every detail that you don't already know might be very wrong?

I see this author has "12 honorary degrees and is an Officer of the Order of Canada". And CBC is Canada's government-funded national public broadcaster.

But it's hard to take them seriously on any particular details given that their article, up for 8+ months (!), mis-describes H.G. Wells' War of the Worlds as a story of the Earth "invaded by benevolent Martians". [emphasis mine]

It's a seminal work of scifi, which popularized the "alien invasion" genre and term "Martians' (both for literal creatures from Mars and also a metonym for any alien visitors/invaders). It's been adapted to film many times. And the Martians in it - with their disintegrating heat-rays & death-clouds, consuming human blood – are far from 'benevolent'.

Distillation done via bulk automated activity of fraudulent accounts, in violation of a terms-of-service, can reasonably be called a "an attack" – specifically a "distillation attack" – even though distillation itself isn't necessarily an "attack".

This is similar to how compromising an account through bulk automated trials of many passwords is reasonably called "an attack" – specifically a "dictionary attack" – even though using a dictionary is not itself an "attack".

You shouldn't need to smuggle your sympathies (for the tactic or perpetrators) or antipathies (for the target) into peculiar judgy language prescriptivism against common, understood usages.… that then label Reuters "complicit" for simply reporting Anthropic's claims accurately. That's what Reuters is supposed to do, in a story about a letter Anthropic wrote!

Twice a year, typically to see how fast my own submission is sinking into obscurity.

Smart guy but whoever eventually actually fixes X search will probably use AI coding assistance to do it.

I don't see how your example, The Browser (thebrowser.com), supports your argument that ad-hoc query-string additions are so prone-to-breaking that 3rd parties should ban them.

In fact, the example seems to suggest the opposite: a 17+ year successful paid subscription business – to which you appear to be a generally-satisfied customer! – receives enough "business value" from the practice, despite its failure modes, they don't want to stop. Improving their probe of the risk-of-failure was enough.

Seemingly, the practice works often enough, pleasing more destination sites than it angers, that "referral tracking" is not something "so minor".

In fact, you usually can just send arbitrary query string parameters to a server - that's why the behavior is so common, and often useful.

Most sites don't mind or break, some sites get value from the behavior in ways hard to replicate in other ways – and those sites that don't like such additions can easily ignore them. And a few lines of code will work better than ineffectually appealing to manners, when the freedom of the web's form of hypertext, and protocols, gives the outlink authors full freedom to craft URLs (and thus requests) however they like.

Trying to boostrap some taboo against novel unpermissioned URL munging is silly prudishness.

Ensuring both sides of a hyperlink agree/consent was a design flaw that limited the uptake of pre-web hypertext systems. The web's laissez-faire approach demonstrated a looser coupling was far better for users, despite all the new failure modes.

Of course any site/server has the practical power free to treat inbound requests as rigorously (or harshly) as they want. But by the web's essential nature, it is equally part of the inherent range-of-freedom of outlink authors to craft their URLs (and thus the resulting requests) however they want. URLs are permissionless hyperlanguage, not the intellectual property of entities named therein.

Plenty of sites welcome such extra info, and those that don't want it can ignore it easily enough – including by just not caring enough about the undefined behavior/failures to do nothing.

Though, when a web publisher has naively deployed a system that's fragile with respect to unexpected query-string values, they should want to upgrade their thinking for robustness, via either conscious strictness or conscious permissiveness. Thereafter, their work will be ready for the real web, not a just some idealized sandbox where scolding unwanted behavior makes sense.