• 1 Post
  • 319 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle

  • In the current market, you want a printer that runs Klipper. The system will typically include a web application that controls the printer (Fluidd, Mainsail, or Octoprint) running on an embedded RPi. You just access this through your browser, it’s not necessary to install anything on your PC.

    You will need to install a slicer software. The slicer is sort of the equivalent of a document editor - it’s how you prepare the 3D file for printing. Your printer manufacturer will probably recommend or distribute a particular slicer, but the file format used for 3D printing (G-code) is an open standard published by NIST. Any slicer software can be used to output gcode for printing - you can use whatever you feel comfortable with.

    Personally I reccomend Orca Slicer or SuperSlicer but there are many options.

    By the way, the entire market of home 3D printers grew out of the RepRap project that started 20 years ago. The original project was open hardware and software, and so almost all of the software in use today is open because open source principles were the foundation of all of it. There are some companies in the field who keep their stuff proprietary, but frankly I avoid their products and consider them to be anathema to the 3D printing community.



  • It can recognize tracks based on a profile of the audio content in the file, so even if they’re not labeled properly it can (usually) identify them. The biggest problem I’ve had with using it is that many artists have re-released or rerecorded songs, or released the same album in different years in different countries but maybe with one track missing or with the tracks in a different order, and sometimes Picard will pick an album release that you know is incorrect. It will reorganize the files, and there are lots of options for controlling how it does that (e.g. file renaming and tagging, output to the same folder or a different one, automation of bulk processing). But you may have to guide it a little, especially if you have many albums from the same artist because then you’ll have overlaps.

    I’ve found the best approach to handling this is to work on one folder/album at a time and make sure it picks the correct release year for metadata reference.



  • Even if the military targets killed by these devices are not considered war crimes, there were several civilians killed and those deaths should be considered war crimes.

    The problem with using a weapon like this is that you can’t possibly know who is nearby at the detonation time. To me this seems similar to butterfly mines which have been internationally banned for 2 major reasons:

    • they can end up outside the military operation area - they’re light enough that they can be blown off-course while falling, and will float downstream if they land in water
    • children pick them up because they look like plastic toys

    It seems like the same logic should apply - this weapon is not discriminating enough and is therefore not a legitimate military option.




  • Someone else has mentioned M-Disc and I want to second that. The benefit of using a storage format like this is that the actual storage media is designed to last a long time, and it is separate from the drive mechanism. This is a very important feature - the data is safe from mechanical, electrical and electronic failure because the storage is independent of the drive. If your drive dies, you can replace it with no risk to the data. Every serious form of archival data storage is the same - the storage media is separate from the reading device.

    An M-Disc drive is required to write data, but any DVD or BD drive can read the data. It should be possible to acquire a replacement DVD drive to recover the data from secondary markets (eBay) for a very long time if necessary, even after they’re no longer manufactured.


  • As always with attacks of this kind, it requires the air-gapped network to be first compromised through other means – such as a rogue insider, poisoned USB drives, or a supply chain attack – thereby allowing the malware to trigger the covert data exfiltration channel.

    This goes on the list with other attacks that are interesting in an academic sense but highly impractical for real-world attacks, like Van Eck phreaking.

    You have to deploy the malware that manipulates the RAM to get it to create the radio signal on the target system, and since we’re talking about an air-gapped system that means you have to be in the room with it already.

    This article is light on specifics, but a RAM board is not an efficient radio antenna and it operates at 3-5v, so the transmission can’t be very strong. The receiver will have to be nearby, and in a relatively noise-free radio environment. Electrical wiring in the walls would mess with the signal transmission, the wall material might just block it, and if the target system is in a metal case that’s electrically grounded (which is normal for desktops and servers) I doubt the signal would get out of it. My guess is that the receiving antenna would need to be in the same room.











  • Well look, not to be dismissive of what you’re saying, but the technical aspects of it really don’t matter. There is not (yet) any law in the US that would protect people from such surveillance, regardless of its current technical infeasibility. The point of getting people at large worried or upset about this is to get law established before it becomes a widespread problem, not after some company publicly admits to doing something despicable.

    The fact that companies are thinking about this, trying to accomplish it, trying to buy this functionality from other companies… that should be enough to scare people and get them angry. It’s certainly enough that we should all be talking about it, and publicly shaming them for the voyeuristic creeps that they are.

    There should be riots in the streets over stuff like this, because you can’t build a surveillance state without surveillance technology.