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
  • 220 Comments
Joined 2 years ago
cake
Cake day: March 4th, 2024

help-circle


  • I think that unless you have some way to enforce accuracy, it’s meaningless and AFAIK automatic detection tools are no better than chance and to my knowledge, getting worse.

    An AI bot operator isn’t going to tag their material as [AI], more likely than not they’d attempt to use [NOT AI].

    I’d also point out that while lemmy doesn’t (yet) support hashtags, any “tagging” would probably benefit from using the existing method using a #tag.

    Ultimately, you need to ask yourself, is undeclared AI that goes undetected by the community a problem, or the new “normal”?

    I’ll note that I’m not a proponent of Assumed Intelligence and think that when the bubble bursts we’re going to be in a world of hurt, but with a little luck the billionaires will have lost their shirts in the process.



  • I think that this is symptomatic of a much larger issue at Mozilla, leadership, or rather, lack of leadership. AI, tracking, privacy, funding, the list of crazy coming from there appears to be just ballooning.

    I see no evidence that they deal with actual bug reports, no evidence that they care about users and no clear path being forged, unless they want to enshitify their business, in which case, that appears to be going swimmingly.








  • 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.