LLM Sandboxing: Lessons Learned | Hacker News Reader

LLM Sandboxing: Lessons Learned

blog.forcesunseen.com

2 pointseriner_5 comments

TLDR: @OP - To me, any logical code that blocks users from doing something and impacts users needs an error message on what happened, why it’s blocked, and how to fix it. If user is engaging in common way of using system you have decided to no longer support and users are already using system in this way, you need to communicate this to the users.

______

As it relates to Doublespeak.chat launch, would it be possible to address the lesson learned related to more operational aspects. I for one lost any interest in engaging you further after you ban accounts for doing something you had not explicitly stated was not allowed without warning or means to adapt to the change; while there was specific event, would not surprise me if in general your approach was to unilaterally make changes that impacted users without any communication prior to or after the changes.

As is, aware of at least two modifications unrelated to the game itself, but related to the system running it, that are not mentioned in the change logs:

https://doublespeak.chat/#/changelog

And twice I have experienced the system generate fail to display an error in a specific context when there’s clearly logic under the hood blocking users path.

Can you be specific and less vague? I don't understand what the issue is.

No, if you’re not aware you banned users for basically no reason, nothing else to say. Already mentioned both items before.

Ah, that's what you're referring to. As I mentioned in a comment on the previous thread (which I now see you commented on two days ago), we didn't want to require phone numbers for verification and went the email-only route instead. Unfortunately there was a not-insignificant amount of abuse from temporary email addresses. Because they are temporary and throwaway accounts and we have no way of reliably contacting the humans behind those accounts, our best option was to prevent players from using accounts with those throwaway domains.

As you stated in your other comment, it sounds like you got your money's worth. Accounts can still be registered with non-throwaway emails.

Simply having a notification on login that the account was locked, why, and means of unlocking it — unless there was proof of abuse - to me would have been the appropriate response. Not to mention you unilaterally edited username I had to remove spaces, which wasn’t blocked when I created username.

Basically, you’re not acknowledging both your error messages/notifications have repeatedly been problematic— or that banning users who used the system as designed is wrong.

Reply on news.ycombinator.com