salawat

Any custodial system will have this problem. There is no way to get the "Financial Services" conveniences without essentially implementing freezeability by law. You cannot be a lawful money transmitter without said capability.

They are shedding the extra consciences they aren't interested in having weigh into the calculus of business. Simple as. They'll deny it, but the actions speak for themselves

Why not just buy out like 1% and change everything. Change out management. Lord knows, new blood would probably do the place good.

Replicant detected. Please remain seated. The authorities will be there shortly.

That's why we fight together as best we can. Syndicate. Spread awareness. Do whatever you are able, and damnit, we both know it's more than nothing. If not for yourself, then do it for those you care about most.

Someone ends up having to act as a hub. The more you gear for that job, the easier you are to target, and the more worth it it is to target you.

Whatever you are trying to accomplish, you have to remember that all tech is predisposed on a functioning society with cooperative people to move your packets from A to B.

Tech cannot solve the problem of Trust. Quite the opposite. It amplifies to immense degrees. In short, if you're looking for tech to save you because your Government is doing something shady, you're at the wrong level. Tackle the government.

Sad, but inevitable.

That makes it someone else's problem who is less informed. You shouldn't be fine foisting problems on people too ignorant to deal with it.

Cracking was the term for that. It's an honest misconception though.

We don't exactly specialize in PR.

Heaven forbid the financial system should be inconvenienced. Nevermind that downstream of all the technologies to lockdown finance are the tools to enable an oligarchic tyranny.

PHP is basically the Ur-implementation of Server-Side rendering and processing. JSP's and a bunch of other technologies are basically "PHP, except in-house" relative to other programming languages. As one of the earliest impl's of that that I'm aware of, it's also got the beefiest stdlib, and most eyes-on time. It was basically the JS of it's era. The value-add was that you once you implement the templates & widget toolkits, your designer could mix and match those elements for an arbitrary set of UI impl's without having to worry about leaving the php ecosystem. (I.e. abstraction + 1), and you get that "dynamic web page" experience where pre-PHP, you didn't have it short of writing a task specific, full featured native client, which was a different impl for each OS, and often meant implementing Yet Another Bespoke RMI implementation to get to your data sources anyway. PHP allowed abandoning the windowing toolkits and finicky clients, and just using a web browser + http. The drawback being all the dynamicity was entirely dependent on the server-side, meaning scaling your user population required beefier and beefier servers since the server was doing all the work. Eventually, the blight of JS happened, and the architect's realized they could dump the rendering work on caller's machines. It's all about tradeoffs. In a world with clients which were much less powerful than server hardware, and sketchier network speeds, PHP made the most sense. With hardware capable of running at clock speeds on par with server hardware, and broadband speeds broadly available, there's a case to be made for making the caller's hardware do more of the work. Personally, I think the server pages ultimately kept the incentives aligned better, but no one really asked me, and apparently the bean counters like externalizing costs wherever they can.

Said defect is called *avarice". Left untempered, it's one of the most destructive of vices.

Doubly recommend turning on show dead. You'll learn a good deal about implicit biases in the community as well. It can be fascinating and eye opening to see what gets buried, and a well placed vouch can go a long way toward bringing back to the forefront worthwhile discussions.

>One in particular, about sharing secrets, that had not crossed my mind (I have found that virtually no one ticks the "do not train on my data" box...):

When said button is in the basement, at the bottom of a broken set of stairs, locked behind a door that says "beware of the leopard", inside a filing cabinet, and implemented as

    dontTrain() { //NYI
    }

I wonder why.

You are part of the problem, sounds like.

>Software malfunctioned

AI cannot be allowed or viewed as an accountability sink. In point of fact, it shouldn't even be being used by anyone not verifying it step by step. The Operator and their employer are always accountable for the actions of the agent of only because they had their hands on the power cord, eyes on the logs, and did nothing to stop it once it started going away.

Any professional with any experience at software development should know that an unreliable software is a useless software. That's half of why it's so damn hard to understand and reason through.