• 1 Post
  • 140 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle



  • #4 for me.

    Proper HTTP Status code for semantic identification. Duplicating that in the response body would be silly.

    User-friendly “message” value for the lazy, who just wanna toss that up to the user. Also, ideally, this would be what a dev looks at in logs for troubelshooting.

    Tightly-controlled unqiue identifier “code” for the error, allowing consumers to build their own contextual error handling or reporting on top of this system. Also, allows for more-detailed types of errors to be identified and given specific handling and recovery logic, beyond just the status code. Like, sure, there’s probably not gonna be multiple sub-types of 403 error, but there may be a bunch of different useful sub-types for a 400 on a form submission.






  • Absolutely. Like you say, it just doesn’t happen in large streams, and the threshold is probably a lot larger than you think, since on average maybe 10% of viewers actually participate in chat. The dynamic starts shifting at around 1,000 simultaneous viewers, in my experience, between chat being readable and interactable, and being just spam. That’s still plenty big enough to qualify for partner, and even make a living off of streaming alone.









  • Main difference there being that switching cities means probably switching ISPs. You can absolutely carry over your IP address when you move between the same provider, if that’s part of your service plan, and that may well happen with some ISPs even without it being part of your plan. There just isn’t really much of a need for people to carry a static IP, except for some businesses, and I’d say the main reason is that people don’t visit websites by memorizing and typing in an IP. They do memorize and type in phone numbers.