I'd like to remind everyone of the "vampire effect" of wall-wart chargers - if you just leave them plugged into the wall waiting for you to connect a device, you're constantly wasting a bit of electricity. That should also be involved in the efficiency decision of using the already plugged in computer or laptop.
"This is how I spent the previous month, creating these 3D printed objects to achieve a goal", not "I am about to pass away and I spent my final month 3D printing these forgettable objects"
Let's say there is a user lmicroservice. I'm on a UI team. I don't get to tell the user service team what, or when, to implement any features.
I'm tasked with making a page displaying all the users who have a birthday this month.
User API service can only search by user id, email, display name, or nickname.
Now instead of just querying the goddamn database, a one line fucking SQL statement, I have to deal with the user team, getting them to first off even admit that my use case is valid, convince them to work on the feature, coordinate with them to make sure the query works, sorts the data the way I need, etc, et. al, blah blah blah.
They already have the next 3 sprints full so I'm sitting on my ass for the next month before I can test.
Meanwhile they decide they're gonna implement a super generic thing, and so despite me working on code that we talked about using an interface we talked about, they implement something else so i have to throw out half my work anyway.
Then when I finally start using it I find, oh, it doesn't support a sort, only returns 100 results max with no pagination, so if there's 200 this month with a birthday fuck the 2nd hundred they don't show up because they're implementing bare minimum and the rest is slated for another sprint.
And it was then, your Honor, I grabbed the lead dev for the user microservice and tossed him off the 9th story of the building.
No one has ever recovered overwritten data, as far as anyone can tell. Go look it up. The technique was only a theoretical attack on ancient MFM/RLL hard drive encoding (Gutmann's paper). Even 20 year old drives' (post 2001, approx) magnetic encoding are so small there isn't an 'edge' to read on the bits. A single pass of random data is sufficient to permanently destroy data, even against nation-state level actors. Certainly enough for personal data.
Most of the patterns in the Gutmann method were designed for older MFM/RLL encoded disks. Gutmann himself has noted that more modern drives no longer use these older encoding techniques, making parts of the method irrelevant. He said "In the time since this paper was published, some people have treated the 35-pass overwrite technique described in it more as a kind of voodoo incantation to banish evil spirits than the result of a technical analysis of drive encoding techniques"
NOW THAT BEING SAID there is no harm in doing a secure, 35-pass overwrite other than the time, energy and disk wear. If watching all the bit-patterns of a DoD-level wipe using DBAN on a magnetic disk tickles your fancy, or you think this is a CIA misinformation campaign to get people to do something insecure so they can steal your secrets, please just go ahead and do a 35-pass overwrite with alternating bit patterns followed by random data. I can tell you that I believe in my heart-of-hearts, that one pass is sufficient.
Brave browser does an okay job, but remember under the hood everything is just a re-skinned Safari browser. There are content blockers, but AdBlock sold out (allows ads) and uBlock Origin doesn't work on iOS due to limitations Apple has in place.
no. POTS (plain old telehphone systems) still exists. None of that is VoIP, although it's almost certainly encoded to digital and sent as packets. VoIP is a very specific thing, and not the same as cellular or landlines.
listless @ listless @lemmy.cringecollective.io Posts 27Comments 185Joined 1 yr. ago
Shaka, when the walls fell