Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Here is a summary of potential mitigations for those too busy to click:

# Limiting users or use cases

- User Vetting: Carefully vet those who can use a tool (Example: Synthesia only working with vetted enterprise clients.)

- Usage Constraints: Limit the synthesis possibilities. (Example: Humen is providing only a limited set of movements for generated videos.)

# Discouraging malicious use of flexible and public tools

- Clear disclosure: Ensuring and requiring that manipulated outputs are clearly labeled (including via metadata).

- Consent protection: Requiring the consent of those being impersonated.

- Detection friendliness: Supporting those working on detection and not seeking to fool detection systems.

- Hidden watermarks: Embedding data through robust watermarks.

- Usage logs: Storing information about usage and media outputs.

- Use restrictions: Enforcing contracts that prohibit forms of violative or malicious use.

Not all apply to every system of course. The article has more detail!



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: