I feel the UPF "debate" is just an appeal to nature, and calorie/nutrient density should be what we fixate on.

These calls come in on an unrecognised number, from staff who say "I don't know" when you ask them to prove they are from Octopus, and generate no call notes so you can't find out why they rang if you use the main customer service number.

To top it off they ask you to key in your card info on the phone after asking for your personal information.

I complained and they offered to fob me off with £30 credit instead of talking to their CISO, but they did at least say they can add phone passwords to individual accounts.

I think you can fairly criticise WAF products and the people who advocate for them (and created the need for them) but I don't think the CF team responsible can really be singled out.

I would surmise that this will stop being a problem if you switch to using a unix socket for the CDP.

Ultimately a sacrifice must be chosen, but I am not sure a discussion about how that should be made is necessarily fit for HN (though I'd be interested in how you'd resolve your proposed scenario).

Within reason I think there is a rational basis for not having to involve software engineers for every project - especially if the SMEs with understanding of their requirements are the ones building it.

This will probably fall over in the same space as Excel spreadsheets do though, when the domain complexity outgrows it, way before anyone is able to recognise that.

VPNs seem useful to guarantee that your traffic is designated as foreign, so this might be a net gain for the intelligence services rather than a loss - the mandatory collection of ICRs only relates to IP addresses and time of access.

[1]:https://www.standard.co.uk/news/uk/edward-snowden-leaks-uk-o...

[1] https://www.reviewgeek.com/45420/over-70-chrome-browser-exte...

There's an obvious slippery slope in these discussions - ultimately it's reducible to who you give the right to vote to, and discomfort about measures to keep the undesirables from rallying ought not to be ignored.

Can't say how well they work but a stack of IF board, DSP only, and Bluetooth programmer cost me around £50. Looks like the DAC resolution is better on the Beocreate though. No idea how good the amp is either - there are plenty of bad TPA3116 boards so sidestepping that problem might be worth the premium too.

It's quite difficult to talk about empirical software engineering without discussing methods, after all papers like [1] were deemed necessary 20 years ago and still the occasional meta-paper is published about correct design of experiments or analyses. As someone who worked in the field it doesn't seem particularly surprising to see some treatment - there are a handful of papers in my former subfield that are oft-cited because they describe a statistical procedure/experiment design consideration, but they also bundle the explanatory stats "for free".

I would hazard a guess that the intent of these chapters is to equip the reader with enough background that they could replicate or run some of the experiments in the book to try to specify findings/experiments to their own organisations. I'd follow that with an assumption that the author felt that chapter 13 needed background, and recursed until they'd finished writing a textbook.

[1] Kitchenham et al. "Preliminary guidelines for empirical research in software engineering" 2001: http://www.ehealthinformation.ca/wp-content/uploads/2014/07/...

Previously if you wanted filesystem control you had to trick a user into downloading something. With this API, it seems like it would be easier to con unsuspecting users into granting permissions they aren't aware they're granting.