996 karma · joined October 14, 2017
We need a clean start. A lot of layers can and should be rebuilt, and even if you do it without reducing functionality, I feel like in a lot of cases like we’ll be able to cut down the code significantly.
When I explain software bloat to non technical people, I say imagine you built a 10 story building, but every few years it was a story at a time with the renovations along the way.
Like there’s gonna be a lot of inefficiencies. Yea I know we refactor. But doing a clean slate rebuild. Knowing exactly what you need based on real world experience, it should work to really streamline stuff.
Second fuck Apple. Fuck all tech companies. And seriously fuck late stage capitalism. Foss or nothing. There should be a rule if you pay for it it has to be foss. This way people can still make proprietary but they just can’t charge for it.
We have zero privacy, zero security, all our politicians and all the corporations are against us.
Media parsing is an endless exploit vector. Like fuck. At some point you have to be like they (not just Apple) keep it broken
An yea I know foss gets these issues too. But if the only option was foss, then at least the whole world’s focus would be on it
I find that unless I have very detailed specs with rigorous completion verification/criteria (manually atm) or tests. It’s like 60/40 at best.
And adding all the tricks only gets me to like 75-80.
Tbh I am using cheaper Chinese models (ds4.1f) and only pay for the $20 plans from the us labs
I can understand the myriad reasons for why a company would be inconvenienced by that.
But on the other hand, it seems like a reason for me to never use the vendor
We will certainly see “front door” access as various places have or are attempting to enact client side scanning, id verified online access, software root of trust remote attestation, and the general attack on e2e.
Taken together your identity tied to unmodifiable software, necessary to access the web or modern economy with client side scanning and no e2e … is a front door.
All this has nothing to do with ai, bugs, hackers or security vulnerabilities, let alone backdoors
I think an optimal solution would be to have more seamless integration between harness and router roles. As each are only half the picture
Or did we forget software inherently is opinionated
Jokes aside this is seriously impressive and makes me want to try and see if I can register them as unique enough. I certainly can taste different water bottle brands difference, but going from that to saying what’s good for x recipe is pretty next level
Given the recent lpe vulns docker 100% won’t cut it.
And containers were never meant primarily as a security boundary anyways
but if not just your own work flow, have a dir dedicated to storing prompt history and then each file is titled with the commit id.
As for the flag just agree to some convention and toss it in the commit message
I upload all object storage stuff to bunny for live but also to backblace for backup.
I’ve always wanted to implement fail over client side for any asset over to bacblaze but seems like a lot of overhead
I have a friend, philosophy masters, smart, autistic and he is not entering the work force. Any tips?