Nope. I don’t talk about myself like that.

  • 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle
  • Saik0@lemmy.saik0.comtoTechnology@lemmy.worldAll the other brands went along
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    1 day ago

    That aliexpress device doesn’t tell you what wattage or data speed the cable will max out doing. Just what wattage it’s currently doing (to which you’d need to make sure that the device you’re testing with on the other side is capable and not having it’s own issues). Also can’t tell you if the cable is have intermittent problems. If all you care about is wattage, then fine. But I find myself caring more about the supported data speeds and quality of the cable.

    But yes, I agree that cables should just be marked what they’re rated for… However it’s possible well built cables exceed that spec and could do better than they’re claiming which just puts us in the same boat of not really knowing.

    Edit: oh! and that aliexpress tester is only 4 lines(usb2.0 basically)… usb 3.0 in type c is 24 pins… You’re not testing jack shit on that aliexpress. The device I linked will actually map the pins in the cable and will find you breaks as well.




  • So am I. I’m not sure what you think wasn’t relevant. It’s a literal DoD spec. Yes that spec is outdated, but it’s still in Dban.

    You coming out of nowhere talking about how the DoD spec itself is “dead” doesn’t change the fact that it’s available and probably still used by many people out there. I’m willing to be that several companies have the old DoD spec embedded in their own SOPs. And I was always talking in the context of the contract work I did long ago which WAS to the old DoD spec regardless.



  • That was basically the workflow. On smaller drives you could do one when you get in, one at lunch and one before you left. Eventually drives got large enough that it was just once in the morning and once before leaving.

    I’ll overdo it.

    Half the contracts you didn’t know if they wanted the short wipes or long wipes. So you just do long wipes to cover your ass. It’s not like there was a rush, it was a simply menial task that became a second nature set of bashing the keyboard. Like typing some of my passwords and pins… I have no fucking clue what they are anymore… but put in front of the keyboard and I can type them by muscle memory.



  • Congrats? DBAN was made prior to 2006… IT people existed before 2006. What’s your point? You think that people just spawned into existence in 2006 with decades of IT knowledge? So like I said… “It WAS my default for a very long time because I simply defaulted to it for COMPLIANCE reasons”… eg. my contracts at the time required it and I ran boatloads of wipes.

    Regardless… DOD 5220.22-M now states

    The National Industrial Security Program Operating Manual (NISPOM) is now Part 117 of Title 32, Code of Federal Regulations.

    So let’s go look at the NISPOM stuff which says… NOTHING! So what you end up with is companies referencing the old DOD 5220.22-M because old government contracts will actually say that specific document in contracts as something that must be adhered to for a long long time. So even though it “died” on 2006, contracts may not be renewed for some time after that which still keeps the document alive.

    Now DOD 5220.22-M actually specified and defines short wipes (3 pass) and long wipes (7 pass). And in theory, could be superceded by NIST 800-88 (and probably is the default on modern contracts). And regardless of all of that… DoD internally has it’s own standards, which after wipe often requires degaussing or outright destruction of the disk, I remember having a dedicated device for it that would document serials and stuff. I’d have to pull up my army documents to remember which specific rules required that type of stuff, but I’m not going to dig out shit from 2010 just to argue with someone on lemmy.

    So I guess this boils down to… The world didn’t spawn into existence in 2006. People are older than 2006 and are allowed to talk about their experiences from before the “old times”.

    Edit: And in current contracts… all our shit is NVMe and secure erase. But I’m willing to bet muscle memory would still kick in for me if I saw the DBAN screen.




  • That’s a completely fair assessment. They’re definitely still quite expensive.

    But I already have a 7950x3d and a 7900xtx… My machine is as good as it’s getting. I had the budget, and have some needs that the larger screen meets.

    Has it been worth it? Eh… situationally it’s been super nice. But I can’t say it’s been worth the extra $600 I paid above the next flagship spec quite yet. My first samsung fold though… Verizon paid for me previous phone and paid me more than I paid for it… So that one was definitely worth it.


  • No. The implication of my “comfortability” with google holding my credentials is that they can use it, or leak it. You wouldn’t know that they did it. I said I don’t trust them, you said “if google did pull something”, I’m saying you wouldn’t even know if they DID pull something. They control such a vast amount of infrastructure and resources that they could do a boatload of malicious stuff and you’d never know. Hell they do some quite malicious things with AMP, ads, pushing nonstandard shit in chrome, etc… But you do you. Give them all your shit. They won’t complain. But you won’t catch me in that boat.





  • My Samsung definitely had issue with the interior screen protector… It’s lifted at least twice on me. Samsung paid for both and took about an hour each time to replace at their authorized center.

    I’ve had no issue finding cases for either phone though.

    The samsung was narrower… the pixel fold isn’t. The front screen is quite fat. almost too wide for me… but that might just have been me being used to the samsung.

    And most of the time I prefer pulling out the laptop too. But the phone has definitely save me several times where laptop wasn’t around and fixing it now could be 5 minutes vs driving an hour to get to my desktop/laptop and fixing it there.

    They’re not perfect, and not amazing for every use case… but I fit snugly into one use-case that has made them great for me. And since the pixel fold is GrapheneOS capable… I’m quite chuffed about it.