There are a whole host of things people could (and probably are) using LLMs for. Think about what the tool fundamentally is. An enabler. A helper. A teaching assistant. A more ergonomic search tool.
Now think about all of the dumb, violent, ideological, illegal things that folks do.
No one wants their bowel/fertility/pregnancy/prostate/breast concerns made public or traded between companies. If for no other reason than health insurance fuckery.
To add a new point, what about the scope of trust here?
For the lifetime (which is?!) of the data do you trust:
- all the executives who make decisions on the data? IE direct policies but also indirect decisions like what budget exists for securing it.
- all the executive of companies who might buy the data or buy the company that has the data.
- all the technical admins of the originating company AND all the companies that might later have the data.
- all the governments that have legal leverage over the above companies
It's very useful to have this additional information in something like a network address. I agree, you shouldn't rely on it, but IPv6 hasn't clicked with me yet, and the whole "globally routable" concept is one of the reasons. I hear that, and think, no, I don't agree.
Globally routable doesn't mean you don't have firewalls in between filtering and blocking traffic. You can be globally routable but drop all incoming traffic at what you define as a perimeter. E.g. the WAN interface of a typical home network.
The concept is frequently misunderstood in that IPv4 consumer SOHO "routers" often combine a NAT and routing function with a firewall, but the functions are separate.
It is widely understood that my SOHO router provides NAT for IPV4, and routing+firewall (but no NAT) for IPV6. And provides absolutely no configuability for the IpV6 firewall (which would be extremely difficult anyway) because all of the IPV6 addresses allocated to devices on my home network are impermanent and short-lived.
You can make those IPv6 IP addresses permanent and long-lived. They don't need to be short-lived addresses.
Also, I've seen lots of home firewalls which will identify a device based on MAC address for match criteria and let you set firewall rules based on those, so even if their IPv6 address does change often it still matches the traffic.
There’s something about ip6 addresses being big as a guid that makes them hard to remember. Seem like random gibberish, like a hash. But I can look at an ip4 address like a phone number, and by looking tell approximately its rules.
Maybe there’s a standard primer on how to grok ip6 addresses, and set up your network but I missed it.
Also devices typically take 2 or 4 ip6 addresses for some reason so keeping on top of them is even harder.
When just looking at hosts in your network with their routable IPv6 address, ignore the prefix. This is the first few segments, probably the first four in most cases for a home network (a /64 network) When thinking about firewall rules or having things talk to each other, ignore things like "temporary" IP addresses.
Ignore all those temporary ones. Ignore the longer one. You can ignore 2600:1700:63c9:a421, as that's going to be the same for all the hosts on your network, so you'll see it pretty much everywhere. So, all you really need to remember if you're really trying to configure things by IP address is this is whatever-is-my-prefix::2000.
But honestly, just start using DNS. Ignore IP addresses for most things. We already pretty much ignore MAC addresses and rely on other technologies to automatically map IP to MAC for us. Its pretty simple to get a halfway competent DNS setup going on, so many home routers will have things going by default, and its just way easier to do things in general. I don't want to have to remember my printer is at 192.168.20.132 or 2600:1700:63c9:a421::a210 I just want to go to http://brother or ipp://brother.home.arpa and have it work.
But as you can see this is still an explosion of complexity for the home user. More than 4x (32 --> 128), feels like x⁴ (though might not be accurate).
I like your idea of "whatever..." There should be a "lan" variable and status could be shown factored, like "$lan::2000" to the end user perhaps.
I do use DNS all the time, like "printer.lan", "gateway.lan", etc. But don't think I'm using in the router firewall config. I use openwrt on my router but my knowledge of ipv6 is somewhat shallow.
Whenever I am feeling smart or particularly talented, I like watching Shane's videos. I'm swiftly reminded that I have no idea what the hell I'm doing and carry on.
I like that he still shows the struggle, so it’s not like he’s pretending to know it all. I find this helps give me perspective when I’m in a similar situation, where everything seems to be going wrong.
This seems like the right call. When it comes to projects like these, efficiency is almost everything. Speaking about my own experiences, when I hit a snag in productivity in a project like this, it's almost always a death-knell.
I too have a hobby-level interest in Rust, but doing things in Rust is, in my experience, almost always just harder. I mean no slight to the language, but this has universally been my experience.
The advantages of correctness, memory safety, and a rich type system are worth something, but I expect it's a lot less when you're up against the value of a whole game design ecosystem with tools, assets, modules, examples, documentation, and ChatGPT right there to tell you how it all fits together.
Perhaps someday there will be a comparable game engine written in Rust, but it would probably take a major commercial sponsor to make it happen.
One of the challenges I never quite got over completely, was that I was always fighting rust fundamentals, which tells me I never fully assimilated into thinking like a rustacean.
This was more of a me-problem, but I was constantly having to change my strategy to avoid fighting the borrow-checker, manage references, etc. In any case, it was a productivity sink.
I bet, and that's particularly difficult when so much of modern game dev is just repeating extremely well-worn patterns— moving entities around and providing for scripted and emergent interactions between those entities and the player(s).
That's not to say that games aren't a very cool space to be in, but the challenges have moved beyond the code. Particularly in the indie space, for 10+ years it's been all about story, characters, writing, artwork, visual identity, sound and music design, pacing, unique gameplay mechanics, etc. If you're making a game in 2025 and the hard part is the code, then you're almost certainly doing it wrong.
Personally, I don’t think of it as fighting, more like “compiler assistance” —
you want to make some change, so you adjust a struct or a function signature, and then your IDE highlights all the places where changes are necessary with red squigglies.
Once you’re done playing whack-a-mole with the red squigglies, and tests pass, you know there’s no weird random crash hiding somewhere
It is a question of tradeoffs. Indie studios should be happy to trade off some performance in exchange for more developer productivity (since performance is usually good enough anyway in an indie game, which usually don't have millions of entities, meanwhile developer productivity is a common failure point).
I can't help but completely agree. I could see an abstraction like this working really well on top of a simpler foundation, and I desperately think that's what the industry needs.
But as it stands, on top of Helm/Kubernetes/Terraform/AWS/GCP/etc., there are so many dragons.
I wonder if this tool could be repurposed to leverage much simpler cloud concepts that inherently require less operational skills to maintain.
There are definitely a lot of dragons, but there are also a lot of teams that use these tools and need help slaying those dragons :)
We chose to focus on IaC because we think general coding agents are going to take a long time to solve all the edge cases well.
I do think a similar tool built on something simpler would be really interesting. I’ve been tempted to try this with our previous product: https://docs.launchflow.com/
Cease and desist from Signal incoming, from their legal terms:
> "Signal", Signal logos, and other trademarks are trademarks or registered trademarks of Signal Technology Foundation in the United States and other countries (more info here).
I couldn't really find any details about any of these cases. Some of the names there too are pretty strange like "Tobaccopedia" and "Kraft LLC vs Kraft ULC". ULCs (as far as I know) are a Canadian thing and I highly doubt I can just go an open a company called "Cocacola ULC" in Canada?
Those examples look like LLM generated nonsense, though correct me if I'm wrong.
The example usually taught in school for this sort of thing is the trademark for Aspirin. Aspirin is a Bayer brand name for acetylsalicylic acid, but Bayer didn't defend its trademark in most of the world. In most countries (including the US) courts ruled that Aspirin is a generic term and anybody could use it. That's not the case for say Tylenol (acetaminophen) or Advil (ibuprofen) for example.
"German pharmaceutical firm Bayer was forced to give up its rights to the Aspirin trademark in the Treaty of Versailles, in 1919, which followed its defeat in World War One (it also lost the rights to Heroin, but in hindsight it's probably not so upset about that).
The punishment only applied to aspirin's use in victor nations the USA, UK and France, leaving Bayer's trademark still enforceable elsewhere."
“Elsewhere” being literally meaning else where. I wasn’t alive in 1919, though my understanding from the literature is that “the American public didn’t like the German”. Like how they didn’t like the Irish before that. Then how they don’t like the Japanese in 1940s, the north Koran in 1956, then the Vietnamese in 1950-60s, then the Arabs in the 1970s-2000s, then the Chinese in the 2010s-today.
You're looking at AI slop because somebody made something up and had the machine riff along with it. You can very well have the LLM generate you a bunch of cases "proving" that it's illegal to have a pet cat or that in France everybody is legally required to smoke.
In fact trademark lawyers would prefer you to believe that if you're spending $1 on like, making the trademarked product rather than giving them the dollar to "defend" your trademark that's a false economy because magically a court will tear up your trademark because you were supposed to spend all that money on lawyers. If they can argue they really believed this was true (e.g. they read nonsense hallucinated into existence by AI) they're not even lying to you, it's just super convenient that they falsely believed something which directly benefited them...
reply