🚀 Seen my posts and want more? Dive deep into the issues with Big Tech at Escape Big Tech!

💡 Need FOSS-focused software solutions? Reach out on Matrix at @dannym:balooga.xyz!

  • 16 Posts
  • 169 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle




  • The medical industry has very bad security practices in general from what I hear. You can basically expect that your medical history is accessible to lots of companies that should have nothing to do with it, not just Microsoft. Pretty much all of your health data is probably in the hands of at the very least Google and Amazon and the sad reality is that people don’t care about security and privacy until it’s too late. The number one server provider for anything healthcare related is AWS and the legal requirements they have to follow for data protection, HIPAA, are the sort of requirements that only a politician would think are actually beneficial to keeping data secure.

    EDIT: to be clear, I hate it, and I think you made the right choice, but sadly expecting privacy of our medical information is gonna keep being a battle, until the medical industry starts taking it more seriously






  • That’s not the issue. You can attempt as many passwords as you want in actually secure password managers as well. KeepassXC for instance IS secure, you can still brute force the password, but because of the hashing algorithm they use it’s extremely hard. With PKZIP if you know some of the words in the file, you can easily guess the password in just a few hours because the encryption algorithm it uses isn’t secure









  • Pretty clear you either haven’t read the bill or grossly misunderstood it. What you describe is not proposed legislation - it’s the current reality that individuals and independent repair shops already live with.

    The 2024 variant of the bill isn’t actually publicly available online, but here’s last year’s WIP text:

    https://olis.oregonlegislature.gov/liz/2023R1/Downloads/MeasureDocument/SB542

    Absolutely, the bill you mentioned is the one I was referring to. It does state that manufacturers must provide documentation, tools, and parts to both independent repairers and owners under fair terms. However, the real issue lies in how “fair and reasonable terms” are interpreted and applied in practice.

    Here’s a quote from Google’s actual response:

    User safety should be a top priority. Improper repair can be dangerous—especially if individuals use faulty parts or are unfamiliar with safety critical components, such as lithium ion batteries.** Legislation should acknowledge the risks borne by unskilled repairers and allow original equipment manufacturers (OEM) to provide parts assemblies rather than individual components to reduce the risk of injury.**

    Doesn’t scream right to repair to me, let’s continue.

    Right to Repair regulation should focus on: Devices that are repaired by an OEM’s existing repair offerings3 Right to Repair legislation in the United States is focused on leveling the playing field between OEM repair and independent repair offerings and putting consumers first, which we fully support

    So, if they don’t repair their devices and only replace assemblies, they’re not required to do anything for RTR, how convenient!

    Right to Repair regulation should focus on: Parts that are provided by an OEM’s existing repair operations

    Hmm… So the easiest way to comply with the law is to not do anything

    Policies should encourage repairers and recycling centers to recycle or to dispose of e-waste responsibly. We believe repair can be an important mechanism to reduce the large and growing problem of e-waste

    Classic corporate green washing, this doesn’t mean recycling, it means break products, into as many parts as possible and dispose of them.

    This is what recycling means to big tech:

    Those are icloud locked iphone mainboards that have had their chips drilled through (this is "recycling). Some extremely smart people have figured out how to scrap them for parts, but that’s the ingenuity of actual repair people, not Big tech’s recycling.



  • there is nothing wrong to make money from their hard work

    I assume you didn’t read my parent comment or perhaps you extrapolated on my beliefs without asking. I even proposed a direct way to ask users to pay.

    you cannot and should not force developers to work for free if they don’t want to.

    My word, of course not! Where did you get the impression that I want that from? I would NEVER propose something like that, as it stands against everything I believe in; in fact if you read through my history on lemmy I am certain that you’re gonna find plenty of proof of that.

    I stand by the original meaning of the word when I say FOSS. It does NOT mean gratis; the misuse of the term FOSS as gratis is my biggest pet peeve. I don’t care how much you charge for your software, if I like the software I will pay for it, exactly how much you’re asking, without a problem.

    The F in FOSS stands for Freedom, not price. I have paid for most FOSS software I use on a regular basis and I’m a HUGE proponent of paid FOSS and I have, multiple times, asked FOSS developers that release gratis software to PLEASE open up donations; I do this constantly and I think I may even have done it here on lemmy once or twice.

    If you want free software then there are FOSS options out there and nobody forces you to use Boost.

    Indeed. My preferred client at the moment is the web ui on desktop and jerboa on mobile. Those are FOSS and developed by the developers of lemmy themselves (to whom I HAVE donated to). But I was thinking about switching client, which is why I asked for the code for Boost to see if it’s software I would be willing to run on my device (and pay for!).

    In fact I will even go as far as to say that it is your RESPONSIBILITY as a user of FOSS applications to donate if you can.


    To me if software is not FOSS it signals one thing: they are doing something they don’t want me to know about, sometimes this is acceptable (tho never preferred), but that’s the exception, not the rule.

    Being able to decide what software runs on your machine should never be a point of contention. Non FOSS software is always a trade off, and for most things (including lemmy clients), it’s not one I’m willing to make, nor should you!