Onno (VK6FLAB)

Anything and everything Amateur Radio and beyond. Heavily into Open Source and SDR, working on a multi band monitor and transmitter.

#geek #nerd #hamradio VK6FLAB #podcaster #australia #ITProfessional #voiceover #opentowork

  • 7 Posts
  • 211 Comments
Joined 2 years ago
cake
Cake day: March 4th, 2024

help-circle


  • Have a look at your AWS billing console, since data egress is charged and downloading to verify is considered egress.

    AWS S3 supports data checksums where a checksum is calculated at AWS, which you can compare against a checksum that you calculate locally.

    This is an article that goes into how it works, but I’ve not (yet) tested it, but I’ll be following in your footsteps pretty soon.

    https://medium.com/@maureenosaghae86/check-the-integrity-of-data-in-amazon-s3-with-additional-checksums-3e51fe45f530

    As an aside, make sure that versioning is OFF on your backup bucket unless you specifically require and understand it, because even when you delete objects, they persist as a previous, all but invisible, and charged(!), version.

    My former backup software “helpfully” enabled versioning and I was left with a $600 monthly bill for six months while there was no actual backup being done due to a local hardware failure, until I figured out what was happening. I used that software for years and shudder to think just how much extra it actually cost.

    I will note that while I had a catastrophic hardware failure, I didn’t lose any data.

    Finally, if you’re storing data in Glacier, retrieval is charged at different rates, depending on timelines of access, so it might be that your backup software is using the slow tier to “save” you money.

    Edit: OP advises that they’re not using AWS, instead they’re using OVH. The object storage solutions appear to be mostly compatible, but I was unable to discover if the OVH implementation supports checksums.











  • Not sure how, or if, I’d want to install an Arch package under Debian, but it’s my understanding that the package I’ve raised a bug for under Debian implements, or is supposed to at least, the functionality you’re describing.

    What I haven’t found is a recipe that documents exactly how it’s supposed to work (not to mention, in a Debian way).

    I’d love to discover something that doesn’t start with instructions to remove all pipewire packages and install from source, since that completely defeats the purpose of running Debian Stable as the host.











  • I’m sorry, but no.

    Age validation is surveillance under the guise of “protecting the children”, which it spectacularly fails at for more reasons than I can count.

    1. Everyone has to validate their age, which creates a whole infrastructure that require documents that “prove” your age.
    2. A verified “under age” user will be added to a database by unscrupulous players, creating a honeypot for predators.
    3. Age verification isn’t universal, isn’t uniform and regardless of the jurisdiction in which it’s implemented, won’t actually prevent content from being procured from sources outside that jurisdiction.
    4. One source of objectionable content is another’s entertainment, legally so, given that laws are made in isolation from each other across borders.
    5. The result of such legislation is the effective censorship of content that some lawmaker finds objectionable, which will cause more harm than good.
    6. Operating System level age verification on open source platforms will spectacularly fail since they’re published outside the jurisdiction.

    So … no.


  • I understand your point and agree that this is the thin end of the wedge.

    What we’re doing here is discussing the phenomenon and I’m highlighting some concerns.

    I believe that this is how you get a dialogue happening which will effect change, which is what we’re both advocating.

    I think that age verification is about surveillance rather than protecting children and I think it should be fought at every level.

    This is me contributing to that fight.