WYGIWYG

  • 0 Posts
  • 454 Comments
Joined 1 year ago
cake
Cake day: September 24th, 2024

help-circle
  • rumba@lemmy.ziptoSelfhosted@lemmy.worldntfy.sh v2.18.0 was written by AI
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    4
    ·
    7 hours ago

    A many-month-long refactor on code you’ve already written is less than fun. While I don’t love seeing a project I’m using being 80% replaced by Claude code, I’ve had Claude code look at some of my old projects and find underlying issues I was able to verify, and then suggested a more best-practice approach that I wasn’t even aware of. The real question is, was the claude output better than the original code? If it is and it has unit tests and many eyes on it, it’s quite possible that it’s better off now.

    I’ll sit on my current versions for a few months and let everyone else test it out :)





  • They wrote him to be cheap drama to give Stewart something to work with instead of just being a toned down, professional Shatner. We were all going to take the Captains side, seeing him as annoying as the Captain did. From the sounds of Wheaton’s book, he really wasn’t treated all that well by the show runners for being as young as he was. It’s kind of shitty to write a young kid in to be the conflict in a well respected characters arc.




  • Reverse proxy or configuration in the admin setting

    I didn’t say I could recreate Plex in my homelab. I said Jellyfin has short comings.

    Not the point of an open source server. That’s your issue.

    Moving the goal posts, The point of this exercise is to show how Jellyfin is a direct replacement for Plex. If you say that it is not, my points stand that it is lacking.

    caching the TVDB and movie DB.

    Every new user that moves from Plex to JF just hammers the fuck out of the free and open services. When one of those services has any issue at all, we’re collectively in bad shape. Plex has protection against this. It would be useful if we cached their stuff and threw it into a DHT, crowd refreshing it.

    There is a plugin to do OpenID

    This does not work for anything by pc clients. if you feed a roku, appletv, android TV, samsung television, visio… a 2FA prompt, it’ll tell you to get bent. THEN there’s the half assed fail2ban they made instead of surfacing the logs someplace that we could use real fail2ban, but now you have ME complaining that I can’t hack features into it where there’s no reason they’re not already there.

    Can’t comment on that. My library is small (<10TB)

    Their search sucks balls even for small libraries. They know it and they’ve been working on it for years. There are some crazy hacky solutions screwing with ports and moving traffic through elastic-cache. it’s extremely hacky.

    In the end, I’m using Jellyfin as my own personal media server and the media server for my family in my house. It’s not as safely designed as Plex, which itself has had some security issues in the past, but they have a paid team for that, You can’t even hack all the features Plex has into your home lab, I could stick it behind cloudflare and get SSL, some proper anti hammer, anti-abuse, but then I’m selling my watch habbits to cloudflare.

    I’m glad we have Jellyfin, I wish I had the skill and time to contribute, if they’d even PR a big-ass change like 2FA, last I heard they were standing on the “that might lead people to port forward it openly which would be less secure”, like people aren’t already doing that.

    I’d LOVE to get rid of my Plex, it’s just no where near as capable for my remote users, I can’t force grandma to run tailscale.




  • My wife started watching tt, I had just escaped the youtube client, reddit and facebook. I watched we swipe past 6 things and pause to watch one for 30 seconds, then swipe through 4 more. OHHH FUCK NO, NOT TODAY SATAN.

    I do have to admit, She gets her news a LOT faster than I do. But she also gets a tremendous amount of knee-jerk conjecture.

    Honey, did you hear X?

    Umm, that doesn’t sound quite right.

    grumble well I just saw it, but whatever




  • At home, I have a shit ton of in-wall HD’s behind TVs, a Dream Machine SE Pro. A 16 port and an 8 port POE switch.

    At work, I have a Pro Max, a 24 port enterprise switch, and a handful of access points. I also have one of their door controllers with its attached video doorbell.

    Their cameras aren’t bad, but they’re overpriced. I went full reolink and haven’t regretted any of that. I use their protect nvr stuff at work, and while it works, it’s not great. If you just want something easy to set up and go, it’s good enough. If you want to do some really complicated, complex things, you’re better off with frigate or blue iris.

    Their VPNs a little bit light duty. I don’t know if it’s still the case, but when I did my setups there was no local DNS option. But that’s easy enough to take care of.






  • Not accounting for any interesting custom choices you made under the hood, the default file browser for both os’s use libfuse3 for MTP. My point is, it shouldn’t have crashed, there are open issues in libfuse3 for possible crashes, so you might just have hit one at the wrong time, but at that, it REALLY shouldn’t have f’d over your journaling filesystem enough to keep you from logging in. A breaking read/write to fuse should not have been able to f your journal over beyond a simple automatic recovery. Most of the design choices in Linux over the last decade have been made specifically to prevent that kind of thing from happening on a healthy system. One can argue that one distro is more stable than another because they take, or refuse to take newer packages, but for your specific issue, they use the same piece of software under the hood.

    The wipe and new OS might have just moved the problems to a less visible area.

    My primary anger with Wayland is the security issues that broke AHK that they’re just now considering. There’s been lots of finger pointing over the years, but now that most OS’s are ditching X11 support all together, we’re going to see a lot more compatibility coming in the next year or two.