Saik0

that is configurable by your admin. while it was useful for you, you should probably raise that problem to your admin.

And has been available for years… Why this is news today is beyond me. I’m pretty sure I saw these cables on hak5’s site over 5 years ago.

Most of the hardware itself was free(business decommissioned) or auction wins (4.5TB of ram out of a $600 auction, selling some servers paid the whole auction off). So quite cheap in that respect. And it’s not strictly private use. Lots of functions in there to keep my business going/make it easier to track taxes/auto billing clients/email/etc. Though only typically operationally, not as an income generator itself (eg, not hosting other companies stuff so much).

And yeah, if energy was 10x more expensive (I think it was you or someone else that said $0.60 per kWh?) I’d probably rethink my situation/stance a bit.

But 3kW service is awfully low. Standard around here is 200amp service to a house (at 120v, so 24kVA service), 100amp (12kVA) if you have gas utilities handling range/heating, as A/C is heavily required where I live. My PV setup is rated 15.9kW, though caps out at 11kW on the best days. I can’t imagine living off of 3kW. My desktop uses 1/10th of that. My idle usage in my house minus the servers is ~2kW. I can see why you’re squeezing Watts. Some googling shows Italy being a country that does this… You probably are in similar situation as them where A/C isn’t really common, heating and cooking isn’t electric based, etc… Most of the year I’m not allowed to even make a fire, so I’m forced to rely on electricity.

But no SUV here… 1 hybrid sedan for this family of 4. Gas costs too much and we drive too little.

And here I am with a 5 server cluster, 2x custom servers running opnsense for redundancy (8gbps internet connection needs real horsepower for IDS/firewall/routing), and a 36 bay storage truenas node… that’s getting upgraded to 72 bay version for more drives (34 additional drives ready for install RIGHT NOW)… I see your 50 and 38 W… and raise you

This

2200-ish watts? Oh… and cooling the servers to keep them to about 75 degrees intake temp.

So really closer to 3400 watts.

Taking your numbers of 6 watts saved per drive would only save me 180w currently and 432w after I install the additional 32 drives next week. I’d still be in the 3kW territory.

…

I also have solar…

I generate (orange) enough to export (purple) a little during the day… but that’s about it… Battery (light green) usage just kills peak hours.

The electrical usage costs me about $100-110 a month in electricity after solar ($0.06 per kWh), probably closer to $150 if solar wasn’t eating up a bunch of it. Less than subscriptions to all the shit that I’m hosting for myself by a long long shot. Forget the family and other users.

Way to comment on something from over a year ago. And no nobody lied to me. I read the manifesto that Hamas publicly published.

Who knows how many meetings they’re involved in to constrain the crazy from senior management?

This is more than half of my job. Telling the company owners/other departments “No”. Or changing their request to something actually reasonable and selling them that they want that instead.

No, that’s an entire external service + a script.

Requires running https://github.com/Cloudbox/autoscan and that custom script.

At that point I might as well tell plex to rescan the library every x hours itself.

Edit: I forgot to add this even though I meant to

Autoscan, A-Train and Bernard are no longer actively maintained.

And that github… it no longer maintained.

It does name management on the files for other players. Such as plex, emby, jellyfin, or kodi. About all I see that’s any special here.

Edit: seems to also do some metadata magic for plex at the very least to make it somewhat usable.

Well… plex support in that it can chuck files into a structure that plex understands. It doesn’t seem to notify plex to rescan libraries…

Same on the official lemmy web UI.

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.

I would agree with you if there were a simple way to tell what the USB-C cable I have in my hand

https://caberqu.com/home/39-ble-caberqu-0611816327412.html

This would do it.

Yes. But there are lists of well known IPs that are serving DoH. So you can just block those. Obviously blocking 443 is not a good idea.

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.

Block all port 53 traffic from your network outside of your DNS server/pihole itself.
Block all known DoH servers.

If you want to get REALLY fancy you can write a NAT rule that will force any outgoing request on port 53 to route to your dns/pihole.

I do all of this. It’s actually funny to see the requests that were hardcoded to go somewhere. Giant fuck you to those companies.

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.

I think the issue comes down to whether the org in question does that 7 passes consistently on all discs, or if it just so happened to start that policy with those that had evidence on them.

No? If 1 is sufficient, any additional shouldn’t matter in any considerations at all. Could have simply been somebody who hit the preset on accident.

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.

so someone using it is being very intentional.

Not if you’re used to taking DoD requests. It was my default for a very long time because I simply defaulted to it for compliance reasons.

It’s also considered wildly overkill

Absolutely is. Doesn’t mean that people like me aren’t out there in droves.

But SSDs make this all moot and HDD are being phased out of many environments. SSDs with chucking the key is more than sufficient as well.

It is… It’s literally a preconfigured option on the dban selection list.
Source: My memory… but if that’s not good enough, here’s wiki too.

https://en.wikipedia.org/wiki/Darik's_Boot_and_Nuke

and DOD 5220.22-M (7 passes) are also included as options to handle data remanence.