I think there's a big "control premium" attached to these things. Not necessarily even that they will manipulate and censor rampantly, but that they could, I think the market prices highly.
Twitch gets a big cut of individual creators’ subs, and I’d bet most people that stream also sub to other channels. Keeping people in the ecosystem is probably worth it, even if there’s some amount of “freeloading”.
youre still encoding to like, 4 different formats and pushing bytes to a cdn for 80k+ streams in real time. I think the actual serving of hls chunks is the cheap part
Transcoding is only guaranteed for twitch partners, and the cdn doesn't actually distribute the video to a given datacenter until at least one viewer using that datacenter requests it.
Twitch can forward the stream as is without transcoding it. That's what transcoding not being guaranteed means. It will be a worse experience for viewers but it can work. Few years ago they even announced working with OBS on feature where streamers themselves can transcode and send multiple streams further reducing need for twitch to spend their compute resources on unprofitable streamers.
what? no, i love projects like these. but re-reading my comment, it does sound a little messed =p. what i meant was it gave me old HN vibes, back when weird, fun projects popped off instead of everything being AI-wrapped.
whats the other end of some of these? you showed which categories tend to have 0-1 viewers, what categories have the least? what categories have lowest average age of accounts with 10+ viewers etc. What should you do to stand out?
For anyone who is curious btw: twitch will count you as your own viewer. So anyone with their own chat open in a browser (almost everyone so they can read it) will have that 1 viewer. Which is why the bottom of the distribution is so weird looking.
what does compilation have to do with iteration speed? There's a lot of ways to get a similar feedback loop that youd get in something like react, like separating out your core gameplay loop into its own compilation unit / dll and reloading it on any changes inside your application
NPM is absurdly complex in comparison, it's just neatly abstracted. Maybe somebody will write a cross-platform reactive layer which can compile both natively and to the web?
If people wanted to do this theyd be self hosting xmpp servers already. No one wants to write and maintain the code and infra for things like this, you are grossly underestimating the effort involved here.
No no it makes sense. Hypothetical scenario: I, a high-level employee at a company just convinced my boss (or did we convince each other?) to spend $30k/year on Claude/Codex enterprise licenses. So far, the productivity gains have not been there and we're starting to sweat. So, I propose to my boss to build an internal version of $SaaS and call it a win. Galaxy brain.
Now some IC somewhere in the company who is at the end of his rope and sees the company as a dead end, sees an opportunity. Why not advocate for this project, get real experience building something greenfield in a brand new domain, strengthen their own resume, and finally have a way out of their strut? It's not like they're gonna stick around maintaining what they built.
Most people using Slack, Teams etc. and especially those making purchase decisions have no idea what XMPP is and what it's capable of. Heck, even Facebook used to federate XMPP until they decided to go proprietary. Not in the interest of their users, but because it makes the most money for its shareholders.
Whats the key difference between this and Rive? Especially now that Rive has full scripting support? Just curious more than anything, this does seem neat, especially the fla / xfl support (although for new things this doesnt seem like a huge killer feature)
What are you needing to use `uv pip` for? I don't think I ever call into pip from uv for anything nowadays. I typically just need to do `uv sync` and `uv run`, maybe sometimes `uvx` if I want to run some random 3rd party python script
reply