This article was written by an LLM. I get that the author might be self-conscious about his English writing skills, but I would still much rather read the original prompt that the author put into ChatGPT, instead of the slop that came out. The story - if true - is very interesting of course. Big bummer therefore that the author decided to sloppify it. David, could you share as a response to this comment the original…
I was shocked to read your comment. But then, not only was there a truth to it; you where absolutely right. * You had the headline spot on. Then you explained what you thought might be the reason for it. * Then you pondered about why the OP might have done it. * Finally you challenged the op to all but admitting his sins, by asking him to share the incriminating prompt he used. --- (my garbage wasn't written by AI, b…
I almost got hacked by a 'job interview'
461–470 of 534 posts
Re: I almost got hacked by a 'job interview'
#462Earlier quoted context omitted.
It would not block many other attacks.
Can you give some examples? I think of my containers as decently good security boundaries, so I'd like to know what I'm missing.
Re: I almost got hacked by a 'job interview'
#463Earlier quoted context omitted.
It would not block many other attacks.
Can you give some examples? I think of my containers as decently good security boundaries, so I'd like to know what I'm missing.
Re: I almost got hacked by a 'job interview'
#464Earlier quoted context omitted.
sucks to be young I guess.
Sure, but nobody expects a 23 year old to have a two decade old LinkedIn account or work history. (Except maybe the sorts of idiots who write job descriptions requiring 10+years of experience with some tech that's only 2 years old, and the recruiters who blindly publish those job openings. "Mandatory requirements: 10+ years experience using ChatGPT. 5+ years experience deploying MCP servers.")
so.. most of them?
Anyway the problem is not a hiring person expecting it, it's systems written with not enough thought that will expect it for them, and flag the people as untrustworthy who do not match expectations.
Re: I almost got hacked by a 'job interview'
#465Earlier quoted context omitted.
It’s not like there aren‘t dozens of companies with real funding that try to „tokenize real estate“. I mean if that’s a good idea idk, but that means there IS real money to be made working at such companies.
Eh, it would be nice if there was a public title database in the US. Ideally government administered, but if we can't have that then maybe a distributed ledger would do the trick. It's hilarious that title searches and title insurance exist. And even more ridiculous that there is just no way, period, to actually verify that a would-be landlord is actually authorized to lease you a place to live.
Re: I almost got hacked by a 'job interview'
#466This article was written by an LLM. I get that the author might be self-conscious about his English writing skills, but I would still much rather read the original prompt that the author put into ChatGPT, instead of the slop that came out. The story - if true - is very interesting of course. Big bummer therefore that the author decided to sloppify it. David, could you share as a response to this comment the original…
I've not been using much LLM output recently, and generally I ask it to STFU and just give me what I asked as concisely as possible. Apparently this means I've seriously gotten out of practice on spotting this stuff. This must be what it looks like to a lot of average people ... very scary.
Advice for bloggers:
Write too much, write whatever comes out of your fingers until you ran out of things to write. It shouldn't be too hard to just write whatever comes out, if you save your self-criticism for later.
If you're trying to explain something and you run out of things to write before you manage to succeed at your goal. Do a bit more research. Not being able to write too much about a topic is a good indication that you don't understand it well enough to explain it.
Once you have a mess which somehow gets to the point, cut it way down, think critically about any dead meat. Get rid of anything which isn't actually explaining the topic you want.
Then give it to an LLM, not to re-write, but to provide some editorial suggestions, fix the spelling mistakes, the clunky writing. Be very critical of any major suggestions! Be very critical of anything which no longer feels like it was written by _you_.
At this point, edit it again, scrutinise it. Maybe repeat a subset of the process a couple of times.
This is _enough_ you can post it.
If you want to write a book, get a real editor.
Do not get ChatGPT to write your post.
Re: I almost got hacked by a 'job interview'
#467This article was written by an LLM. I get that the author might be self-conscious about his English writing skills, but I would still much rather read the original prompt that the author put into ChatGPT, instead of the slop that came out. The story - if true - is very interesting of course. Big bummer therefore that the author decided to sloppify it. David, could you share as a response to this comment the original…
What's crazy is that I only realised this after my Fiancée pointed it out. Up to that point I thought it was just meandering way too much, I just skipped through most of it. I've not been using much LLM output recently, and generally I ask it to STFU and just give me what I asked as concisely as possible. Apparently this means I've seriously gotten out of practice on spotting this stuff. This must be what it looks li…
that's one of my key takeaways from all the comments here. a lot of people actually like the og - pre ai content I wrote more than the blog article it became. i just have to be confident in my own writing I guess.
btw, how do you have Arch in your name and have a Fiancee? sounds fishy :) /s
Re: I almost got hacked by a 'job interview'
#468cross check the package json with list.
Re: I almost got hacked by a 'job interview'
#469Earlier quoted context omitted.
Your comment looks like it was Ai generated. I can tell from some of the words and from seeing quite a few AI essays in my time. But seriously, anyone can just drive by and cast aspersions that something's AI. Who knows how throughly they read the piece before lobbing an accusation into a thread? Some people just do a simple regexp match for specific punctuation, eg /—/ (which gives them 100% confidence this comment…
Well, why don't you practice what you preach? There's no need to make drive-by allegations if there is information available to you. And there is: the author responded in this thread. https://news.ycombinator.com/item?id=45594554 There's no need to be contrarian. The accusation wasn't baseless.
Regardless, you're reading a lot of things into my comment that aren't actually there, but even if they are, I certainly didn't mean them that way. My comment wasn't about comments where someone sat down and thought about it and took the time to give reasons for their beliefs, it was about comments like https://news.ycombinator.com/item?id=45596745 that do nothing for the discussion, so that receiving one like that can be dismissed without a second thought.
Re: I almost got hacked by a 'job interview'
#470Earlier quoted context omitted.
I was shocked to read your comment. But then, not only was there a truth to it; you where absolutely right. * You had the headline spot on. Then you explained what you thought might be the reason for it. * Then you pondered about why the OP might have done it. * Finally you challenged the op to all but admitting his sins, by asking him to share the incriminating prompt he used. --- (my garbage wasn't written by AI, b…
„you where absolutely right“ could just be the perfect sentence to show you’re a human imitating an ai („where“ should be „were“, an ai wouldn’t misspell this).