HackerTrans
TopNewTrendsCommentsPastAskShowJobs

neilalexander

2,300 karmajoined 12 anni fa

comments

neilalexander
·l’altro ieri·discuss
I don't expect that my current version of the software will be updated forever or remain indefinitely secure though. I expect that I'll get some small updates or security patches for a certain amount of time only and I'm OK with that. If something comes along that I can't live without, or the platform breaks things sufficiently, then I pay for the upgrade at that time.
neilalexander
·l’altro ieri·discuss
TablePlus is a good example. I buy their product and in exchange I get a year of updates. After that, it keeps on working without new features or updates. If I want new features or updates after that, I buy it again. Otherwise, I can keep on using the version I have pretty much until it stops working due to e.g. platform changes.
neilalexander
·l’altro ieri·discuss
> Upgrade pricing also doesn’t solve this. [...] versioned upgrades incentivize developers to chase shiny features that people might pay for rather than improving their app and building for the long haul. It makes the product worse.

In my mind this is missing the point. I am very pro-upgrade pricing because upgrade pricing actually forces the developer to think about what their users actually will pay for, or what improvements will make my workflow better, instead of just adding whatever fancy side-quest thing that you've decided I need today.

If users are asking for shiny new features and are willing to pay for them then fine. If we want refinements and are willing to pay for them then fine. If you want to optionally provide backend storage or backups or whatever then fine.

However, if my continued use of a specific version of your software has no continued cost to you, then be absolutely assured that I do not feel a moral obligation to keep on paying for it endlessly, nor should you assume that I do.
neilalexander
·11 giorni fa·discuss
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.
neilalexander
·18 giorni fa·discuss
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.
neilalexander
·18 giorni fa·discuss
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.
neilalexander
·mese scorso·discuss
No, because you could feasibly end up with neighbour entries for the same address via multiple interfaces and then you are no further forward.
neilalexander
·mese scorso·discuss
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.
neilalexander
·mese scorso·discuss
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.
neilalexander
·mese scorso·discuss
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.
neilalexander
·mese scorso·discuss
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.
neilalexander
·mese scorso·discuss
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.
neilalexander
·mese scorso·discuss
HaLow is just Wi-Fi on sub-1GHz frequencies and narrower channels. You get normal MTUs and TCP & UDP work just fine.
neilalexander
·mese scorso·discuss
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.
neilalexander
·2 mesi fa·discuss
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.
neilalexander
·2 mesi fa·discuss
If only I had a penny for every HN comment about naming conflicts.
neilalexander
·2 mesi fa·discuss
They didn't. Apple contributed the core logic to the Wi-Fi Alliance to build Wi-Fi Aware, which they now also support.
neilalexander
·2 mesi fa·discuss
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.
neilalexander
·3 mesi fa·discuss
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.
neilalexander
·4 mesi fa·discuss
I'm a fairly average HN user but I earn my livelihood by working from home. Backup connectivity is cheap.