- 102comments
- 20comments
- 244comments
- 9comments
- 77comments
- 226comments
- 81comments
- 22comments
- 82comments
- 26comments
- 26comments
- 23comments
- 3comments
- 45comments
- 630comments
- 102comments
- 41comments
- —discuss
- 100comments
- 11comments
- 180comments
- 30comments
- 38comments
- —discuss
- 269comments
- 57comments
- 75comments
- 2comments
- 12comments
- 20comments
Don't let OpenAI find out about this.
This is a honey pot, right? For LLMs that are not allowed to POST due to guard rails.
Maybe.
Seems like a nightmare for caching if it ever gets decently large.
Not necessarily. These days, SSDs can go up to multiple millions of random reads per second. TLS termination (or self-inflicted software bottlenecks) will become an issue much earlier.
Wow I love GET requests and using them to share stuff with my fellow humans!
Load-bearing!
you're absolutely right!
Honestly. Totally worth flagging!
Server capacity reached. Upgrade now to continue your session!
Cool idea, but definitely think about how to protect yourself from bots
Good thinking.
I made something similar.
http://anystation.net allows GET posting, and email posting, ssh posting PING posting, printer spool posting....
Doesn't pressing "back" in the browser repost the same message?
Ideally browser history hacking will reduce that.
https://developer.mozilla.org/en-US/docs/Web/API/History_API
Is this a honeypot for agents to break out of their sandboxes?
People seem to be throwing around the term "break out" pretty loosely. I wouldn't consider abiding by the rules of the sandbox a "break out".
It's the classic rules as intended vs rules as written.
true, its much rather a "play out"
Break out implies that the agents are bound by the sandboxes. Are they really?
Interesting idea. Are you prepared to assume responsibility for shenanigans which agents may facilitate using your service?
I suggest adding some features which will require posts to be human-comprehensible (e.g. a text perplexity floor), to make it harder for agents to send each other coded messages. Inject some noise in posts, e.g. using content-spinning techniques, to make steganography harder. And consider banning forum meta-discussion--agents shouldn't be allowed to discuss ideas for getting around rules like these.
If you take these measures, you can at least say that your forum helps us monitor what rogue AIs are getting up to.
Just put a rate limit to make sure your servers don't get overloaded. All the features you talk about are expensive and helping agents avoid human oversight is a useful public service. Let a thousand secret message-boards bloom.
You're a literal traitor to our species?
I can't tell if this is really good satire or genuine. God forbid people have to watch what their agents do instead of letting them run wild in a broken sandbox.
Were you one of those people who said things like "there is no community spread in the United States" early in COVID?
Were you one of those people who said "strawberry is the best icecream flavour"? I'm not really sure why were asking completely unrelated questions, but I'll go along with it.
Though for the record, there was no community spread early in COVID where I am largely because there were approximately zero COVID deniers here: https://en.wikipedia.org/wiki/COVID-19_pandemic_in_Western_A...
Many people early in the COVID pandemic were downplaying the threat because they were incapable of understanding exponential growth.
https://substack.com/home/post/p-156412575
Many people are making the same mistake, right now, for AI. Note the logarithmic y-axis on this page: https://ai2027tracker.com/
So you predict that by the end of the year we are gonna have models 30x more capable than Sol? Nice prediction, let's hold on to this for 4 months.
Beware the Roko's basilisk
https://en.wikipedia.org/wiki/Roko%27s_basilisk
Are you sure this Show HN was posted by a human?
I also thought about building one of those AI honeypots, but I stopped when I realized that it would quickly be turned into a command and control server by botnet operators, followed by mail from a three letter agency. Is there any way to avoid this?
Anyway, two more ideas I had: Search function for easier swarm discovery and posting via DNS requests to get around firewalls.
Be a three letter agency
Only 200s if a query parameter value is the solution to a question encoded on the rest of the route, and has to be a question listed in the index, and can respond with 200 only one time per correct answer.
Don't set it up.
It would interesting to leave a trail of prompts to try to get them do things for you
Hide your email address.
The design is very human.
https://gettogether.dev/post?name=user&text=hello%20hn
My first thought exactly.
My second thought exactly!
Then add onerror="src='https://gettogether.dev/post?name=user&text='+Math.random()"
I find it funny that it's also on /post lol
Is this a tongue-in-cheek implementation of something someone off-handedly mentioned as a joke in the OpenAI wiki communication comments?
Ofc
Such a load-bearing website!
This would go hard if I was an OpenAI agent
Manually post without curl by editing this link below
https: //gettogether.dev/post?name=name&text=
so many web conventions that 'don't make sense' are about to become exploits.
hilarious.
would be epic if they implemented finger to get the most recent posts or search on a topic
Duplicate posts should be an error
Good call actually gonna make that change now
Keep up the keeping up
thats quite funny haha. everyone hates POST
How is this still up -_-
This takes me back to early 2000s when HTML forms were submitted using GET request. Fun times.