I'd agree completely but this could just be due to logistical constraints of the ANAE, I took a course with Charles Boberg (one of the authors of the ANAE) and he was definitely aware of that, I vaguely recall learning from him that the Newfoundlander accent traditionally doesn't have t/d flapping which is totally unique in North America. Great class, he definitely has an incredible knack for precisely imitating accents.
For me there is definitely a blocking factor, like awaiting for a click, before I can move into exercises and healthier food and such. Maybe it is a rare case and I do wish it is the other way around.
Actually now that I think about it, "The Soul of the New Machine" / "Showstopper" both describe this kind of mental (although I'm far from a good engineer) when engineers are done with a project, they get frustrated during the waiting period between two projects. This is pretty similar to what I felt -- whenever I finished a project, I tried to find new projects to work on immediately, not want to lose the momentum, but frustration quickly mounts among 1) I was burnt out temporarily but could not take a break, and 2) It's hard to find projects suitable for my level. It usually took a few months for this frustration to pass, which is frustrating by itself.
The second interpretation is nonsense of course. If you want GPL-like obligations, use the GPL.
A license is what it says in the license, nothing extra. It's a legal document not a moral guideline.
I do think it's a very good idea to always use the GPL (even though commercially minded types always get their panties in a bunch about the GPL) for any user-facing software, to force everybody to 'play fair and share'. The only reason to use MIT imho is for a library implementing some sort of standard where you want that standard used by as many people as possible.
I don't understand people who use MIT for their project and then complain some commercial firm takes their contributions and runs with it. If that's not what you want don't use that license.
Apart from license terms and moral obligations being a bad mix, companies don't have morals. Don't get me wrong, I think they should have! But they don't.
People have morals. Groups of people (a company, a country a mob) not so much. Sadly.
I submitted this because I thought it was a good and nuanced (if long) take.
FTFA:
> If I had AI in 2019, I would not have lasted 3 years before the interview crashed me. I would have lasted longer, and the crash would have been worse.
Basically, there is no standard beyond the ages-old requirement to have abuse@ and postmaster@ email addresses that react to such reports. Which Google doesn't follow at all, you just get redirected to some useless web form which requires a Google account and the sacrifice of a goat.
It is entirely Google's fault, and they should be shunned for it and their emails dropped. But unfortunately, they are too big for that by far...
> What makes you so sure that closed-source companies won't run those same AI scanners on their own code?
How many companies take the time to use penetration testing tools, that have been available for many years, to verify their software (or pay a penetration testing company to do a more thorough job than they have the experience to do internally)?
Some, certainly. Many, possibly. Most, I would wager not.
This feels like the 2026 version of companies adding "blockchain" to their name in 2017 and watching
the stock jump. The shoe business was real — they had a genuinely differentiated product with the
merino wool. Pivoting from a physical product with brand recognition to "AI" when you have no
obvious AI expertise or data moat is a tough sell beyond the initial hype pop.
Well he didn't choose JSON, he chose JSON Schema and since the documentation is trying to hide the existence of JSON Schema and the potential limitations of it when used in combination with e.g. gRPC, when the schema is 99% of the project it's hard to trust the project.
I had a 386 with 40Mhz (which does not exist, so in hindsight it must have been a clone chip) and 4MB Ram. I could run all Doom 2 levels with reasonable speed, except the last one, where 4mb just wasn't enough.
In the first half of my comment, I explained that I don't think people should suffer. I'm just also aware that if everyone can pick their child's attributes, it could lead to a nation of blond-hair, blue-eyes kids
Women can help the front line fighters but if I was running a country I would not want to put a large number of women on the front, especially young women.
Sure they can fight and kill.
But a country that loses its ability to make more people won't last longer than a generation.
Two things a country needs from which all other needs derive: people and a border that can be defended.
Men historically get sacrificed to protect the border. And women "sacrificed" to make more people.
Food, entertainment, religion, government, taxes, education, etc... it's all to serve those two fundamental requirements.
With IPv6 privacy extensions it's impossible to tell which device you're talking to inside of a /64. You'd need to do something silly like DHCPv6 to get that kind of remote device-level tracking.
It amuses me to see that according to the map, France is best in class or close to be, while just a few weeks ago, my ISP in France stopped providing me IPv6 connectivity…
The story is that at the beginning I had IPv6, and a shared dynamic IPv4 behind a CGNAT, I asked for a rollback to a full duplex static IPv4 and for three years I had both a static personal IPv4 and an IPv6. A few weeks ago my router went down and since it went back up, I no longer have an IPv6 address. I called my ISP and they explained that I could either have IPv6 or a static IPv4, but not both, and that it's abnormal that I had both for so long… welp, it's sad to see IPv6 but getting it back is not worth abandoning my static IPv4 and going back to a dynamic shared IPv4.
Yes, exactly. I made the Context Layer into a skill where I describe the structure. So when I say, "reindex", the agent knows to check and update the index files. Also it knows if it modifies any file, it needs to also update the index. Works really well!
The big reason is that domestic ISPs don't want to switch (not just in the US, but everywhere really.)
Data centers and most physical devices made the jump pretty early (I don't recall a time where the VPS providers I used didn't allow for IPv6), but domestic ISPs have been lagging behind. Mobile networks are switching en masse because of them just running into internal limits of IPv4.
Domestic ISPs don't have that pressure; unlike mobile networks (where 1 connection needing an IP = 1 device), they have an extra layer in place (1 connection needing an IP = 1 router and intranet), which significantly reduces that pressure.
The lifespan of domestic ISP provided hardware is also completely unbound by anything resembling a security patch cycle, cost amortization or value depreciation. If an ISP supplies a device, unless it fundamentally breaks to a point where it quite literally doesn't work anymore (basically hardware failure), it's going to be in place forever. It took over 10 years to kill WEP in favor of WPA on consumer grade hardware. To support IPv6, domestic ISP providers need to do a mass product recall for all their ancient tech and they don't want to do that, because there's no real pressure to do it.
IPv6 exists concurrently with IPv4, so it's easier for ISPs to make anyone wanting to host things pay extra for an IPv4 address (externalizing an ever increasing cost on sysadmins) rather than upgrade the underlying tech.
If you want to force IPv6 adoption, major sites basically need to stop routing over IPv4. Let's say Google becomes inaccessible over IPv4 - I guarantee you that within a year, ISPs will suddenly see a much greater shift towards IPv6.
I recommend going through Hurricane Electric's multiple-choice tests. It's not exactly a how-to guide or course, but it'll mention all of the terms and technologies you need to look up to get things right. They'll even send you a free T-shirt if you make it through all of them.
The most difficult parts for a homelab in my experience is getting Docker to play nicely. All of the other stuff sort of just works these days. Even things like using DHCPv6 prefix delegation to obtain a routable subnet is almost trivial with how well-supported the protocol is with modern networking software.
