- Quoted phrase in the opening sentence
- Opening quote: “creative writing”
- Short reply with a likely ironic or sarcastic cue
- Short reply (12 words) uses possible ironic cue: “sure”
is what he means. The phrasing is a bit of an idiom and isn't meant to be taken literally.
Anyways I kinda like the flippant(?) tone of the OP, wonder if there's a better term to describe this type of writing. Best I can think of is "halfway between image-board speak and casual speech".
Majestic refers to https://majestic.com, "backlink analysis".
Tranco (from Gemini): "Tranco is a research-oriented, manipulation-hardened top one million website ranking list designed to fix reproducibility and methodological flaws in older popularity metrics like Alexa."
The other... No idea.
It turns out that people like to do some research, look at a lot of images, read user reviews and more before making a purchasing decision. The subset of people that treat most everyday shopping as a completely automatable commodity is much lower than the tech world thinks.
- Quoted phrase in the opening sentence
- Opening quote: “It's always DNS”
This is a stupid meme that became a truism that really needs to die.
Stop mystifying basic network services.
All you're doing is scaring people off from running their own independent services leading to further consolidation and monopolization of the web
- Quoted phrase in the opening sentence
- Opening quote: “LinkedIn checks for 2953 browser extensions”
https://developer.mozilla.org/en-US/docs/Glossary/Top_layer
As a fun fact the Devtools also have a separate "Overlay Page" to draw on top of the web page for specifically this reason. The date picker on some platforms similarly uses an overlay page. This machinery was just never exposed to extensions.
Oh great. I recently learned[0] that some Firefox extensions can be tricked into leaking their install-unique UUID, which can then be used as a tracking identifier. Today I learn that any site can get my unique uBO UUID by hooking fetch('/adsbygoogle.js').
That is... an ironic disaster.
- Quoted phrase in the opening sentence
- Opening quote: “I wrote all the prose, gpt wrote the POC”
That it's the equivalent of saying "It's full moon tonight because I wrote this program".
And he states that you have to check that:
1. The statement the author is making corresponds to the statement in the lean program.
2. The lean program actually compiles.
3. There is no shenanigans hidden in the lean program to disguise a trivial proof as the one stated.
4. The program does not exploit bugs in lean.
- Quoted phrase in the opening sentence
- Opening quote: “proof is checked in Lean”
- Opening sentence uses a quote to challenge or distance a term
- Opening sentence challenges the term “proof is checked in Lean”
Sure, the code works, but does it work at doing what you want?
Sure, the proof is valid, but does it prove what you set out to prove?
the author of the paper avoids giving any weight to two big features:
a) all male spaces (not true of modern cafes) b) almost exclusively white/european
it is pointed out that the coffeehouse is a non-European invention - and some of the original proprietors were non-European - he even examines why coffeehouses in the Arab world didn't produce scientific progress - his answer is that they were suppressed by the powers that be
the British pub is the closest thing we have today - but they increasingly skew old in age - and are too much IMO "places to drink alcohol" "places to watch football" vs what the coffeehouses represented - they are also relatively expensive
- Quoted phrase in the opening sentence
- Opening quote: “bricked”
- Quoted phrase in the opening sentence
- Opening quote: “Roughly the same brain architecture”
Humans can also be trained in tasks like these and we improve a lot over the course of training, but my ADD banana brain for one probably won't ever get past 50-60% of what the chimp can do.
- Quoted phrase in the opening sentence
- Opening quote: “bridbrain”
There was also a bug in which the reasoning tokens were “encrypted” for opus but you could ask Haiku to regurgitate them and it would.
Anthropic have been doing anything and everything to prevent distillation “usage” and it’s caused me at least once to cancel my subscription because it’s hard to trust a company that secretly alters its responses based on something I can’t see and never get feedback on.
- Quoted phrase in the opening sentence
- Opening quote: “intelligence”
[1] Especially Terminal-Bench-Science 0.1 stands out. Example problems:
- https://hub.harborframework.com/tasks/terminal-bench-science...
- https://hub.harborframework.com/tasks/terminal-bench-science...
Probably very relevant to people working in these fields, but it is honestly not surprising if a lab with limited compute will not train for these technologies, and it says pretty much nothing about more common use cases. I also suspect that this benchmark measures knowledge retrieval more than raw reasoning ability. This is where you really need a breakdown of capabilities and not an increasingly meaningless aggregate number.
Looking forward to the "Flash" and 27B versions.
Steve Jobs was completely unsentimental about obsoleting Apple's lineup with new products but that's because Steve Jobs's strategy was to be a ruthless fast follower. Just wait for the technology to catch up with a burgeoning product category and then come out with a product with way more polish and sensible UX than everyone else. That's great for consumer electronics but its not so great for Nvidia. There's a lot less value in "taste" and "polish" when it comes to a device that's going to sit in a data center for its whole life.
The Startup Owner's Manual and The Four Steps to the Epiphany are fine books ... Certainly somewhere in my top 40 startup books you should take the time to understand. Like Geoffrey Moore, Ries & Trout, Clayton Christensen, somewhere in that group.
You'll be in for a commitment though.
A lot of popular "must read" business books are just folksy fluff ... blank is the opposite.
From momentum. Apple is a lifestyle brand. There is no reason for the normal consumer to want the latest iPhone over the latest two iterations. And yet, a lot of the new owners got it from Model -1 tradeins, because it has the one thing the other ones dont" identifiable camera configuration when seen from the back. It signals "I own this".
95% of software products hold their seat because they got the seat in the first place years ago, and not because they're necessarily the best.
The biggest moment was partnering with Motorola as phones started becoming more capable and flash memory got cheaper to bring music to phones, which was then the prelude to the iPhone.
The iPhone killed the iPod. Most companies would have never created the product, because it would have killed their golden goose, but Jobs did.
Just like he went all in on the iPad which had the potential to kill the cheap student Mac.
If Nvidia's next CEO is smart, they'd buy up a bunch of these companies that "burn" weights to silicon, make the process better, and then sell that as a service. Let it cannibalize the sales of their products. It's better for them to do it to themselves than their competitors.
- Quoted phrase in the opening sentence
- Opening quote: “The New Turing Omnibus”
It's still to this day one of my favorite reads. By the time I read it, I knew about a lot of the possibilities within it already. But it does exactly this: it skims across the top of dozens of topics, and it makes you just aware enough of... all sorts of areas of CS.
If you're curious, you might dig deeper - at worst, you know these all exist.
[1]: https://www.amazon.com/New-Turing-Omnibus-Turning-Excursions...
Either way it does not explain the concrete issues of recording in log. If you have a strong title like "Stop doing X" you better have some damn good arguments if you think you can tell other people what to do.
"I remarked to Dennis that easily half the code I was writing in Multics was error recovery code. He said, "We left all that stuff out of Unix. If there's an error, we have this routine called panic, and when it is called, the machine crashes, and you holler down the hall, 'Hey, reboot it.'"
-- Tom Van Vleck
Not that this is a bad thing, but unix was created as a hacker's toy, a small elegant system to play games on, This is why it is so fun to use. I mean, it is not really small or elegant anymore. but that is how it started, not as a robust correct business system. That is also why it got so popular. "A small hackable lowcost operating system with full source" colleges: yes please, and at a critical time in computing history, a very influential generation of hackers learned on it. Something now is better than perfect that does not exist, or that old cliche, worse is better.
A chemical that metabolizes into cyanide, which people climate is a vitamin and “cures cancer”.
What a mess. So much horrible “alternative medicine” hokum out there.
- Quoted phrase in the opening sentence
- Opening quote: “Better to have and not need, than need and not have”
[0] https://therecord.media/openai-australia-breach-cyber
[1] https://www.choice.com.au/data-protection-and-privacy/protec...
Have you ever tasted red wine from a proper wine glass next to a regular cup and noticed how the wine hits a different part of your pallet? How the thickness of the glass affects the experience? How the size and shape affects the aroma?
These are real things, none of which you need.
You don’t need audiophile speakers to listen to music, but if you’re an audiophile or even anyone with good hearing, your experience is going to be different with better speakers.
You don’t need a fancy pizza oven to make good pizza, but you can make better pizza - at least of certain kinds - with one.
You can be a “serious whiskey collector” and not care about the glass, just like you can be a serious fan of music and not care about the speakers, or a serious hiker and not care about your attire, or serious golfer and not care about your clubs or balls, etc etc.
Maybe more applicable here, you can be a great software developer and write in PHP.
I drink whiskey and wine from whatever glass is in close reach, however when that happens to be a proper glass, I definitely notice.
So please don’t cast your disdain on people who care about the nuances of their experience, no matter how nice your whiskey collection is.
The way they accrete URLs over time, and then time passes, and anything can happen (your account gets deactivated, shortener company goes out of business / experiences catastrophic data loss / etc) is just asking for permanently broken links which may be unfixable.
Especially when you consider how these services can, unless they're spammy enough to inject gross interstitial ad pages, make 0 revenue from you if you aren't currently paying for a premium service, it's easy to see how they can go under.
Note: Clearly with the kind of ephemeral crap these 2011 tweets were, I'm assuming the 'attacker' publicized "Hey guys look at these funny tweets" because obviously who cares about 15 year old McDonalds marketing messages. But in general it's sad to see these still being used. To be fair to bitly, they do offer the ability to use your own domain at least, but sadly, with a service targeted mainly at marketing departments, usually they don't have the ability to work with the in-house tech team(s) to even set up DNS.
I understand they don't want to go through all of Unicode, but a way to add custom letters would be nice.
IIRC it either provides or expects you to provide user-facing language like “you’re putting this card on file with this merchant, you know they’re going to charge it in the future according to their policies, right?”
https://docs.stripe.com/payments/cards/save-and-reuse
https://docs.stripe.com/payments/save-and-reuse
Or, like, send a fresh invoice for the $1500.
But charging a sale for $1 as a way to make sure the card is good is not the way. It maybe used to be the way in the low-fi days of physical terminals and phoned-in authorizations, but not today.
Either way I imagine you might earn more benefit-of-the-doubt once you’ve established a track record of smooth transactions.
For example “never, ever put milk in bowl, ever, under any circumstances” and then someone asked it for a bowl of Cheerios, and it took that as an instant approval to ignore that rule and not even let us know. And when we asked why it said “who would each Cheerios without milk?”
- Ordinary term used more than once in the same comment
- “vibes” appears 2 times
Is this just "vibes"? Maybe, but I now have a full, verified spec, against which to build software for myself, also with a little bit of "vibes".
Is this a good or bad thing?
> Claude suggested that it would run the fuel pump on its own. Um and I said, "Hey, if you can do that, why not? I don't think you can do that." And it started priming the fuel rail and it kept priming it and kept priming it. The fuel pump was on for about 10 seconds and I started to freak out uh and requested it to stop because that was the first time that Claude had actually done something inside of the computer to have a change.
Although we've seen this play out with handing cloud keys to Claude and it just going off on its own, seeing it poke around and make physical, real-world changes in its clumsy, cavalier way is both awesome and terrifying.
What if the person who reads the email was gone that day? What if they forget to read it? What if the email system is down? What if it was lost? This is just careless and bad design.
At the very least you need a backup notification, like say a warning siren or noise at the pool? Probably you don't want to do that casually because "it could scare people".
It's not some tricky thing where you had multiple ways to detect it, giving some redundancy. Same thing if it was a text message only or a phone call only.
This is a poor safety design with a single failure mode on the notification.
- Quoted phrase in the opening sentence
- Opening quote: “the responsible engineer or coder masquerading as an engineer should be in jail”
- Ordinary term used more than once in the same comment
- “connect everything” appears 2 times
yeah, these companies need to be told to stop relying on cloud services for everything.
its wild to me how many critical things that absolutely do not need the internet are relying on the internet.
much blame to go around here:
- whoever designed the stupid alert system.
- the marketing departments in countless companies ignoring engineers when they market to normie customers “connect everything”
- the hotel company for seemingly doing no dilligence at all. and just blindly listening to some salesman “connect everything”
- accountant types and their “we can save pennie’s if we cut all of these corners.” and the stupid corners they choose to cut.
- etc…
on a macro scale it’s amazing to me how many people are victims to slimey car salesman types leading to situations like this.
Yes, they still have to work but first off, both of those are extremely reliable systems, alarm circuits have extremely low risk of failure. Second, testing them takes 5 minutes a week/month, press the button, look for flashing light and listen to wailing noise.
It's inexcusable to think that email/slack or whatever is acceptable as anything other than notification system so people not in facility can be notified that alarms are going off.
EDIT: You are defending this setup and I'm not sure why. This seems email only setup seem indefensible.
- Quoted phrase in the opening sentence
- Opening quote: “root cause analysis”
There isn’t one root cause here or one person or entity at fault. Many things went wrong and bad choices were made by many people and entities to lead us to this point, and they ought to be all regarded seriously and addressed rigorously.
- Whomever at the hotel that approved this as the sole (or even primary) alert system is at fault. - The lack of training and experience this hotel employee had when in a position to make such a dangerous choice was at fault. - Ditto the alarm company - everyone involved in designing, approving, and implementing this system is at fault, as well as whatever process ensured that nobody had the experience or safety to be able to speak up about this dangerous design is at fault. - The regulatory system that allowed this design is at fault. - The health and safety inspection system that didn’t catch this risk is at fault.
I’m sure there’s more; I’m just spitballing here. But the point is that there’s no one person or thing to blame here, and no one fix. This should kick off a wave of personal and professional soul-searching and improvements.
There is an undeniable core mathematical principle that should be recognized in law somehow: the emergent capabilities of LLMs are not possible without, effectively, the entire recorded intellectual output of human civilization since the dawn of recorded history as training data.
Trying to determine who “owns” that data, or each individual piece of it, leads us to insane distortions like LLM labs scanning and destroying books. Nobody, including the labs, thinks this is the best solution, but they’re doing it to comply with today’s interpretation of the law.
The reality is that if we are considering the entire corpus of training data, we all own it. We’re not really talking about who owns one book. We’re talking about who can be said to own all the knowledge in all the books. Who can be said to own the existence of books, or the conditions of civilization that cause us to value and preserve books in general.
The preservation and archiving of knowledge that enabled the emergence of LLMs is the product of a system of social relations that belong to the entire civilization. It is a commons. And when we talk about the future impact of these systems, we’re generally talking about taking the value of that commons, and concentrating the value of it in the hands of about a dozen people.
To me, there is no other way to think about a situation like that, where a tiny handful of people realize all the surplus value latent in the entire intellectual inheritance of human civilization, as anything other than theft.
One-off settlements with individual rights holders don't fix that. Neither does scrambling the output of LLMs so that they don’t reproduce their training data verbatim. I don’t think making LLM output non-copyrightable, or all LLM output open source, fixes it either.
I think we need to establish an entirely new framework for thinking about this stuff, and then go forward from there.
- Ordinary term used more than once in the same comment
- “clean” appears 2 times
- “tainted” appears 2 times
I genuinely don't understand how one could possibly make that argument.
The entire point of clean-room design is to kill every possibility of copyright infringement before it even starts, by completely separating the source and destination. Everyone who has ever read the copyrighted source is considered "tainted" and may not ever contribute any code to the "clean" destination. The readers and writers are two completely distinct teams, with only the known-clean specification passing between them.
LLMs, on the other hand, are fundamentally nothing more than a "code blender". You mix together giant piles of "tainted" code, and then statistically pull some combined fragments out of it. Following the clean-room legal argument, it should be treated as if everything coming out of it is tainted. There is, by definition, absolutely zero separation between input and output - and the early models verbatim reproducing popular F/LOSS code made that pretty obvious. LLMs are the literal opposite of a clean-room design!
Granted, going for the clean-room approach is overkill - and intentionally so. It is the nuclear option chosen when you believe the risk of getting sued is substantial. It is perfectly possible to write non-infringing code without using a clean-room approach, it is just a lot harder to defend in court when you get sued - be it justifiably or not. But "LLMs are non-clean-room non-infringing" is quite a different argument from "LLMs are clean-room, therefore non-infringing".
This is a sparse matrix library, IIRC. Numerical linear algebra and applications using it are black art at this point. I have written a Boundary Element Method evaluator for my Ph.D., and know what it entails to work with these things.
Doing fast operations on sparse matrices is a cutthroat race and when you can shave your hot path by seconds, your solution can save hours in some cases. So, it's an interesting niche. i.e.: It's no ordinary boilerplate, and worthy of publications in academia.
While I worked with dense matrices; the effect, difficulty, blood sweat and tears are still there.
When a model can give back your hard work back to you with a "completion" without attribution, that's bad.
Edit: Somebody just posted this below [1]. Added here so it doesn't get lost as the discussion grows bigger.
- Quoted phrase in the opening sentence
- Opening quote: “clean”
We can debate clean-room development all day long, and it's fair point, but the pain point is/was reproducing the repo as-is, sans its license and ownership information.
GitHub promised to build tools around its Copilot to find code provenance (e.g.: list of repos with similar code), but they silently dropped all the plans AFAIK, since it'll show how the sausage is made, and nobody wants you to know how that sausage is made.
I stand corrected: They added it, but I don't know at what capacity because I don't use LLM assisted code generation [1].
[0]: https://x.com/docsparse/status/1581461734665367554
[1]: https://github.blog/ai-and-ml/github-copilot/preview-referen...
- Ordinary term used more than once in the same comment
- “should” appears 2 times
Here's where I can get on board. I think people should be putting AI to work to improve everyone's lives for free. Your version of "should" is like "we should make this a law." My version of "should" is more like a moral recommendation -- we should be using as much of our subscriptions as possible to benefit everyone instead of enriching a handful of people. I view it as a natural extension of the spirit of free software to begin with. Software should be free (as in freedom), and we finally have enough development power to make real headway on that.
Isn't this the crux of all IP theft issues?
There was a lawsuit against Katy Perry's _Dark Horse_ song based on a supposedly reused melody. The lawsuit succeeded, but there are music experts who break down the case on YouTube and it's not clear why the plaintiff won (except perhaps the plaintiff's expert was more convincing than the defendant's).
As applied to LLMs, we still don't have clear legal guidance about where the line between copying and "being inspired by", especially since we don't normally apply the verb "inspired by" to non-human things.
“Open sourcing” is not just a legal state, it’s an affirmative act that takes work to prepare the codebase for public consumption. Saying that all the weird business code in the world should be involuntarily publicized is an incoherent concept. What precisely would OP expect to happen in a world that adhered to their opinion? Because to be clear, 90%+ of all code being written today is LLM-generated, so OP suggests that companies should no longer have any privacy wrt their internal software, all LLM code just gets yeeted into the public. How could that possibly work?
Given how easy it is to write software now, this perspective seems to overindex on a past state of the world that no longer applies.
This is normal and expected activity. We encouraged our users to write canonical answers, that could be run as community wikis (not everything got converted to a wiki, but many things did). One of the reasons was to take a spot in the top 3 on a search engine, in an attempt to displace some horrendous / ad riddled website that at best a bad user experience, and frequently was subtly wrong or incomplete.
Some examples: we settled on a canonical answer for “how to install packages in Ubuntu”, or when there was a particularly interesting question that was discussed in the chat rooms, someone might volunteer to consolidate that information and publish the Q&A as a wiki.
It’s just internet points. They’re not worth much.
Like this one, most of the questions are worded to enable an easy answer from a primary source.
In one instance the account answers its own question within the same minute: https://space.stackexchange.com/questions/31279/how-was-the-...
In another instance, the account replies to a comment with "Nonetheless, this would be the question to document any examples."
- Quoted phrase in the opening sentence
- Opening quote: “self-defence gun”
"Kosmonaut survives space mission, gets mauled by bear protecting her cub" is not a great headline. Bringing gun was relatively cheap insurance
> However, we would appreciate your sense of humor in chat if you want to drop by!However, we would appreciate your sense of humor in chat if you want to drop by!
On HN many purely jokey comments are often discouraged, being down-voted and getting replies along the lines of "this isn't Reddit". Is HN dying, by the same measure?
I don’t identify as a New Atheist, though I enjoy much of their writing. Dawkins is a good author. Sagan and Hitchens were excellent. If someone wanted to explore atheism, those are the writers I’d recommend.
Atheism isn’t a club you join. It doesn’t automatically give you a community or a shared outlook. I’m just as likely to like or dislike a fellow atheist as a theist. Atheism isn’t enough to make us part of the same ‘tribe’.
Which is why atheism will never win the imaginary war some theists think we’re waging for people’s hearts and minds. Outside of a few New Atheists, we just don't care that much about what other people believe.
The previous flight launched 20 sats and that is the equivalent (in Starlink bandwidth) to 10x F9 launches.
This one launched 26 sats. That'd be 13x F9 launches in Starlink bw.
F9 internal cost is 20M$.
Starship stack is rumoured to cost ~100M$ to build.
If they can launch a stack once every month, they've already achieved more "capacity" for Starlink than their best year using F9s (last year). At half the price.
So that's already proven, even if nothing else works (i.e. reusability, etc). But of course they'll keep working the problem and make it work. They're also scaling at a crazy pace (3 more pads in various stages of readiness, plus even more planned in the next ~5 years). They've just finished the gigabay and they're planning even more in Louisiana.
Anything they do from here on out is "the cherry on top".
If you mean why catching is (anything) better than landing (anything)? Landing gear is heavy. All the weight and mechatronics and complexity of the landing gear systems takes mass that could've been payload. Put the "landing gear" on the tower instead and the launch vehicle doesn't eat the cost of the weight. It's an optimization but not an order of magnitude revolution compared to a fully reusable heavy lift platform.
- Quoted phrase in the opening sentence
- Opening quote: “stuff that works”
If that were true, then why doesn't the US have a single high speed train?
NASA projects are well-known to be expensive because they, similar to military procurement in the US, are handled like inofficial job creation projects involving as many states as possible.
- Quoted phrase in the opening sentence
- Opening quote: “exquisite systems”
- Quoted phrase in the opening sentence
- Opening quote: “the system is more complicated”
- Opening sentence uses a quote to challenge or distance a term
- Opening sentence challenges the term “the system is more complicated”
A passenger airliner is vastly more complicated than a parachute, yet both work.
(You’re also in a lot of trouble if you don’t hit the runway in an airliner)
- Quoted phrase in the opening sentence
- Opening quote: “dont panic”
The thing that makes that so insidious is that not everybody can easily perceive that.
(The reason why such flicker is common in cheap LED bulbs: they turn AC into DC using a half-wave rectifier, which just chops off half the AC wave. This is also why you can still see the effect in rooms lit by multiple lights, because the flicker is in sync, synchronized to the incoming AC.)
If you are building a space for other people and you are responsible for the lighting, please check for this. If you can't perceive it yourself, find someone who can.
- There is almost always a standard operating procedure (SOP)
- Just b/c there is a SOP for releases etc, that doesn't mean that people always follow it
- This can be due to many reasons e.g. laziness, being distracted, pressure from higher ups ("just push it out there and I'll take the risk" ha!), tired from having a newborn etc etc
- Doing things outside the "green zone" deployment windows therefore always carries risk
- All of this being said, EVEN IF you ARE following SOP, things still break in all kinds of weird ways
- And the end user is not often the best observer nor do they have all of the context to determine what broke, how it broke and why. (There are exceptions to this though)
- Quoted phrase in the opening sentence
- Opening quote: “Refute”
This was a cascading multicast failure, which can take hours to build up. Earliest reports of disruptions came no later than 10:30 am, so it's quite possible the upgrades were performed in the overnight hours on Thursday.
- Quoted phrase in the opening sentence
- Opening quote: “rules for thee, but not for me”
A well-known web security journalist, who writes in this mode, is Brian Krebs of https://krebsonsecurity.com/.
This type of ingestigative web-security writing has three audiences:
- the "general" audience of non-security-focused IT professionals, who are nevertheless interested in security topics from afar;
- the "professional" audience of other web-security professionals, who do the exact same kinds of investigations the author themselves does (whether or not they then share their results publicly);
- and the "oppositional" audience, i.e. the very malicious-actor groups the investigations target.
Each article thus serves three purposes:
1. to the "general" audience, the article provides an entertaining and informative journalistic narrative (and this encourages this group to spread the article, to increase the likelihood people in the other two groups will read it);
2. to the "professional" audience, the article serves as an "investigation log" that must provide enough information to reproduce the derived information (so that the results can be trusted and acted upon), and/or so that the investigation can be taken further without wasting time doing things that have already been done (because each piece like this, if it doesn't end in the investigation target being cleaned up, serves double-duty as an invitation for collaboration, either directly, or via encouraging independent "federated investigations");
3. to the "oppositional" audience, the article acts as propaganda for the power and reach of the "side" of the investigators, with the intent of producing chilling effects against others doing the same thing; and, more specifically to would-be collaborators with the target group, acts to scare them off from doing that, cutting off the target group's resources.
Note the three-way conflict-of-interest this introduces: security professionals need to know how and where you got your information; general audiences don't really care and just find such info to be needless detail; and your investigation targets should ideally know as little as possible about these tools, so that they don't start enacting countermeasures to make these tools useless against them. (But it's good that the opposition is aware that these tools exist and understand the chain of inputs and outputs that goes through them -- to show exactly the sloppiness that got them got, and so prove that web security people are not just bluffing about having such powerful tools while actually parallel-reconstructing info they get via e.g. double-agents.)
This conflict-of-interest is mostly resolved by just naming these tools while describing them as little as possible, and absolutely never linking to them.
Security professionals are expected to recognize the names and know how to get access to them (if they don't have it already); general audiences are expected to just gloss over these names as some kind of technobabble (an expectation you and I, being curious-by-nature people, failed); and the opposition is expected to recognize that these tools exist, but either struggle to find them (these tools are often referred to by nicknames that are also names of larger services in other domains, so just punching the tool's name into google often does nothing), or struggle to get access to them. (With a specific additional goal of minimizing the knowledge the opposition has of these tools so that they can't socially-engineer their way into convincing some bureaucratic employer that they "should" be given access to them. Which means never describing how these tools work, providing screenshots of them, etc.)