jamescun

How? There are dozens of us! DOZENS!

I'm that minutia in your statistics that is still rocking NoScript in 2026, enabling JavaScript on a site-by-site basis, but this is increasingly difficult with the modern web.

Hopefully these and others modern HTML features gain adoption, along with realizing perhaps a Single Page Application isn't necessary in most instances.

I don't often have to write frontend code, but when I do, there is very little in terms of interactivity you cannot do with HTML these days, worst case a little sprinkle of something like HTMX.

Second for NATS.

I've deployed Core NATS as few times now at scale, including within financial trading. It's been a dream to operate.

I have limited experience with JetStream, but coming from Kafka and Rabbit MQ, it seemed nearly as featureful but also easier to maintain.

This post touches on a realisation I made a while ago, just how far you can get with the guarantees and trade-offs of object storage.

What actually _needs_ to be in the database? I've never gone as far as building a job queue on top of object storage, but have been involved in building surprisingly consistent and reliable systems with object storage.

UK citizen and 23andMe customer here. How likely is the sale of UK/EU customer data, or is it worth submitting a GDPR deletion request anyway? Get my data deleted before it's sold.

Not sure what questions Microsoft have to answer. A third-party vendor shipped defective software.

I guess the only question they could answer is why they don't provide a framework like Apple do with Endpoint Security for third-party vendors to use.

That channel is a gem!

I was recently in hospital with not-so-great WiFi.

With the mobile app, I would often notice Spotify loading album artwork, lyris, artist information and even video before playing the music. It's network prioritisation is deeply disconnected from the users wants.

I remember when Spotify heavily optimised to play music in the quickest possible time. Enshittification indeed.

Why is silently patching considered a "no-no by the infosec community"?

If your product's automatic update functionality can reach most users within the responsible disclosure window, that sounds like a net positive? We still learn about the vulnerability but limits the potential fallout of the disclosure.

I'm very much in-favour of the private vulnerability research and responsible disclosure, but the "no silently patching vulnerabilities" sounds more like wanting to own the press to me than actually wanting to improve people's security.

The ICO has always been a bit of a wet blanket. Never really uses its powers effectively. From pathetic fines to putting out press releases about raids before they happen. £140k is just the cost of doing business with 79 million spam emails and 1 million spam texts.

I don't like this. Is there a reason for using a stringified method prefix?

I'd prefer the type safety of verb-specific methods (i.e. mux.Get, mux.Post etc) than magic strings validated at run time. Additionally editors can autocomplete/intellisense methods.

I'm based in the UK and have a passive interest in amateur radio. If I had to guess, it isn't outright forbidden, just a licensed activity. Maybe the license isn't easy to get or widely granted?