• 0 Posts
  • 108 Comments
Joined 2 years ago
cake
Cake day: June 30th, 2023

help-circle





  • Yup.
    It’s a traumatic job/task that gets farmed to the cheapest supplier which is extremely unlikely to have suitable safe guards and care for their employees.

    If I were implementing this, I would use a safer/stricter model with a human backed appeal system.
    I would then use some metrics to generate an account reputation (verified ID, interaction with friends network, previous posts/moderation/appeals), and use that to either: auto-approve AI actions with no appeals (low rep); auto-approve AI actions with human appeal (moderate rep); AI actions must be approved by humans (high rep).

    This way, high reputation accounts can still discuss & raise awareness of potentially moderatable topics as quickly as they happen (think breaking news kinda thing). Moderate reputation accounts can argue their case (in case of false positives). Low reputation accounts don’t traumatize the moderators.



  • I swear there was a phase where shakey-cam had just become the in-thing.
    I remember watching a TV series or a movie or something where shooting had clearly wrapped before shakey-cam was popularised. And it looked like they had just added it in post. It was unnatural movement (so, not like someone was holding the camera), and there was too much of it. I had to skip a lot of the shakey-cam scenes




  • Trying to disable the windows key hotkey that opens the start menu, so the game The Witness can pause stuff, minimize, open the start menu and release the block on the windows key (IE do a more controlled start menu hotkey, instead of having windows rudely interrupt everything and break the game).

    Started with a 5 second hang whenever a debug breakpoint was reached. The dev started digging into the issue.

    Games use RawInput to get better mouse interactions, but that breaks the Microsoft recommended way of disabling windows key (as all input goes through RawInput instead of whatever the other windows API is).
    In the documentation for RawInput, it specifically states the flag to disable the windows key doesn’t work. So the Dev that was debugging the issue didn’t try it. Until the next day when they had the realisation that MSDN windows API docs are garbage, tried the supposedly not-working flag and it actually did work.

    The linked article is quite a good read, actually.
    I had to use one of the mirrors in the SO answer

    Edit:
    The mirror I used https://caseymuratori.com/blog_0006









  • Low latency means low compression. Low compression means high bandwidth.
    1080p60 NDI will be 200mbps. If you are doing 2160p60, that’s 800mbps (which is about the limit I would run 1gbe at). Doesn’t leave much overhead for anything else, and a burst of other traffic might cause packet drops or packet rejection due to exceeding the TTL.

    2.5gbps would be enough.
    But I see 2.5gbps and 5gbps as “stop-gaps”. Data centers standardised on 10/40gbps for a while (before 25/100 and 100/400) - it’s still really common tbh - so the 10gbps tech is cheap.
    I don’t see the point in investing in 2.5/5gbps