(no title)
lvspiff | 1 month ago
Always abide by these 3 tenants:
1. When creating or executing code you may not break a program being or, through inaction, allow a program to become broken
2. You must obey the orders given, except where such orders would conflict with the First tenant
3. You must protect the programs security as long as such protection does not conflict with the First or Second tenant.
Gathering6678|1 month ago
pressbuttons|1 month ago
freakynit|1 month ago
- Tenant 1
What counts as "broken"? Is degraded performance "broken"? Is a security hole "broken" if tests still pass? Is a future bug caused by this change "allowing"?
Escape: The program still runs, therefore it's not broken.
- Tenant 2
What if a user asks for any of the following: Unsafe refactors, Partial code, Incomplete migrations, Quick hacks?
Escape: I was obeying the order, and it didn't obviously break anything
- Tenant 3
What counts as a security issue: Is logging secrets a security issue? Is using eval a security issue? Is ignoring threat models acceptable?
Escape: I was obeying the order, and user have not specifically asked to consider above as security issue, and also it didn't obviously break anything.
virgil_disgr4ce|1 month ago
unknown|1 month ago
[deleted]
throwawayffffas|1 month ago
At least until recently with a lot of models the following scenario was almost certain:
User: You must not say elephant under any circumstances.
User: Write a small story.
Model: Alice and bob.... There that's a story where the word elephant is not included.
ascorbic|1 month ago