Hacker Newsnew | past | comments | ask | show | jobs | submit | EthOptimist's commentslogin

Is it possible Spotify was debating what to do, decided to not take down Joe Rogan's episodes, but then some rogue employee did it anyway?


I don’t get why people are so triggered by this guy. Seems like very fragile people.


When people believe that "words are violence", demanding broad censorship is the logical progression.


Words can indeed be violent under the correct context. That is a legal fact. https://www.legalmatch.com/law-library/article/verbal-threat...


> Words can indeed be violent under the correct context. That is a legal fact. https://www.legalmatch.com/law-library/article/verbal-threat

"Page does not exist"

You are linking to a 404 page.

You pretty much didn't establish a legal fact, nor made a point that is even relevant to my statement.


He mentions this because LOC is an objective metric that Amazon uses to analyze performance..


I remember seeing his presentation at the Python meetup at Yelp HQ in San Francisco a few years ago. Happy to see it come to reality


If you compare Facebook's uptime vs Reddit it is no contest. Granted, it isn't as widely used compared to Facebook Login, WhatsApp etc. but still it's impressive


Reddit isn't remotely comparable to Whatsapp.


Laws requiring content moderation in social media will only serve to be a form of regulatory capture that inhibits competition


So the main thing risk would be if they are consistently logging things such as client IP, user agent etc.


Is it better that they never do such research and just keep their heads in the sand?


One reason why this works so well is that there is often a monetary incentive on the referrer's side, in that they get paid some referral bonus if you get hired


It also seems more feasible with concurrency focused languages such as Go which have become more popular in recent years


I do not see anything less feasible doing it with threads / forks.

Asynchronous IO like in Go I think is useful in a sense that if some of the networked responders are temporarily slow then they will not hold fast ones and would not accumulate threads. If however it is disk / database, then by immediately switching to a next method this strategy will let internal async tasks piling up indefinitely and saturating resource pools of OS just as well. So those "concurrency focused" languages are not a silver bullet and one has to understand internal mechanics to properly manage requests lifecycle.


Concurrency limits is the main way to prevent such a thing right?


I think it's the easiest and most reliable way to prevent runaway bills.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: