neilalexander

This is a dumb take and a very weird attempt at gatekeeping. Of course programming is a profession. It can also be a hobby, but that doesn't mean that it isn't a profession. The world runs on computers and software development is lucrative.

Visa and Mastercard are both US companies and they issue both debit and credit cards. If you have a UK or EU bank account with a Visa or Mastercard, regardless of currency or whether it's debit or credit, you are still ultimately reliant on US companies to clear transactions every time you use it. That's what the EU want to reduce.

Bank-owned and supermarket cash machines don't generally charge for withdrawals in the UK but there are still many third-party machines that do.

No, because you could feasibly end up with neighbour entries for the same address via multiple interfaces and then you are no further forward.

AI contributions are only a part of the issue. Another part is where a contributor decides they want a specific feature and contributes it but then disappears off into the sunset when it comes to needing maintenance later.

Having services be accessible on a link-local address and then advertising that service via mDNS is a completely legitimate use-case that works extremely well and is extremely common with Apple devices amongst others. The advantage being that it still works just the same even without a router handing out addresses or if you just connect two devices directly to each other.

Also what gives you the impression that zones were “deemed a mistake”? They may be awkward in URIs but they are very much not a mistake, they are a deliberate part of ensuring that each link has its own link-local subnet without any ambiguity. It solves the problem of what the operating system should do if you need to access a link-local address that shows up via more than one network interface, which is a very real problem with unscoped IPv4 link-local addresses.

Finally, ULAs don’t and were never intended to replace link-local addresses, they serve a different purpose entirely.

I would add that there is no particularly good reason for an EV to have a push-to-start button. With Volvo, Polestar etc, you get in and shift straight into Drive or Reverse, and when you’re done, you put it into Park and climb out again. This is how it should be.

It matters if it's relevant to the person asking the AI agent for help with what they're doing with the software that they already have.

Because there is a world of software out there that isn't CLI-based and much of it may never be updated to expose LLM-friendly APIs.

HaLow is just Wi-Fi on sub-1GHz frequencies and narrower channels. You get normal MTUs and TCP & UDP work just fine.

None of MeshCore, Meshtastic or Reticulum will scale well, especially not on top of a heavily constrained radio technology like LoRa. Flooding is inefficient for obvious reasons, AODV-esque routing (which MeshCore tries to do for DMs and Reticulum tries to do in general) is prone to almost-immediate path failure on unstable underlying transports, and the hidden node problem always bites on haphazard/unplanned mesh radio deployments where people show up with nodes in random locations on the same frequency.

The cracks are already extremely visible in MeshCore in the UK, where overheads from adverts and dropped packets from collisions mean it is already horrendously unreliable and most of the chatter in the Public channel is people sending test messages and being unsure whether anything they sent was ever heard by anyone.

Most other routing protocols (BATMAN included) are also not that well suited to situations where the underlying transport ends up asymmetric, e.g. one node can't hear others but it can be heard, and that's an extremely common occurrence/failure mode in wireless meshes like this. It's a difficult problem to solve with coordination between nodes, let alone without.

Incoming voltage monitoring is a requirement for EV chargers in the UK. The sudden huge demand would result in a voltage drop, the chargers would then detect the under-voltage condition and they'd stop charging.

If only I had a penny for every HN comment about naming conflicts.

They didn't. Apple contributed the core logic to the Wi-Fi Alliance to build Wi-Fi Aware, which they now also support.

That's precisely what Wi-Fi Aware (NaN) is and it is heavily based on AWDL. It's even built into recent versions of iOS and Android.

Vegetable oil will cause long-term damage in modern diesel engines with direct injection or common rail injection systems. Older indirect injection diesel engines could tolerate it much better because of the pre-combustion stage.

I'm a fairly average HN user but I earn my livelihood by working from home. Backup connectivity is cheap.

No platform is perfect but I'd argue that desktop Linux still has far more many rough edges to contend with when something goes wrong. There are way too many problems for which "well just open the terminal and..." is the only solution.

Useless padding and borders seems to be par for the course in the last couple of years. Another thing redesigned for no tangible benefit.

Random Bluetooth MACs are already possible. iOS devices have been doing it for years alongside the random Wi-Fi MACs.

There is not a single good XMPP client for macOS or iOS either. There are a couple of minimally functional ones that are aesthetically dreadful, but nothing that would come even close to replicating what people would expect even from Signal or WhatsApp, let alone a monster like Discord. Certainly nothing that I could ask friends or family to use.

You might want to check that charger. I have the same option set to ask every time and it never appears for chargers.

I have been using the exact same G4201TM devices at home for approaching five years now to do much the same: reuse some unused telephone wiring for a meaningful purpose. They are rock solid and have needed exactly zero attention since being installed.

One advantage with LLMs is that they are often more able to find things that you can roughly explain but don't know the name of. They can be a good take-off point for wider searches.

If you assign a subnet to a host, or allow the host to claim multiple addresses via ND from the link subnet, then you can use as many addresses as you want. You could give every process on your machine its own IPv6 address for example.

You can go to https://privacy.apple.com, log in with your Apple ID, select "Request to transfer a copy of your data" and then select "iCloud photos and videos to Google Photos".

Because there isn't "empty space" in the IPv4 packet header (or even the pseudoheader format from which TCP or UDP checksums etc are derived) to expand your new bits into. By breaking the packet format, you just invented a new network protocol that all of the routers, firewalls and middleware of the world don't know how to handle.

> Old farts making laws about things they know nothing about.

Who's going to stop them?

As I understand it, Volvo's relationship with Luminar broke down, not that there was an obvious problem with the technology itself.

I would think that if they actually spent the time and money fixing the core functionality of their core products (like Windows and Office) that they might have a much easier time promoting things like Copilot. Instead they leave their users wondering why they're so hell-bent on shoehorning AI into a Start menu that takes whole seconds longer to open than it should or into Windows Search that regularly fails to find installed programs or local files.