2upmedia

Eyal just released this. For those of you just easing into Claude Code from pure Cursor, this is an awesome combo. Use your current Cursor subscription + Claude Max subscription. Even a Claude Pro subscription will do.

Hacker finds a vulnerability and wins the bounty. People are not happy and feel he deserves a higher payment.

Tell me about it. facepalm

Awesome. Thanks.

Happen to know of any places where I could find high level data architecture concepts like that? Or did you know that just by experience?

Wow. Never heard of that one. Very useful thanks.

Planning stages, so no 3rd parties yet. Considering strategies because I need live connections with as low latency as possible so I'm probably going to be managing the websocket connections myself on the server side, unless there's something else that will give me the same benefits and nearly no latency.

Would you find any value in getting conceptual information in video form?

Great insight. Thanks.

This is actually a problem across multiple social networks. On Facebook and Instagram there's been a lot of scams recently with people selling stuff way below retail. They're complete scams. I reported it to Facebook through their mobile UI and they didn't really investigate it.

Hehe. Based on the previous pendantry, it blended in. I'll take it as help then. :D

More pedantry ;)

Unfortunately, HN doesn't have an edit function for comments. ;)

Good call. Minor oversight. Just updated that. I think if your NOT a hardcore technologist you probably think of megabytes as as 1000^n. It's really easy to forget too for the rest of us.

I mention: "never do these tests on a production server unless you’re sure you have plenty of RAM and you fully understand how web server processes consume memory. You could easily bring a server to its knees if there are many concurrent processes running, each using a high amount of memory." It's a temporary debugging procedure. The obvious goal to reduce memory usage.

Later on I say: "If by increasing the memory limit you have gotten rid of the error and your code now works, you’ll need to take measures to decrease that memory usage. Here are a few things you could do to decrease it:"

@trebor: yes, just like @laumars mentioned this article talks very little about memory leaks. Ever since PHP 5.3 the Garbage Collector was introduced which took care of the biggest contributor to memory leaks: circular references in objects. This article talks more about reducing high memory usage which can happen in any version of PHP.

Increasing the memory limit is only temporary. It's used as a debugging procedure. I later write "If by increasing the memory limit you have gotten rid of the error and your code now works, you’ll need to take measures to decrease that memory usage" with a list of things to do to decrease memory usage.