> the clitoris did not even make it into standard anatomy textbooks until the 38th edition of Gray’s Anatomy was published in 1995.
This seemed surprising, as it hews too close to an annoying meme in feminism and history generally, that people in prior eras were idiots. And it turns out to be wrong. The clitoris was in Gray's Anatomy until 1947, when it was removed by the editor Charles Goss for the 25th edition. See https://projects.huffingtonpost.com/projects/cliteracy/embed... Indeed, the clitoris had been depicted in Classical medical books.
Why it was removed--and stayed removed for nearly 50 years--would make for an interesting story about mid-century culture, if not for a cynical throwaway comment, though it seems nobody knows Goss' actual motivations.
I don't understand who uses that network anymore. Everytime I login it's all ai generated stories next to ai generated flavor images of people sounding like a parody of themselves ("what taking my kids to school taught me about business scaling").
Out of all places to doomscroll, why choose the one that feels like an episode of Severance?
I built a pipeline that converts all Spanish state legislation into version-controlled Markdown. Each law is a file, each reform is a real git commit with the historical date. 8,642 laws, 27,866 commits.
The idea: legislation is just patches on patches on patches. Git already solves this. Instead of reading "strike paragraph 3 and replace with...", you get an actual diff.
The repo is the product. Browse any law, git log to see its full reform history, git diff to see exactly what changed.
Built the pipeline in ~4 hours with Claude Code. Source is BOE (Spain's official gazette) consolidated legislation API.
Exploring whether there's a business here — structured legislation API for legaltech/compliance, or just a useful open dataset. Curious what HN would build with this data.
Hey! I'm Nick, and I work on Integrity at OpenAI. These checks are part of how we protect our first-party products from abuse like bots, scraping, fraud, and other attempts to misuse the platform.
A big reason we invest in this is because we want to keep free and logged-out access available for more users. My team’s goal is to help make sure the limited GPU resources are going to real users.
We also keep a very close eye on the user impact. We monitor things like page load time, time to first token and payload size, with a focus on reducing the overhead of these protections. For the majority of people, the impact is negligible, and only a very small percentage may see a slight delay from extra checks. We also continuously evaluate precision so we can minimize false positives while still making abuse meaningfully harder.
This is the most supremely motivating post I've seen in a long time. I know what it is to be diagnosed with cancer, being rushed to surgery - it's amazing how quickly the medical-industrial complex can move once you've got a diagnosis (at least in Australia). I had a short period of contemplating terminally, because cancer claimed the life of most of my family. Thankfully, after surgery it was gone.
To see Sid use his motivation and resources to solve his own problem is the core message (IMHO) of the hacker community.
It makes me look at my own problem (Peyronies) in a different light; a disease which has affected my life in ways which cannot be overstated. Yet, all the money in the world right now can't fix Peyronies - yet in reading his journey my mind has been changed about this.
His slide title: "I'll talk to anyone, I'll go anywhere, and I can be there anytime" is certainly the mindset!
Thanks for posting this - I'm inspired to take similar action for Peyronie's. Anything is possible.
A bit skeptical of how this article is written as it seems to be mostly written by AI. Out of curiosity, I downloaded the app and it doesn't request location permissions anywhere, despite the claims in the article.
I've noticed Claude Code is happy to decompile APKs for you but isn't very good at doing reachability analysis or figuring out complex control flows. It will treat completely dead code as important as a commonly invoked function.
It's absurd how unusable Cloudflare is making the web when using a browser or IP address they consider "suspicious". I've lately been drowning in captchas for the crime of using Firefox. All in the interest of "bot protection", of course.
> They also included 2,000 prompts based on posts from the Reddit community r/AmITheAsshole, where the consensus of Redditors was that the poster was indeed in the wrong.
Sorry, anonymous people on reddit aren't a good comparison. This needs to be studied against people in real life who have a social contract of some sort, because that's what the LLM is imitating, and that's who most people would go to otherwise.
Obviously subservient people default to being yes-men because of the power structure. No one wants to question the boss too strongly.
Or how about the example of a close friend in a relationship or making a career choice that's terrible for them? It can be very hard to tell a friend something like this, even when asked directly if it is a bad choice. Potentially sacrificing the friendship might not seem worth trying to change their mind.
IME, LLMs will shoot holes in your ideas and it will efficiently do so. All you need to do ask it directly. I have little doubt that it outperforms most people with some sort of friendship, relationship or employment structure asked the same question. It would be nice to see that studied, not against reddit commenters who already self-selected into answering "AITA".
Without even looking at the AI part, I have a single question: Did anybody investigate? That's it.
Whether it's AI that flagged her, or a witness who saw her, or her IP address appeared on the logs. Did anybody bothered to ask her "where were you the morning of july 10th between 3 and 4pm. But that's not what happened, they saw the data and said "we got her".
But this is the worst part of the story:
> And after her ordeal, she never plans to return to the state: “I’m just glad it’s over,” she told WDAY. “I’ll never go back to North Dakota.”
That's the lesson? Never go back to North Dakota. No, challenge the entire system. A few years back it was a kid accused of shoplifting [0]. Then a man dragged while his family was crying [1]. Unless we fight back, we are all guilty until cleared.
> The connection is believed to be the spatial reasoning involved in routing.
This is triggering me lol. I was a Paramedic for 10 years and 3 of those years were before GPS existed and we had these awful 900 page 5" thick things we had to wield on the fly called Map Books. It was part of our probation period testing and they would time us to pick out the routes reliably within a certain deadline or not graduate from being a probie.
While your partner drove to the call you'd put the book on your lap and flip to the big large grid which would tell you which map your location would be on (page 770), then you'd look up the street in the back appendix to get the coordinates for the specific house (P5, C2) and then find the cross street on another page (P5, C3), go to the grid and find the closest appropriate hospital for the purpose of the call (different ERs have different functions- for gunshots go to Highland, for amputations go to CalPac Davies, for heart attacks go to UCSF, etc) (page 815), the street location for that (A6, C4) and then make your route while flipping back and forth between all the pages while simultaneously telling your partner where to turn as you go.
When I went to a better ran company, dispatch would give us map page and grid coordinates over the radio when we got the call.
Within a few months you learn most of the neighborhoods and routes, and road hazards and preferences- for example if going to UCSF from the Peninsula take O'Shaughnessy because there's no traffic and is a smooth ride. And if you're going to Seton Hospital from 101 slow down around the turn on the on ramp onto 280 because there is a GIANT bump that will knock your partner in the back's head into the ceiling and not be comfortable for the patient on the gurney.
Map books were no fun but some of the dudes I worked with definitely became route-finding savants.
> While I’m certain that this technology is producing some productivity improvements, I’m still genuinely (and frustratingly) unsure just how much of an improvement it is actually creating.
I often wonder how much more productive I'd be if just a fraction the effort and money poured into LLMs was spent on better API documentation and conventional coding tools. A lot of the time, I'm resorting to using an AI because I can't get information on how the current API of some-thing works into my brain fast enough, because the docs are non existent, outdated, or scattered and hard to collate.
When a LLM tells me I'm right, especially deep in a conversation, unless I was already sure about something, I immediately feel the need to go ask a fresh instance the question and/or another LLM. It sets off my "spidey-sense".
I don't quite understand why other people seem to crave that. Every time I read about someone who has gone down a dark road using LLMs I am constantly amazed at how much they "fall" for the LLM, often believing it's sentient. It's just a box of numbers, really cool numbers, with really cool math, that can do really cool things, but still just numbers.
The rate of fatality for Alzheimer’s among ambulance and taxi drivers is 3x lower than the general population. This is not observed in other transportation-related careers.
The connection is believed to be the spatial reasoning involved in routing. No causative link is suggested.
Let's focus on the real issue here, which is that HN has apparently normalized the double hyphen in the title to an en dash--yes, an en dash, not even an em dash.
Very cool. In 1998 (oof) we built Road Rash 64 which was accidentally open world -- even though you had race on a particular road, with a start and finish line, you could drive anywhere, see traffic all over the map, jump off of mountains, etc. The r4k plus reality coprocessor was quite potent -- we got to over 750k shaded triangles per second in optimized testing -- though finicky because you had to manage audio during vblank, etc. Plus, the reality coprocessor fog had a brutal hardware bug that made it really tricky to use.
I got my last job there, and I have a steady queue of recruiters reaching out the whole time. So I will probably continue to use it as long as I need to eat. I don't engage with the feed at all though.
I'm amazed that wasn't taken into account! Many years ago, in the final year of my Biology degree, I did a paid summer internship at an Evolutionary Biology lab here in Spain, assisting in a project where they were researching relationships between metal ion accumulation (mostly zinc) and certain SNPs (≈"gene varieties"). A lot of my work was in slicing tiny fragments of deep-frozen human livers and kidneys in a biosafety cabinet over dry ice.
The reason I bring this up is because the researchers had taken the essential precaution of providing me with a ceramic knife to do the cutting (and platic pliers), to eliminate the risk of contaminating the samples with metal from ordinary cutting implements.
That some research on microplatics did not take into account the absolutely mental amount of single-use plastic that is involved in biological research, particularly gloves of all things, boggles the mind.
The solar covered parking lots near me are great because they also serve as cover for your car when it’s hot and sunny.
It’s not the most cost effective way to install solar, though. A tall structure designed to put the panels high up in the air and leave a lot of space for cars is a lot more expensive than normal rooftop solar or even field setups. This is basically a way to force some of the cost of clean energy as a tax on parking lots. Which may not be a bad thing for dense cities where parking lots have their own externalities on the limited available land.
Looks like what you might expect in a standard marketing app from a consultancy. They probably hired someone to develop it, that shop used their standard app architecure which includes location tracking code and the other stuff.
Let's be real, LinkedIn is full of LinkedIn Lunatics but pretty much all mainstream social media is pretty shit. They're just different flavors of shit. LinkedIn: bad. Facebook: bad. Twitter: I literally think it contributed to the collapse of discourse and rise of shallow thought / rejection of expertise. I'm not going to list more because the theme is, you guessed it, they're bad.
Google+ had promise in that the many problems of the other platforms could be curtailed with tooling to make your social experience effectively local (not necessarily geographically).
> Scraping static content from a website at near-zero marginal cost to its server, vs scraping an expensive LLM service provided for free, are different things.
I bet people being fucking DDOSed by AI bots disagree
Also the fucking ignorance assuming it's "static content" and not something needing code running
I am still amazed that people so easily accepted installing these agents on private machines.
We've been securing our systems in all ways possible for decades and then one day just said: oh hello unpredictable, unreliable, Turing-complete software that can exfiltrate and corrupt data in infinite unknown ways -- here's the keys, go wild.
It's a very small concession. The high initial friction still means when someone comes to me with a problem and I tell them the solution is in F-Droid, they have to wait a day. Most give up and pick a different, less trustworthy solution from Google Play.
