Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)P
Posts
1
Comments
466
Joined
3 yr. ago

  • I love a real pregramming blog. I actually wrote my own HTTP frontend for my NTP server. It uses the "new Date()" and doesn't adjust for RTT.

    My approach was for all static content to be cached, which is everything except for the raw timestamp. I also ensured the whole website would fit in a single TCP frame if it had to. No repeat round trips.

    Here it is, anyway: https://ntp.ubermotive.com/

    I should probably try to get better timing adjustment into it. The primary goal was more an exercise in golfing than anything else. The site is seriously small.

  • AI is "taking credit for the work of humans" all the way down.

  • I'm old enough to understand this reference.

  • You clearly haven't seen Debian stable.

  • Installed it this week on an old PC. It really is unusable at this point.

    • It's not already in my distro's package manager
    • A github project with 1000 open issues and no commits for 3 years.
  • Fun fact: Australia's youth social media ban was lobbied by crooked betting agencies so that they could run ads without restriction.

  • Deleted

    Permanently Deleted

    Jump
  • I'm in my 40s, and have only ever dated within 1 month of my age.

  • Interesting. I'm getting full marks on mxtoolbox but failing the same tests on this one.

  • We almost had to mention standard cars, which are also half the size.

  • They didn't look all that advanced...

  • Way to stand up to the man!

  • I wonder if anyone ever wrote an update aggregator that would find all package managers, containers and git repos and whatnot and just do all of them.

    Some are a right pain to update, such as Nextcloud. Installing a monthly update should not feel like an enterprise prod deployment.

    It's kinda ironic that package managers have caused the exact problem that they are supposed to solve.

  • I've found the biggest bottleneck is bugs. If you catch a bug during development, it takes the least time to fix.

    Catch a bug during PR, you need to fix the code, and the PR needs to happen again.

    Catch a bug in QA, and you need to fix the code, do another PR, and get it tested again.

    This pattern goes right through UAT, and god help you when a bug makes it to Prod.

    There is nothing more time consuming than code that was written quickly.

  • Ahh. That's usually among the red stuff in dmesg. I glad to hear you solved it, but a failing hard drive is a pricey thing to endure these days.

  • This is no different to the meta pixel localhost listener exploit.

  • This is absurd. They know we can go all the way to the root servers, don't they?

  • Just start listening to dubstep and you'll stop noticing 😆.

    Maybe run lm-sensors and make sure the CPU/GPU isn't being thermothrottled? I'd usually look at dmesg and look for red stuff. Any hardware issues are usually pretty obvious.

    Try other apps. If you youtube or VLC behaves the same, the problem may be outside of jellyfin. If not, it narrows it down.

    If could even be the server not being able to transcode in realtime. Try watching a file known to already be in a suitable format. It should direct stream and be much less load on the server. I've seen server encode CPU saturation and it does kinda look the same as client decode stutter. If it's the server, you'll probably see the same stutter from another device such as a phone.