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

  • 5 Posts
  • 128 Comments
Joined 3 years ago
cake
Cake day: March 4th, 2024

help-circle
  • I moved from VMware Fusion after a hardware failure and migrated to Proxmox. I use VMs to isolate client information and to test and use different OS versions and distros.

    I have a VM that runs Docker and connect to it via SSH for running applications I don’t want to install on my main workstation.

    My main workstation is also a VM.

    I came from bare metal Linux for years and found that I spent too much time recompiling kernels to make it work with my hardware.

    Now that everything is a VM, changing underlying hardware, and even hypervisor is trivial.

    If VMware hadn’t been bought by Broadcom and allowed me to virtualise x86 on Apple Silicon, I’d still be running VMware Fusion. UTM by the way is completely unreliable … I really tried.

    As it is, I’m running Proxmox on AMD.

    in summary, Proxmox allows me to build what I need when I need it virtually and it’s running on a standard Debian host.

    Edit: #$#__# autocorrect (unreadable -> unreliable)




  • What are you using to get it there and back?

    I’m asking because I had been using this for years and only after a catastrophic event, discovered that my “helpful” backup software had turned on versioning which AWS, also helpfully, doesn’t explicitly tell you when you attempt to delete old backup sets, showing no objects but charging you anyway.

    I did recover all my data after a catastrophic event, but it was an expensive experience to put it mildly.




  • Here’s some questions:

    • What happens when you die?
    • What happens if your house is burgled or catches fire?
    • How do you protect against pe(s)ts making themselves at home in your server?
    • What happens with a power or internet outage?
    • What happens with hardware failure?
    • What happens if you suffer dementia?
    • How are you dealing with AI bots?
    • How are you mitigating hacking attempts, security, authentication and exploits?
    • How are you dealing with data corruption?
    • How do you mitigate against ransomware having entered your systems?

    Note that I’m not picking on you, nor is this list comprehensive or in priority order. I’m trying to determine if you’ve considered these common issues and concerns associated with hosting stuff that has great sentimental value, if not actual value.


  • Onno (VK6FLAB)@lemmy.radiotoSelfhosted@lemmy.world•*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    17
    arrow-down
    3
    ·
    4 months ago

    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.




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