Live data from Hacker News

How I Made Porn Video Streaming More Efficient with Python and C

toptal.com

11–20 of 118 posts

Re: How I Made Porn Video Streaming More Efficient with Python and C

#13
post #4

Hey this is awesome! Though the admin/moderator changed the title for some unknown reason from the title of the blogpost to their own.

For what it's worth, the new title is more accurate and more likely to get me to click.

Re: How I Made Porn Video Streaming More Efficient with Python and C

#14
post #6
post #4

Hey this is awesome! Though the admin/moderator changed the title for some unknown reason from the title of the blogpost to their own.

Of course because of snobbery. NH visitors should be protected from words, which starts from "p" and ends with "orn".

"NH visitors should be protected from words, which starts from "p" and ends with "orn"."

popcorn? preworn?

Re: How I Made Porn Video Streaming More Efficient with Python and C

#16
post #14
post #6

Earlier quoted context omitted.

Of course because of snobbery. NH visitors should be protected from words, which starts from "p" and ends with "orn".

"NH visitors should be protected from words, which starts from "p" and ends with "orn"." popcorn? preworn?

  % egrep '^p.*orn$' /usr/dict/words

Re: How I Made Porn Video Streaming More Efficient with Python and C

#17
post #12
post #4

Hey this is awesome! Though the admin/moderator changed the title for some unknown reason from the title of the blogpost to their own.

It was kinda link-baity and vague...

jdc... it's the name of the actual article...

Re: How I Made Porn Video Streaming More Efficient with Python and C

#19
Agreed that RTMP is an abomination that needs to be exorcised from the Earth as soon as possible. Unfortunately, it is probably here to stay until something like WebRTC gains critical mass.

It's not clear what the article means by "repackaging" a stream or "pointers" to tags (especially in the diagram that shows tag pointers being transported between users). While RTMP is cumbersome, shoving media data (tags) under a per-session protocol header is essentially the standard way of moving data from one session to another.

So I'm not really following this. Is this cutting out the RTMP entirely for receiving clients, and instead sending the FLV down via another transport, like HTTP or whatever? Or is it more of, "I wrote my own RTMP streaming server in C and Python", along with some implementation details which I'm not understanding? (Not that there's anything wrong with doing so. Options are limited in the streaming-server space.)

Post reply on HN