Little bit of everything!

Avid Swiftie (come join us at !taylorswift@poptalk.scrubbles.tech )

Gaming (Mass Effect, Witcher, and too much Satisfactory)

Sci-fi

I live for 90s TV sitcoms

  • 19 Posts
  • 638 Comments
Joined 1 year ago
cake
Cake day: June 2nd, 2023

help-circle




  • I went on facebook as an experiment for a couple of weeks, try it out again, even take part.

    Algorithm quickly caught on that I liked some interests - transit, trains, Taylor Swift, and EVs.

    It was fine for a while, made a few comments, engaged with a few people, both who agreed and not.

    All of a sudden over the last week I’m seeing just pure propaganda - BS “headlines” like “50% of Americans regret buying their EV”. Absolutely unproven horseshit, but there it is.

    Facebook is absolutely culpable in this mess. They straight up promote it, and for me I was pro all of that stuff, it switched on me.











  • Exactly right there with the not worrying. Getting started can be brutal. I always recommend people start without worrying about it, be okay with the idea that you’re going to lose everything.

    When you start really understanding how the tech works, then start playing with backups and how to recover. By that time you’ve probably set up enough that you are ready for a solution that doesn’t require setting everything up again. When you’re starting though? Getting it up and running is enough



  • WD Red has always been my go-to, and in the last 8 years of homelabbing I haven’t had a single one fail. Blues and Greens are not build for NAS operations, and you’ll see them fail. Toshibas I haven’t had a single one make it past a year, except for their gaming drives.

    If you want the shortcut, the WD Elements usually go on sale at Best Buy regularly, and they’re always a WD Red or White, which will also work. All of my drives have been one of those. You just shuck the internal drive out of the enclosure


  • (instance admin here, but for a small one) woof well, for me, I agree, but I wouldn’t use that wording.

    Lemmy for sure isn’t a plug and play site. Setting it up took leaps and bounds, learning way more about nginx than I ever really cared to, and figuring out documentation that was very clearly out of date. Very little logging or error messaging exists to help with that problem.

    Very little errors exist at all, it’s very much a “happy path” project. That’s why we get constant spinners everywhere, because when an HTTP error occurs there’s no actual error message. (Come on guys, just add it to your standard HTTP messages, if statusCode < 200 || >= 300 then show a toast message).

    But yeah, the moderation tools have to be the worst. Lemmy has an amazing development group that’s separate from the main developers who have patched together a good set of tools, from automods to CSAM and illegal scanning, huge props to them - but these issues are routinely ignored by the main devs. I was shocked, honestly shocked that when we were under CSAM attacks that there was not an immediate roundtable of the head devs to try to solve the problem officially. Here was a problem that 99% of countries would immediately and gladly throw us, the instance admins, in jail over and they just handwaved it away. In fact, I don’t know that there was ever an official post about it, or even that there are things coming to help with it.

    I love Lemmy and being here, and the devs have done a great job at building this platform for us, but we’re at a critical point right now. It’s no longer software that is just fun side projects and building stuff that looks cool, it has some real issues now that it has a real userbase. I’m definitely one to say “But it’s FOSS, and other people can pick up and submit a PR” - but it also says something when the head devs just completely ignore a massively huge issue with it.

    Bugs and caches and that sort of thing I can overlook. Those I can wait on and see them get smoothed out over time. Actual issues that could land me in jail or get the feds to beat down my door? Those I kind of expect a fast response.

    So, I’ll say I’m extremely conflicted. I want to host lemmy long term, and I’m happy to bring the fediverse to a few more people, but the csam attacks really altered my view of the devs.

    Edit - because my favorite manager said “Bring me solutions, not problems” a few things that would really help immediately -

    • Integrate db0’s CSAM checker natively, more or less a plug and play option, or a checkbox. His checker sits at an endpoint. The admin page of lemmy could easily have you plop in the endpoint and it would start checking
    • Have an image management portal, with capabilities to:
      • Auto remove images after X time (to help with ballooning storage costs)
      • Perma-delete images and users (maybe blurred too if the CSAM checker flagged it, so I don’t need eye bleach) (Edit again, 0.19.4 might have fixed this, I need to upgrade so I’ll see)
      • Federating image purges, so one purge on one server will force purge it on everyone else’s
      • ~~Disabling of caching other server’s images ~~ (Edit again, I see 0.19.4 just dropped which has this, so this is good). This way I’m only responsible for my own users.
      • View images that are not related to a post (DM’d messages that I’m hosting, or people just uploading images to my site)
    • Bring in a logging system into the UI itself, so I can keep tabs on the error logs. I can pipe them somewhere, but this would be a major plus as an admin