HackerLangs
TopNewTrendsCommentsPastAskShowJobs

collinmanderson

2,378 karmajoined 12 年前

Submissions

Django 6.1 alpha 1 released

djangoproject.com
4 points·by collinmanderson·2 個月前·1 comments

The college student–and his cat meme–who hunted the biggest cyberweapon

msn.com
5 points·by collinmanderson·3 個月前·0 comments

National Security Strategy of the United States of America [pdf]

whitehouse.gov
9 points·by collinmanderson·7 個月前·9 comments

I want to build a chip fab in Canada

ontario-chips.vercel.app
2 points·by collinmanderson·7 個月前·2 comments

[untitled]

1 points·by collinmanderson·8 個月前·0 comments

comments

collinmanderson
·昨天·discuss
No, they would just ignore Firefox and not test against it, and might start to use chrome/safari-only features.
collinmanderson
·3 天前·discuss
This makes sense. Originally Fable was going to be available via subscription June 9th through June 22nd (~14 days).

It ended up being available 2.5 days before pulled, then was made available July 1 through July 7. (~7.5 days), so only ~10 days total.

Now they're giving us 5 more days, so ~15 days total, more similar to what they originally announced.
collinmanderson
·4 天前·discuss
Part of the problem is The US Government (and UK Government) use the "2% rule" on their websites and only officially support 98%.

I mentioned 3 years ago that Firefox at 2.2% is dangerously close the being unsupported on government websites, and at this point it's now at 1.9%.

https://news.ycombinator.com/item?id=36776603

https://analytics.usa.gov/ says "There were 1.66 billion sessions in the last 30 days." - so 2% is 33 million sessions if I did my math right.
collinmanderson
·24 天前·discuss
https://xkcd.com/1150/
collinmanderson
·上個月·discuss
> no cooldown (or a much smaller countdown) for security fixes.

A supply chain attack would likely able to publish a "security" release just as easily as a normal release, so I don't think that would help much.
collinmanderson
·2 個月前·discuss
Release notes here: https://docs.djangoproject.com/en/dev/releases/6.1/

Looks like there's some features to try to reduce the “N+1 queries problem”.
collinmanderson
·2 個月前·discuss
> I just caught myself about to copy and paste it into Claude to see what it thinks because I'm worried that it doesn't make sense or it reads funny or there's something missing. That's the self-doubt that it's feeding on and what I need to fight back.

This is where I'm at. I feel like I need AI to review everything.
collinmanderson
·2 個月前·discuss
> As the victim of the one from last year

Background here:

https://news.ycombinator.com/item?id=45169657

https://news.ycombinator.com/item?id=45187528
collinmanderson
·2 個月前·discuss
> Or are folks seriously proposing that the patch/mitigations should have been circulated to distro maintainers privately before going to mainline?

I always assumed that distro maintainers got early access to patches before going mainline but maybe that’s not true?
collinmanderson
·2 個月前·discuss
Github Copilot also lets you use other models when one has an outage.
collinmanderson
·2 個月前·discuss
> Disruption with Gemini 2.5 Pro model

> Disruption with Grok Code Fast 1 in Copilot

> Incident with Copilot Grok Code Fast 1

> Claude Opus 4 is experiencing degraded performance

It doesn't seem fair to blame Github for this? There's nothing they can do about it?
collinmanderson
·2 個月前·discuss
https://xkcd.com/1150/
collinmanderson
·2 個月前·discuss
Shout out to https://ticalc.org/ - the design is pretty much unchanged.
collinmanderson
·2 個月前·discuss
Yes. So cringy.
collinmanderson
·2 個月前·discuss
Why not Just™ store all PR/Issues content as markdown on a separate branch along side the code itself? Why do we need a new protocol?
collinmanderson
·3 個月前·discuss
> Because we cannot name something leading with a trademark owned by someone else.

And this WSL project is going to run into the same problem.
collinmanderson
·3 個月前·discuss
> Proudly written without AI.

Looks like it's been updated now to be more clear. Amazing though.
collinmanderson
·3 個月前·discuss
I just want to point out this guide uses many of the same tasks I use when migrating websites between servers while minimizing downtown.

- reduce dns ttl (if not doing an ip swap)

- rsync website files

- rsync /etc/letsencrypt/ ssl certificates

- copy over database (if writes don't happen often and database is small enough, this can be done without replica, just go read_only during migration)

- test new server by putting new ip in local /etc/hosts

- turn off cron on old server

- convert old server nginx to reverse proxy to new server

- change dns (or ip swap between old and new server)

- turn on cron on new server
collinmanderson
·3 個月前·discuss
France is trying to switch to desktop linux. https://news.ycombinator.com/item?id=47716043 and https://news.ycombinator.com/item?id=47719486

I think AI also makes it easier to deal with issues that come up.
collinmanderson
·3 個月前·discuss
This is a super interesting story and I'm surprised it hasn't made the headline on Hacker News.

Edit: looks like this one is the most popular, from Jan 3rd. It even was put into the 2nd chance pool, but still didn't get catch on: https://news.ycombinator.com/item?id=46472040