This is my primary account. All content contributions should only be coming from this account.

Other accounts owned by me are strictly for moderation purposes, and they are:

!cosmic_slate@lemmy.world

!cosmic_slate@lemmy.zip

!cosmic_slate@sh.itjust.works

  • 0 Posts
  • 35 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle







  • Meta is a trash organization and I think it’s completely fair to approach this with skepticism and some “fuck Meta” attitude. After all, Meta has a demonstrated history of promoting toxic social media habits.

    I think, broadly speaking, the fediverse’s exaggerated takes, misinformation that’s outright lies, and aggressiveness on this issue is showing that corporate owned social media isn’t the only harmful social media though.

    Facebook/Twitter/etc. had a financial incentive for divisiveness and uncivil discussion. The fediverse doesn’t have this incentive. It’s people voluntarily choosing to do it themselves on the platform they wanted to use as a lifeboat, except now it’s spread out across several servers.



  • Yeah, and your way can give you a free off-site backup.

    I guess if you really wanted to optimize to minimize the number of backups to take, you could just take one of the drives to the offsite location as part of the rotation.

    Say if you have 3 drives, you’d always keep your second oldest copy off-site. You want your most recent backup on-site for convenience of restoration, and you want your oldest on-site to use to take a backup without driving to your buddy’s place first.

    Let’s say your drives backup schedule is quarterly and with 3 drives, and the backup dates are: Drive A: Jan 2023, Drive B: April 2023, Drive C: July 2023

    Now it’s October. Use Drive A for your backup since it is the oldest. Now Drive B becomes your oldest

    Take Drive C, the now-second-oldest, to your buddy off site.

    Bring back Drive B from your buddy’s place since it used to be the second-oldest and is now the current oldest

    When it’s time to rotate the drives for backups, do a backup to the oldest drive first.

    Take , do your backup to your oldest drive locally first, then drive offsite to drop off your now-formerly-newest drive, and bring back the off-site drive as the oldest.


  • It might be worth keeping a text file log of what’s on there at least.

    Music is almost by-far the easiest to “restore”. In the event you lose everything and don’t want to spend time restoring it all, you can fling money at Spotify/etc and use a service that automagically imports playlists.

    The other stuff? That’s going to be insanely annoying to back up and insanely boring to rebuild if it’s a super-huge collection. Personally, if it’s something I think I’m going to watch in the future I’m buying the bluray/dvd and keeping it on the shelf (more-so for that it works as a conversation piece).

    I only care to have a solid backup strategy of stuff where there is a 0.0% chance to rebuild like personal documents, photos, and videos.

    Fortunately, since you “only” have 2 10TB drives (I’m assuming as a RAID1 array), consider this:

    1. Buy a 12/14/16TB external drive (just in case you upgrade disk space in the future, you’re using this drive so infrequently it’ll last you a few years easily)
    2. Take a full disk backup, put a physical label on it with the date, store the drive in a safe
    3. Wait 6 months, buy a second 12/14/16TB external drive – you’re almost guaranteed to get a drive in a different batch, and if you really want to amp up the paranoid factor, go for a different brand.
    4. Back up your data to the brand new drive, put a label on it with the date, toss it in a safe
    5. Wait 6 months, grab the oldest drive, replace it’s contents with a new backup, throw new label on it, toss back in safe.

    Generally speaking, this will give you at least 1 backup that’s no older than 12 months, and 1 backup that’s no older than 6 months. The only risky time where you’d lose a backup is when you’re replacing the oldest backup.

    IMO this 6mo strategy is a fine compromise on cost, effort, and duration of loss of data but tweak as you see fit.


  • There is no way “EEE” is applicable here outside of spreading FUD. The biggest risk to the Fediverse isn’t Meta, it’s other Fediverse users.

    The collective fediverse’s userbase is nothing more than a rounding error to Meta. They probably have to delete a magnitude or two higher number of spam accounts each day.

    Threads is 50x the size of the Fediverse and is growing significantly faster. Twitter users are almost certainly their priority.

    Meta is probably only using this as a way to convince regulators they don’t need regulation and so some director can put “changed the world” on their resume.

    If anything, it’s easier to pull people over because their friends who refuse Mastodon/etc aren’t holding them back.

    And the absolute worst case? Meta ends up contributes junk to the ActivityPub protocol or Mastodon, the community forks it, software gets patched to adopt the intricacies of whatever changes are needed to defang whatever controversial stuff gets added in, and everything carries on.

    The most realistic concern is the communities that provide a safe space for those regularly subject to harassment online may start getting unwanted attention from trolls. After all, this expands the potential audience from 2 million to 100+ million.




  • I agree the wealthy only became more wealthy during these revolutions, but the average standard of living for the lower classes also increased as well for both movements.

    For example, with the Industrial Revolution, newly created industrial jobs led to generally increased pay over rural jobs, improved transportation access, and started a focus on education.

    That isn’t to say workers weren’t abused in this system, though.

    I don’t think the wealth inequality problem is something that will get better or worse with an “AI Revolution”. There are plenty of jobs available to keep wages where they are. This could only be solved with tremendous government action or an incredible accident.


  • Displacement of workers isn’t necessarily a bad thing as long as it’s spread out over a long enough time for people to adjust.

    I suspect(/hope) we’re not going to see people losing jobs, but rather jobs in certain industries will just be created at a slower rate. Workflows take a long time to change in larger companies. I suspect a lot of value will be realized by smaller/just-starting companies who could more easily afford, say a $500/mo AI “task helper” service vs. hiring a $60k/yr position.



  • One of the easier options is going to be Ubiquiti’s ecosystem. You’ll be tied into it, but the video data is local. You can self-host the Unifi software yourself or grab a Cloud Key G2 Plus, which is a tiny ARM box running Ubiquiti’s software. Then you buy Ubiquiti’s cameras. At least as of a couple years ago, you could not pair this with any standard camera though.

    If you want a fair bit more effort but more flexibility, Zoneminder is an option. Most Amcrest cameras stream a feed over RTSP. You just need to configure Zoneminder to stream the feed.