• 0 Posts
  • 80 Comments
Joined 1 year ago
cake
Cake day: September 10th, 2023

help-circle
  • I mean, the minimum you need is some authentication mechanism, a secure certificate, an authenticated endpoint to send a live data feed to, an endpoint to query a given live data feed from, maybe a website to serve the whole thing for people that don’t have their own tool for reading and playing back a live data feed…

    …and the infrastructure to distribute that data feed from ingest to content delivery. Easy.

    (Note: easy does not mean cheap. Even if a live data feed ingest and delivery was easy to implement (which I doubt it is), you’d skip buffering (to reduce memory demands) and only used a single server (to spare such stupid things as distributed networks, load balancing, redundancy or costs for scaling cloud solutions), you’d still have computational overhead of network operations and of course a massive data throughput.)






  • A lot of data throughput and buffer just for ingesting and distributing the live streams themselves, technical and business administration to keep things running, moderation to ensure compliance with content laws and data protection regulation, and then there’s still all the other fancy features major platforms offer if you want to compete for users.

    Multiple resolution options with server-side rescaling for users with slower connections? Graphics computing power.
    Store past broadcasts? Massive amounts of data storage capacity.
    Social features? Even more moderation.

    And we haven’t even touched on the monetary issue of “How do you pay for all that?” and all its attached complexity. You could be running the nicest platform in the world, but without any funding, it won’t run very long.







  • That is Popper’s own proposed solution for that paradox: Tolerance is not to be extended to the intolerant.

    He suggests trying to work within the bounds of the contract first (talking, reasoning, voting etc.), but if that fails or is impossible endorses the censorship and suppression (violent, if necessary) of the intolerant. Try the high road, but be willing to acknowledge when that road is a dead end and ready to correct course in time.


  • …along with calendar weeks being entire weeks, not bullshit like 5 days of CW 53 and 2 of CW 1. This matters when dealing with BI facts that continue through NYE.

    Do you know how infuriating it is to view analytics by calendar week with two major dips around new year’s because the week is split in two?

    Bonus points: “Sure, you can set the week aggregation to consider weeks starting with Monday, but if you filter for the last X calendar weeks, you’ll have the last week’s sunday omitted from the stats and an orphaned Sunday before the first week yoh actually wanted.”

    Support international standards, you bloody imbeciles.





  • I once held a temp position in QA. I found a nasty, but obscure error that wouldn’t have popped up until way down the line (and also wrote and submitted a fix). The original developer was annoyed, but the team lead was pretty happy to see me do exactly what I was brought on for: Abusing the app in all the ways I could imagine a user not on the actual dev team doing.

    So yeah, great job tester, great job developer, now we wait for the user to try actually sleeping in it and finding it terribly uncomfortable in the long run, or exerting lateral force instead of the vertical one it was designed for.