• 1 Post
  • 242 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle



  • It really depends on what your data is and how hard it would be to recreate. I keep a spare HD in a $40/year bank box & rotate it every 3 months. Most of the content is media - pictures, movies, music. Financial records would be annoying to recreate, but if there’s a big enough disaster to force me to go to the off-site backups, I think that’ll be the least of my troubles. Some data logging has a replica database on a VPS.

    My upload speed is terrible, so I don’t want to put a media library in the cloud. If I did any important daily content creation, I’d probably keep that mirrored offsite with rsync, but I feel like the spirit of an offsite backup is offline and asynchronous, so things like ransomware don’t destroy your backups, too.



  • I don’t spend any time, awake, in my bedroom. TV is in the living room, where I spend my idle time. I can hear through the walls, though, that my neighbors spend a lot of time just hanging out in their bedroom, and that there’s a TV there. So, I suspect, if you’re in a home with multiple people, that having a TV or entertainment in each bedroom is more common. Essentially treating the bedroom as a private apartment within the larger space.






  • tburkhol@lemmy.worldtoSelfhosted@lemmy.worldISO Selfhost
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 months ago

    Wonder if there’s an opportunity there. Some way to archive one’s self-hosted, public-facing content, either as a static VM or, like archive.org, just the static content of URLs. I’m imagining a service one’s heirs could contract to crawl the site, save it all somewhere, and take care of permanent maintenance, renewing domains, etc. Ought to be cheap enough to maintain the content; presumably low traffic in most cases. Set up an endowment-type fee structure to pay for perpetual domain reg.


  • tburkhol@lemmy.worldtoSelfhosted@lemmy.worldISO Selfhost
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 months ago

    At least my descendants will own all my comments and posts.

    If you self-host, how much of that content disappear when your descendants shut down your instance?

    I used to host a bunch of academic data, but when I stopped working, there was no institutional support. Turned off the server and it all went away (still Wayback Machine archives). I mean, I don’t really care whether my social media presence outlives me, the experience just made me aware that personal pet projects are pretty sensitive to that person.


  • As a long-term non-exerciser, routine and coupling it with a reward was definitely key. I started out just walking, and walking to get lunch was a key motivator. Upgraded to a rowing machine, and it doesn’t even feel like a chore to sit on the machine and watch a movie in parts or a show, going on 5 years.

    Still have to figure out how to get some strength work in there. Just can’t seem to find a system to consistently do a few push ups, pull ups, and stand ups.


  • For me, the effort of going somewhere to exercise is a big impediment, and I’m self-conscious exercising in front of people. The low barrier to start a daily workout wins, hands down.

    Others find camaraderie just having other people involved in the same process, or really enjoy the variety of machines and options of a well-equipped facility.

    You have to figure out which type of person you are. The most important thing is just to do something. (Unless you have specific, Jason Momoa-type goals in mind)






  • Back in the day, I set up a little cluster to run compute jobs. Configured some spare boxes to netboot off the head-node, figured out PBS (dunno what the trendy scheduler is these days), etc. Worked well enough for my use case - a bunch of individually light simulations with a wide array of starting conditions - and I didn’t even have to have HDs for every system.

    These days, with some smart switches, you could probably work up a system to power nodes on/off based on the scheduler demand.