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

  • 127 Posts
  • 1.18K 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.










  • I didn’t see any other video in relation to this.

    As I understand it, the author of the AGPL has recently posted about software that’s including closed source modules and the person who was told to cease and desist has documented exactly what the issue is based entirely on Bambu Labs’ source code. There’s also discussion about reverse engineering.

    I don’t know if any of that is new ground or not, as I said, this is the first video I watched on the topic, it randomly turned up in my feed.


  • I think that below is probably a fair summary, but I note that I’m a FOSS user and contributor and this is my opinion.

    There is a case to be made that there is an AGPL violation here and the documented evidence and commentary is growing.

    More people with knowledge on the subject are apparently weighing in.

    As a software developer, I think that this case is important because there is a growing trend by companies and individuals to hide source code from the community, even if that software was originally licensed to them under an irrevocable licence. In this case, as I understand it, the Bambu Labs software is a fork of Prussia Slicer, which itself is a fork of Slic3r, all of which is licensed under the AGPL.