Please write your own blog posts rather than asking us to read LLM slop.
I thought it was a perfectly cromulent article making a perfectly reasonable point.
31–40 of 64 posts
Please write your own blog posts rather than asking us to read LLM slop.
I thought it was a perfectly cromulent article making a perfectly reasonable point.
Earlier quoted context omitted.
GP is right. This paragraph is a major tell. If you have read enough ChatGPT output that hasn’t been humanized, you start to instantly notice it: “ The attacker hadn’t broken into anything. They’d just noticed something I hadn’t: I had a verified email-sending domain attached to open, unverified signup, and that’s a useful primitive if you don’t care what you send.”
Yes, instead he should have written: "The attacka didn broke into nuffin bruv. They jus noticing sometin I aint, yeh?" Instant betterness.
[flagged]
Why do you think this is LLM-generated? Reads perfectly fine to me.
[flagged]
[flagged]
Please write your own blog posts rather than asking us to read LLM slop.
Just curious, on what grounds do you call this slop? I thought it was a perfectly cromulent article making a perfectly reasonable point.
I have a few small projects that I would love to serve publicly from my VPS. But I have put them behind strict logins (no signup) or put them in read-only mode, with (likely premature) rate limiting, fail2ban and cloudflare, for fear that a month of bandwidth gets used within minutes by an attacker. For the same reason, sometimes I only shared the source on github and let people deploy it themselves if they are interested.
I've dealt with these and similar issues over the last 8 years, which led our team to develop a security tool 5 years ago that is now open-sourced.
I designed something that was "too open," and that "openness" was abused.
Sadly, spammers are why we can't have nice things; but that's been the case for decades. The incident I mentioned, happened in the 1990s.
The good news is, is that once this happens to you, you learn your lesson.