• 0 Posts
  • 143 Comments
Joined 3 years ago
cake
Cake day: June 18th, 2023

help-circle

  • Cleaning isn’t an inherently undignified job

    So what? It is still a job that most people don’t want to do. It is a job that people do when they can’t find other work. And typically the working conditions are poor.

    The point isn’t whether anyone would “do fine in a job like that”. The point is that very few people are signing up for those jobs voluntarily.

    For work that is genuinely unpleasant, there’s no reason I know of there can’t be non-monetary perks that would make it worthwhile.

    This I agree with. As a society we should be rewarding people who fill these very necessary roles. Janitors, especially those who work in medical facilities and have to regularly deal with biological waste, should be getting a lot more compensation.

    Regardless of whether that compensation is in the form of money or not, I don’t think that’s an example of anarchy. Providing such compensation would require some form of organized group that distributes it to the people doing the work, which means that group would have to collect whatever resources are necessary in order to distribute them, and then we’ve just reinvented taxes.






  • I know there is labor that won’t be done voluntarily, yes.

    For instance, cleaning shit smeared over the walls of a restaurant bathroom, or sorting through garbage to separate recyclables, or changing catheter bags and diapers for adult patients.

    Sure, somewhere in the world you might find a few people who are happy to do that kind of work. Are there enough of those people spread throughout every community to actually complete the volume of work that needs them?



  • Here’s a thought experiment:

    Imagine trying to operate a modern county hospital as an anarchist organization. For the sake of the experiment, let’s assume this is a miraculous money-free post-scarcity society and we’re not worried about the cost associated with anything or handling billing nonsense. We are absolving ourselves of all of the complexities of the accounting department, thus simplifying everything. Materials and labor are supplied for free, somehow (handwaving details TK).

    OK, so what we’re concerned with is system management. Inputs and outputs, and internal processes. Patient appointments, work shifts, task assignments, surgery schedules, emergency response, education and training programs, laboratory analysis, medication distribution, food distribution, waste disposal, supply requisition, shipping and receiving, inpatient and outpatient care, and above all sanitation for everything. The goal is to have the right resources in the right places at the right times. If you miss the goal, people die.

    Is this a system that can operate effectively without dedicated authority figures? without centralized management? Can a hospital be run effectively as a coalition of equals, with no empowered oversight?

    No.

    Why would the rest of a society that exists around a hospital be any less complex in practice?


  • More specifics are needed for a support request. Provide the baseline specifications please.

    What OS are you using? What is the make and model of the drive? Is it internal or external? USB? SATA? SAS? NVMe? A PCIe adapter? Is this a desktop, laptop, NAS, server, NUC, Raspberry Pi with an expansion board?

    For all we know you’re using a refurbished and relabeled SAS drive plugged into an adapter on an eSATA port on a 10 year old motherboard sitting in a cardboard box.

    Are you familiar with SMART? Have you done any diagnostics?




  • I wonder what you are securing against?

    OK, you’re familiar with vulnerability scanners and port scanners right?

    The threat model here isn’t really attackers specifically targeting your home network for any particular reason (unless you’re a LastPass engineer working remotely while running an exposed Plex server). They’re not looking for you, they’re looking for anything useful.

    The threat model is attackers using scanning tools to discover vulnerable systems connected to the Internet. All they need from you is an active connection and a system that can store data, from which they can host malware files for distribution to other targets or conduct attacks or just run a cryptominer (if you’re lucky and they’re not very ambitious). They can find this by scanning for open ports and then running a vulernability scanner to figure out if there’s some exposed hardware that can be exploited.

    An unsecured system is a hazard that could land you in jail when someone else starts using your device and network connection to commit crimes.

    Now, as long as you’re behind a standard residential network service, and your ISP is in control of your gateway device, you’re relatively safe from this. Most ISPs will block any traffic like that very strictly. If your ISP is in control of your gateway device then they’re responsible for its behavior (demarcation matters).

    But, most self-hosters run into limitations with their ISP blocking a lot of ports by default, because they want to access their personal server from outside their home, and so they take control by running their own gateway device or paying for a business connection which gives them complete control over which ports are open. This is where the risk comes in. You are assuming the responsibility for properly securing your connection to the public Internet, taking it off your ISP’s hands.

    If you’re going to do this, you should know exactly which ports you have open to the outside and why, and a general idea of what traffic you expect to see on them when and how much. Monitor that traffic at your firewall. Every other port should be closed and your firewall (on your router, gateway device, or better yet a dedicated OPNSense firewall) should be configured to drop packets received by closed ports (“stealth” mode). You don’t want it to respond that those ports are blocked, you want it to appear to not be there at all.

    Every other security implementation is a secondary concern for a home network. Yes you should patch your software regularly and you should practice deny-by-default and least-privilege as a matter of course, but you’re going to mitigate 90% of your risk by just not accepting incoming connections for anything you don’t need. Most vulnerable systems are discovered by automated scanning, so the less your system responds to external connections the better. If you’re going to worry about configuring, securing and patching one device, make it that front line firewall. And be very selective about which internally hosted services you expose externally.



  • You are running into the ultimate, and ultimately unavoidable, limitation of self-hosting, which is the self.

    You should run a VM on the VPS for Vaultwarden, with no other services in the VM except whatever you need to connect to it remotely. Keep it simple. Run an exact copy of the VM on your local server. Have the VPS instance push its database to the local instance regularly, to keep up with any changes that your users make. Make regular backups of the local instance.

    When you need to update the software, freeze an image of the local VM and then update the local VM, then when you’re sure it’s stable, copy the updated local VM to the VPS. If either the local or VPS instance crashes out, you should be able to recover (or reproduce) one from the other.

    In the end though, it is functionally impossible to ensure reliability by yourself. Hosting Vaultwarden on a VPS shifts the responsibility for running the underlying server and network connection to the provider, and probably removing the dependence on your residential network connection will be better for your family/users.

    You are still the weak point in your system. You need someone else who can log in to your local server, and into the VPS, and perform recovery if needed. There is no technical solution for this. You cannot be the sole admin, and also ensure reliability for other users.


  • One thing I think people forget, or were never taught in school, is that there was a time period (like, hundreds of years) when European imperialist nations went to war every summer. After the winter cold passed, and the ground dried up from the spring rains and snow melt, the armies marched. Mercenaries were a part of every serious national military, it was a common profession, alongside regularly practiced conscription. Destruction and death was an annual event for civilians, basically from the end of the Pax Romana until the end of the Napoleonic wars.

    Capitalism (coupled to industrialism) tied the wealth of nations to their productivity more than hoarded treasures or even land. Destroying a nation’s infrastructure, and killing its people, damaged its value, possibly irreparably. Going to war became expensive, and less rewarding.

    Reality is more complicated, of course, and there were a lot of other factors. The global market also created other avenues for the wealthy and powerful to exercise greed. Economic conquest was a practical substitute for military conquest. The relatively long periods without widespread international warfare are a historical anomaly.

    All of that sounds like I’m praising capitalism, and that’s not the point. My point is, I agree, capitalism was an improvement over the way things were before, maybe moreso than people realize in the present. Capitalism isn’t good, but it was a step on the path out of rampant violence - but only a step, not the end of the path.




  • There’s a new one being launched by a San Francisco-based startup that has some impressive specs, is powered by Linux, and isn’t looking to sell user data.

    yet.

    This is not an open source project. We covered it because the operating system for this is based on Linux.

    It’s (not) FOSS

    Some use cases the company points to include hands-free coding agents, reading board schematics mid-build, following a recipe in the kitchen, and keeping sheet music in view while playing an instrument.

    We’re trying really hard to come up with justifications to normalize people wearing a camera and microphone on their face all the time.

    Before you get worried, Raven Prism will ship with a physical cover for the camera that you remove when you want to use it and put back when you don’t.

    Which people will discard or lose within a month, especially if it looks like a weird extra piece attached to the frame.

    There’s also “Beakon” lights that illuminate when the camera is active, making it visible to both the wearer and anyone nearby.

    Which will get disabled almost immediately.