Tell HN: Bash.org Is No More

Re:Tell HN: Bash.org Is No More by nirui on Thursday January 11, 2024 @10:44AM (#38953752)

This has to be a joke.

The only way it can be realistically implemented involves the storage of clear-text user password to enable string replacement during comment submission. Either that or converting user comment to a prefix/suffix table (or something similar) and then hash each item to search for a match. Both option is ridiculously unnecessary.

Anyway, my HN password is ****. I bet it don't work.

[ Parent | on HN ]

Re:Tell HN: Bash.org Is No More by thomaslord on Thursday January 11, 2024 @11:23AM (#38954342)

Fortunately with modern serverless architecture, it's possible to make this performant! Just split up each comment into words and dispatch each word to a queue where AWS Lambda workers can check the words against the user's password hash. It might cost $20 to process each comment, but at least it'll autoscale to handle any comment volume you throw at it!

[ Parent | on HN ]

Re:Tell HN: Bash.org Is No More by Affric on Thursday January 11, 2024 @04:21PM (#38959261)

Can passwords include spaces?

[ Parent | on HN ]