neilalexander

Many new public charging sites are being built in the UK too, yes. Several thousand rapid charging points in the last year alone.

Yes, I responded to your other comment about that. Charging at home is very cheap though and it's estimated that roughly half of housing in the UK has a driveway. Some more creativity is going to be required to address it for everyone else indeed, for example kerb or lamp-post chargers, or in flat building car parks etc.

I think "nobody wants a used EV" will change, there is already a growing amount of evidence that battery deterioration is nowhere near as bad as feared on average. ICE vehicles also tend to get less efficient over time as well due to wear and tear, build-up, degrading sensors etc, it's just that nobody talks about that.

The cost of public charging is still one of the biggest problems. I'm currently on a night-time charging tariff at home at 4p/kWh. It will go up to 8p/kWh in October but that's still pretty good considering it's not uncommon for public rapid charging to be 10x that.

Of all the rapid charging networks, I find Tesla are often the cheapest, there are Tesla 250kW charging stations near me that are 33p/kWh during quieter hours.

There are over 120,000 public charging points across the UK, with over 25,000 of them being 50kW+ DC. That's averaging more than one charger per square mile of the mainland UK (density distribution of course varies).

There is a “Turn off Siri” option. Apple Intelligence & Siri are now effectively one.

My attempts to use XMPP mostly start and end very quickly with the fact that there isn't a single good native XMPP client for Mac or iOS. None of Monal, Siskin or Beagle are a good experience, ChatSecure appears to be abandonware and Prose is Yet Another Web App.

Documentation explaining the Keychain security model: https://support.apple.com/en-gb/guide/security/secb0694df1a/...

I would think it has far more to do with content consumption than it does eyesight.

“Useful computer” is subjective. It seems to be difficult for HN users to imagine a device that doesn’t have a terminal for example, but the overwhelming majority of users simply do not care. Many of them manage just fine with a smartphone as their primary (if not their only) computer, so clearly they are useful enough.

It's not about fighting over the "one and only", it's about sane human-friendly defaults. A desktop environment can and should express opinions over those defaults, because they are what make or break the experience for a new or novice user. If a power user wants to swap things out, rename/disambiguate them or whatever then ultimately nothing stops them.

The subtitles are a user interface bandaid that has to exist because the naming is bad. With discoverable naming, the bandaid would not be needed. When you keep compounding bandaids, user experience breaks down.

Naming should be general. Ask a new user whether names like Dolphin, Okular, Kdenlive, Kate, Gwenview and Dragon are even remotely discoverable.

KDE application naming is so consistently terrible that their default application launcher has to subtitle them with descriptions.

Regarding 2, use the File menu in the menubar.

XMPP leans heavily on capability negotiation and service discovery which makes it straightforward to degrade gracefully when feature mismatches occur. Matrix is significantly lacking in this regard.

> audacious mission to make Linux on the desktop happen

On the one hand, I'm supportive of people trying to make Linux on the desktop happen. On the other hand, a distribution aimed squarely and solely at developers doesn't seem like it's faithfully achieving that goal whatsoever, given that developers are the one group of people today that don't generally have a problem running Linux on the desktop. I would be far more excited to see this kind of money being poured into building a desktop for everyone else.

It's not really a hack. It's a hint to a static analyser, that's all.

For anyone who missed the reference: https://xkcd.com/927/

In the same way that you can hack apart a loaf of bread with a spoon, yes, but they are very different things with different goals.

Different animal altogether.

Rayfish, Tailscale, ZeroTier, Netbird etc are a different category of tool, designed to facilitate connectivity between you and your own pool of machines. They don't generally do much in the way of multi-hop routing, but rather they orchestrate VPN tunnels on top of another routed network (like the internet).

Reticulum would be better compared to Yggdrasil, cjdns etc as routing schemes for larger networks or true meshes, which can work independently of (and have no dependency upon) the internet.

It is immensely frustrating that there is so little unlicensed spectrum available vs the massive amounts of spectrum available to militaries and very rich network operators.

Worse is that the unlicenced spectrum that is available is often so heavily encumbered with restrictions in many parts of the world. Wi-Fi HaLow for example, in ETSI regions, is limited to a paltry 14dBm EIRP in no wider than 2MHz channels and an unacceptably punishing duty cycle restriction in most cases that render it barely able to make a TCP connection (some mitigations exist that involve channel hopping on some products but nothing that works for things that require fixed channels, e.g. IBSS or 802.11s).

I worked on Dendrite for a number of years, activity on it pretty much fell off a cliff after I left Element but there seems to be a fork called Zendrite that has carried on with development more recently. There is a migration path from a standard Dendrite installation: https://zendrite.pat-s.me/administration/migration-from-dend...

The CAP_NET_BIND_SERVICE capability on Linux is far less of a blunt instrument that applies to a single process rather than system-wide.

Someone else commented about the law being “non-autistic”, this is a perfect example of that. The technicality of the encryption keys vs the files is irrelevant, the intent was to successfully prevent a search. The border agents will not be even remotely impressed or suddenly decide to release you just because you say “well the files are technically still there”.

This is not true. There's a specced QR code and Bluetooth workflow for using a passkey on one device to sign into an account on another. It works cross-platform.

Ofcom's interpretation and enforcement of a law is not immune from judicial review, however. The courts can rule that Ofcom misinterpreted the law or acted outwith their remit or didn't have the necessary legal foundation for a decision. At which point Parliament have to consider whether or not to revise the law or whether to leave their primary enforcer with their hands tied.

I did read the article, yes, and it is clear to me that this is a bug, not a feature. Ofcom were suddenly able to find a "novel reading" when directed to do so by a court as a means to temporarily make the problem go away and to avoid having to weaken the legislation.

They know full well that if a successful legal challenge forced them to weaken parts of the OSA by removing service categories from scope, that they'd effectively open the floodgates to more challenges over other categories. The government and Ofcom don't want their precious work ripped up and the courts seemingly don't want to be responsible for doing so.

Whatever loophole they've found, it is practically a certainty that it will be addressed in the future.

In other words, "stay where you are for now, we promise to extend the legislation to cover you in the future".

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.

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.

> 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.