3 ms·

Also from the same author (actual titles): - Multi-Factor Authentication Sucks - Nobody Cares About OAuth or OpenID Connect - What Happens If Your JWT Is Sto

Also from the same author (actual titles): - Multi-Factor Authentication Sucks - Nobody Cares About OAuth or OpenID Connect - What Happens If Your JWT Is Stolen? - Why JWTs Suck as Session Tokens I would rather write an article titled: Why all those blog posts suck

ikiris 4y ago
This is a great summary of why this guy's blog is a waste of time honestly. Thanks for doing the work!
zmxz 4y ago
The titles are misleading (purposely, because it attracts interest), however - you should read what's written before judging. From what you've written, I'd safely bet your attention span is really low and that you haven't read a single one of those before writing the comment here.
- InGoodFaith 4y ago
  > The titles are misleading (purposely, because it attracts interest) I am neutral to this conversation but thought you might not want to justify this point as it is against the spirit of HN. Specifically in the guidelines: > Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize. Which would give the submitter permission to change the title to something more substantive.
  - zmxz 4y ago
    When you read the posts and when you don't rely on titles, you can see the point that the author argues. 2FA does suck, it's not a pleasant experience but it is necessary. If something sucks, it does not mean that you don't have to or should not have to use it. There are things that hinder user experience but are immense for security, like 2FA is. Making judgment based on title is silly, and if the spirit of HN is to judge without facts - then I apologize. Carry on as you were. The strawman argument against the author, based on the title that provokes thought, is not a sign of intellectual discussion.
    - InGoodFaith 4y ago
      I am in agreement with what you are saying. > and if the spirit of HN is to judge without facts - then I apologize. Although snarky, I am sure you would appreciate if HN doesn't devolve into sensationalist titles such as: "PHP sucks" ad nauseam since there are plenty of social media networks that get flooded with titles like that already. Just as we (the audience) in good faith read and judge based off of the merits of the article's content - one could also argue that an author should treat the audience with similar courtesy of not needing to: > misleading (purposely, because it attracts interest) Not saying this applies to this article since in my subjective view I didn't find the title misleading or egregious. You might also be interested in seeing the recent edit history of titles on HN https://hackernewstitles.netlify.app/ https://hackernewstitles.netlify.app/
      - 29athrowaway 4y ago
        PHP does suck though, and OAuth doesn't.
dontlaugh 4y ago
The titles may not be useful, but the posts are generally correct.

ikiris 4y ago

This is a great summary of why this guy's blog is a waste of time honestly. Thanks for doing the work!

zmxz 4y ago

The titles are misleading (purposely, because it attracts interest), however - you should read what's written before judging. From what you've written, I'd safely bet your attention span is really low and that you haven't read a single one of those before writing the comment here.

InGoodFaith 4y ago
> The titles are misleading (purposely, because it attracts interest) I am neutral to this conversation but thought you might not want to justify this point as it is against the spirit of HN. Specifically in the guidelines: > Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize. Which would give the submitter permission to change the title to something more substantive.
- zmxz 4y ago
  When you read the posts and when you don't rely on titles, you can see the point that the author argues. 2FA does suck, it's not a pleasant experience but it is necessary. If something sucks, it does not mean that you don't have to or should not have to use it. There are things that hinder user experience but are immense for security, like 2FA is. Making judgment based on title is silly, and if the spirit of HN is to judge without facts - then I apologize. Carry on as you were. The strawman argument against the author, based on the title that provokes thought, is not a sign of intellectual discussion.
  - InGoodFaith 4y ago
    I am in agreement with what you are saying. > and if the spirit of HN is to judge without facts - then I apologize. Although snarky, I am sure you would appreciate if HN doesn't devolve into sensationalist titles such as: "PHP sucks" ad nauseam since there are plenty of social media networks that get flooded with titles like that already. Just as we (the audience) in good faith read and judge based off of the merits of the article's content - one could also argue that an author should treat the audience with similar courtesy of not needing to: > misleading (purposely, because it attracts interest) Not saying this applies to this article since in my subjective view I didn't find the title misleading or egregious. You might also be interested in seeing the recent edit history of titles on HN https://hackernewstitles.netlify.app/ https://hackernewstitles.netlify.app/
    - 29athrowaway 4y ago
      PHP does suck though, and OAuth doesn't.

dontlaugh 4y ago

The titles may not be useful, but the posts are generally correct.