Hacker Newsnew | past | comments | ask | show | jobs | submit | donohoe's commentslogin

https://donohoe.dev/ - My site

https://donohoe.dev/timeswire/ - My favorite thing on my site


There is nothing stopping anyone here from registering a new shiny .org domain (or any tld) and pointing it to Anna’s Archives name servers.

Except they are probably not set up to respond to new domain names and generate HTTPS certificates for them.

No vaccine is without risk, but the vaccine approach is based on that risk being so low (but not zero) in comparison to the risk of not vaccinating that it is vastly the better choice.

Ok that was a bad question, let me rephrase: isn't there something particularly bad about this one for males that are already adults that makes it not recommended by doctors by default?

There's nothing particularly bad for adult males.

The benefits may be statistically lower, since you may have been infected by some of the variants already, older males may have fewer sexual partners in the future, and cancer takes a while to develop.

In the USA, it is recommended by default for adults up to 26 and kinda for 27-45.


There is plenty there “for journalism to occur” in terms of the write-down of the deal and Teslas current performance. It’s newsworthy in itself.


It's not journalism anymore when you take one fact and then use it as the basis for wild speculation.


I re-read it. Very little is speculative and nothing I’d label as “wild”.


It's 'wild' to this person because it challenges their opinion on Musk and Tesla I have to guess. This is a classic 'it is bad reporting because it does not agree with my worldview' take, aka 'fake news'.


Many other comments show that it is. One example: https://news.ycombinator.com/item?id=46423846


The one comment suggests a valid alternative. It doesn’t suggest that this was ‘wild’ reporting - which was your original point. The article still adds information, analysis, and not much speculation.


About 10 years ago, when I was at The New Yorker, I worked on launching the redesign, paywall, and the move to WordPress. We actually had most of the archive technically ready to go. The data wasn’t the hard part.

The real blocker was permissions and rights. Contracts going back a century obviously never contemplated digital publication, domains, or the internet at all. Untangling who owned what, and securing the right to republish everything online, was a massive legal and logistical undertaking.

That’s what held us back then, not so much the technology. Really glad to see that chapter finally closed.


Any idea what changed, if anything? Court decisions made in the meantime simplifying things?

Hopefully the content fits in a few buckets (cartoons, fiction, non-fiction) as far as different terms for rights might go. And then from there, you can lop off anything that's past its copyright term (?). Then maybe the next step is grouping works by the agent/publisher, if any? Or maybe all the contracts with the New Yorker are signed by individuals, with the New Yorker as a publisher. I don't know.


I assume it was a matter of time - ten years of digging into contracts or chasing people/agencies down (speculative on my part)? Bear in mind, if you are unsure if you have rights to a piece then you cannot use it until you know for sure - I am sure that was part of it too.


Fun (unrelated) fact:

My favorite product that I got to build there was “Cartoons at Random”. You’ll never guess what it did/was!

I miss it terribly, just swiping images off a stack to reveal a new random cartoon underneath.

The developer (Justin?) did an amazing interaction on iOS app (seamless, no jank) and web version was decent too.

They broke it when they migrated from Wordpress to their own Condé Nast CMS

https://www.newyorker.com/cartoons/random/share/1544311

Such delight. Sigh.


I'm bummed that we never made that link keep working - it was a fun start page.


It happens. I felt like the Copilot/Autopilot CMS team had a lot going on so I understood. But it was a good play for a decent native ad experience (example: we ran a decently funny set of Bill Murray cartoons - and that was good) oddly enough and assumed that would ensure its survival.


Or just this:

  $ sed -i -E '/maxUsers(Hard)?Limit.*0$/s/$/_000/' channels/app/limits.go
Source: https://github.com/mattermost/mattermost/issues/34271#issuec...


This is a different limit.


Would also be nice to remove the phone-home telemetry.


“Free”?

What’s the catch, or how I can I be sure it will still be around in 3 months?

No snark, genuinely curious as I would use this if I could count on it.


The only tech you can trust to be around is the tech you control. And even then it's still a bit iffy if you didn't write all the code yourself and you host it on someone else's servers.


Its been happening a lot and its becoming more prevalent. This coverage from 2022 is still highly relevant and digs into some details:

https://restofworld.org/2022/blackouts/


Which will settle it quickly under the watchful AI judiciary.


Two AI agents fighting couldn't end up in an infinite loop?


More billable hours.


Or seconds. Hours if there is a Cloudflare outage.


Just to say that humans have only been here around 300,000 years. “Human-kind” is a stretch.


We've been harnessing fire for over 400,000 years

https://www.npr.org/2025/12/11/nx-s1-5640109/early-humans-fi...

> The discovery suggests early humans were making fire more than 350,000 years earlier than previously known.

> "For me, personally, it's the most exciting discovery of my 40-year career," Ashton said.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: