It uses a session cookie to remember that you are logged in. Commenting requires being logged in, so it definitely tried to set one on your machine.
Maybe you've got an extension or something that prevents the cookie from actually getting stored?
Maybe you've got an extension or something that prevents the cookie from actually getting stored?
At this point I'm not sure what was actually meant. The website of the article doesn't set any cookies on my machine, and HN's session cookie likely doesn't need ePrivacy directive consent since it's actually functional.