E2EEd

If that helps to compartment knowledge in order to further UK security, one can expect it, eventually.

Nothing is scarier to me than a distant techno landscape where knowledge in irresponsible or irrational hands can be used for unimaginable horrors. Such extreme measures as censorship of undergrad STEM education would, in such a case, seem appealing to authorities.

Encryption offers table stakes for weaponization of math. I do, however, agree in spirit with your slippery slope arg

* Successfully hacked US citizen on US soil, from US soil, without a warrant. All hops were domestic. SIGINT then provided to celebrity's hired PI's.

* Stalked and gaslighted US citizen on US soil, using said SIGINT.

* Threatened US citizen on US soil with murder to deter investigation into previous federal crimes.

* Threatened to ruin US citizen as retaliation for not staying silent about above incidents

* Stalk and harass US citizen on US soil in public

etc

Clearance Holders

I built an app with a REST API a long time ago, now a defunct startup. In an effort to save API calls, the front end devs requested that I add various other resources in new endpoints, often a subset of another endpoint's response fields. The API spec ended up being fairly unwieldy.

I've often thought that this would be a great use case for GQL. Seems like a good choice if your front end wants to specify exactly what data to get.

SOP: Build "from scratch" as a superset on the existing legacy.

Key feature is swallowing the dentic as harmless. Risk management is the priority.

Yes, that is it, thanks.

This article is on the hn front page but disappears for this account "E2EEd".

User error is still the 600 lbs gorilla. Figure out how to make tech security idiotproof. This is increasingly difficult as IT systems become more complex over time, adopted by an expanding pool of participants.

It's all broken, but a purist will go off grid and live in the woods.

Perhaps you'd find passion in pursuing a PhD (or other avenue of professional R&/D) that focuses on resolving the fundamental issues with much of software development methodology, endpoint arch, and networking.

Barring that, the MO is to devise more robust bandaids.

The proprietary and secret nature of big tech security creates a playing field of fortified castles vs. self reliant survival in the wilderness. Tail end participants such as Google's core infra security will outmatch any independent actor. And, still, both google and apple consumer endpoints seem to have fundamental security flaws, entrenched due to being built on many billions in investment over decades.

Something like CHERI may take decades to bear fruit, hopefully turning over and pruning any insecure legacy systems sooner rather than later. Telecom is an example of why this will likely never occur anytime soon, and that we may be stuck with current security paradigms for many, many decades.

While I never investigated it personally, my understanding is that the quantization on the MPC60/3000 series was a big part of the feel. By definition, a quantized sequence is not a sample-accurate reproduction of a live MIDI perfomance.

Also, such idiosyncratic quantization is faithfully simulated in software nowadays, anyway.

Contrarily:

I challenge the notion that it is impossible to model the A/D, any DSP, and the D/A of the MPC3000 in software. While modeling non-linear response dependent on factors such as gains and impedances is not trivial, it is certainly feasible. Much of the pro audio world has moved on to plugins for their ability to reproduce the desirable aspects of analogue hardware while removing the undesirable aspects (such as noise).

A hardware sequencer/drum machine offers things that can't be modeled: tactile feel, low(er than some computers, still to this day) midi latency. Even the limitations such as a slow UI synchronously coupled to slow offline processes (which could be conceivably be modeled) affect the creative process in non-intuitive ways.

Similarly: reel to reel creates a smell that affects the vibe. Limited tape and no undo button affect the creative process as well.

DAW's are great but are essentially unlimited. This opens up horizons, but it does remove musicianship as a requirement in a recording context.

In East Coast rap studios, MPC3000 was it for a while

SP1200 and MPC3000 were considered standard

False. Akai MPC3000 was the pinnacle of rap/r&b beat machines in its time. The info conveyed is serious, not a joke. GOAT is an opinion.

Go into the biz of robbing banks for profit. Like in Sneakers intro but adjusted for 2022, more automated, robotic, human-decoupled.

It'll make DHS salivate when you prove that the need for high speed, AI drone defense is greater than currently is deployed.

You'd probably sell a full stack solution with a "Jolly Bank Robber Cookbook Manual 2022" to prove the risks going fwd along with successful live field tests.