No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
assets
.gitignore
README.md
SUMMARY.md
acknowledgements.md
addressing-abuse-vectors.md
bad-actors-vs-bad-behaviors.md
chapter1.md
exercise-3-empowering-humans-to-prevent-abuse.md
exercise-3-empowering-others-to-prevent-harassment.md
further-reading.md
holographic-doctor-use-cases.md
how-can-i-identify-an-abuse-vector.md
pip-boy-use-cases.md
pokedex-use-cases.md
rpgreet-use-cases.md
second-exercise-addressing-abuse-vectors.md

README.md

Welcome to Identifying Abuse Vectors!

This is a workshop for software developers who are interested in making sure that the software they work on can't be used to harass or otherwise harm its users. We're going to look at some examples of fictional software and see how they could be used for abuse and harassment. Then, we'll make proposals for how to address these abuse vectors without compromising the functionality of the application. After that, you'll be able to approach real life projects with an eye for how to keep users safe.

Credits

This tutorial was written by Terian Koscik for RailsConf 2018. You can view the source at https://github.com/spinecone/Identifying-Abuse-Vectors.