I don’t have direct experience, but when I looked into it my takeaway that NBD was unable to reliably deal with network interruptions as well as iscsi.
I just bought a few more Intel 310 Series 40GB mSATA ssd’s on eBay for $10 each. They are ancient and comparatively slow, but reliable and extremely low power, so much so they can be perfectly powered by a USB 2.0 port in an enclosure if needed, and don’t need a heat sink. My original 80GB version ($190) that I put in my W520 thinkpad in 2011 is still going strong.
Basically I like to use them as a cheap “better” thumb drive, putting ventoy on them with no concern for space, along with a fat32 partition for bios updates.
These along with a nanoKVM box my siblings can attach to the computers I built for them makes remote troubleshooting relatively painless when rustdesk isn’t sufficient.
I’m an agronomist and while I don’t directly deal with that level of things, what you wrote sounds roughly like what goes on for the hazelnut industry here in Oregon.
It’s for sure not fair for you personally.
However it’s also not fair the rest of us have do deal with Russia’s hacking and propaganda organizations that are either directly state run or willfully tolerated. IP blocks don’t fix everything, but they do (or did at least) counter a good portion of the bots for no effort.
You live in a country that is awful to itself and everyone around it, but that’s not something we can fix.
It’s unfortunately not something Russians can fix either.
And I understand the desire to just blackhole all RU traffic, but if everybody starts doing this, it would result in two things:
1. Ordinary Russians who want to just read your website will have to jump through hoops (or probably find another source; I don’t live in Russia anymore but find myself clinging to the latter option for websites that decide to block all non-US traffic)
2. Hackers will... use botnets to proxy their traffic? It’s not like they don’t have options, they just pick lowest hanging fruits for now.
---
The proper solution to the hackers problem is:
• Use static sites for static content
• Practice good security for webapps, and maybe use a WAF
>An estimated 1.36 short tons (1.23 t) of uranium and 46 curies of alpha contaminants traveled 80 miles (130 km) downstream[8] to Navajo County, Arizona, and onto the Navajo Nation.[2] In addition to being radioactive and acidic, the spill contained toxic metals and sulfates.[9] The spill contaminated groundwater and rendered the Puerco unusable to local residents, mostly Navajo peoples who used the river's water for drinking, irrigation, and livestock. They were not warned for days of the toxic dangers from the spill.[2]
>The governor of New Mexico, Bruce King, refused the Navajo Nation's request that the site be declared a federal disaster area, limiting aid to affected residents.[10] The nuclear contamination event received less media coverage than that of Three Mile Island, possibly because it occurred in a very rural area not served by major media. The spill also happened in Native American country, among a community who reportedly did not have their concerns addressed by medical authorities.[11]
My understanding is that FDIC deposit insurance only protects against bank failure, not fraudulent activity. Getting your account drained by an attacker may or may not be covered by a patchwork of other laws at various levels, and you could very well end up shit out of luck.
I think this is a good point, insofar that how bacterial resistant the stethoscope is relevant. Stethoscopes made of stainless steel are going to beat anything 3d printed by a significant margin.
I doubt the diaphragm which actually touches the body, or the flexible tubing of expensive scopes can be sterilized in an autoclave. This diaphragm here is cut from cheap plastic and easily replaceable, the tubing is silicone. I do not believe the flexible tubing on the expensive ones is usually silicone and replacement diaphragms probably cost as much as this whole DIY scope. Metal is resistant to heat, but porous still, so disinfecting with alcohol isn't enough, if you got nasty on it. Never in my life have I seen any doctor pulling a stethoscope from a sterile paper bag. It's likely not as clean as you want it to be.
I believe, in practice you should avoid putting it directly onto the heart, keep a layer of healthy skin in-between. Given the scope of the scope, that may be acceptable, considering the alternative may be direct skin2skin contact with your patient...
But yeah, generally, 3D printed objects are not easy to sanitize properly.Eg. their porosity makes them not safe for repeated food contact. I mean, the glass transition temperature of ABS is 105°, so you could dip it in boiling water, but that's not enough for making it sterile and consequent water inclusions are a welcoming place to start a new family a few hours later for any remaining spores. You could try fractional pasteurization and heat drying, in a pinch, at the end of times.
It definitely doesn’t help that prints from filament printers are very porous, 100% infill or not. Maybe sealing it with epoxy after printing would help?
This seems like another case where the hobby has discovered the 3d printer hammer and forgot that cnc tools (lathe, milling machines) are often better and faster for the job. Or if plastic is what you want injection molding is something you can do on a hobby scale and it is much better (but unlike the others this isn't something you can go from CAD to widget)
In my experience it is very rarely the case that setting up machine tools is faster than 3d printing. And even when it's faster, it's not less trouble. And you have to go and acquire materials in suitable shapes and sizes, and deal with cleaning up chips and offcuts, and deal with deburring and cleaning the part after it's finished.
The 3d printer is always ready and always has material in the right shape. It doesn't make a lot of noise, it doesn't make a lot of waste, the parts come off the machine clean and dry and ready to use. It's really hard to overstate the convenience of 3d printing.
I seem to remember the fatal flaw with harvester AI was that once a harvester was returning to the drop-off building, it would "claim" it, and so any other harvesters would just do a dance around the building until the the first harvester arrived. As a result, a harvester that was further away could block closer trucks if it just happened to fill sooner.
Same, and agreed. It’s also annoying for everyone else who has to listen to the same few unit movement confirmation sounds hundreds of times in an hour.
https://forums.gentoo.org/viewtopic.php?p=4895771&sid=f9b7ac...
https://github.com/NetworkBlockDevice/nbd/issues/93
Whether that’s the case with the latest version, I don’t know, but it’s something you might test if you choose to try it.
reply