• 0 Posts
  • 405 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.









  • 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


  • It could just do with a UI refresh and maybe some added functionality

    That is actually huge ask.
    Mumble works in an “engineer brain” kinda way. Cause it has been made by engineers making sure the underlying tech is available to be used in so many scenarios.
    Making it work in a “user” kinda way is a huge change.
    And it would either make the code really difficult to maintain, or would isolate the power users by restricting the flexibility of mumble.
    The fact that mumble is FOSS is absolutely fantastic!

    Feel free to fork the project and refresh the UI.
    Or sponsored programmers to do this. If there is actually a market, you would be able to overtake mumble. You can even start from their codebase, the license is very permissive (just make sure you credit mumble!)