|
| 1 | +# Clojurians Slack Log demo data |
| 2 | + |
| 3 | +This is a small subset of the raw logging data that is gathered from the |
| 4 | +Clojurians Slack community. It is here to help people who want to help improve |
| 5 | +the app that displays these logs, found at |
| 6 | +[clojureverse/clojurians-log-app](https://github.com/clojureverse/clojurians-log-app). |
| 7 | +You can find instructions on what to do with this data over there. |
| 8 | + |
| 9 | +What you find here is the data from the first 9 days of February 2018, as well |
| 10 | +as the data of users and channels that were active during this period. |
| 11 | + |
| 12 | +This is "real" data, with two differences |
| 13 | + |
| 14 | +- user email addresses have been replaced with fakes |
| 15 | +- message text that has been deleted or changed has been scrubbed |
| 16 | + |
| 17 | +## Why don't you just make the raw logs public? |
| 18 | + |
| 19 | +We've considered this. People should assume that what they post on Slack is |
| 20 | +public, so this should be fine, but there are a few reasons why we chose not to |
| 21 | +do this. |
| 22 | + |
| 23 | +A person with bad intentions could use this data to specifically filter and |
| 24 | +search through the chat history of a single person, looking either for |
| 25 | +identifying or incriminating information. This is the main threat model we |
| 26 | +consider. The website with the logs is still public, so a persistent individual |
| 27 | +could still do this, but we're not making it trivial. |
| 28 | + |
| 29 | +Slack allows people to edit or delete messages. In these cases we only display |
| 30 | +(or don't display) the end result. The original message and the change events |
| 31 | +are all present in the raw log data though, and so we choose not to share those. |
| 32 | +That is also why the data in this repo has been processed, to remove such events. |
| 33 | + |
| 34 | +Finally, if a user asks to remove their message history from the archive then we |
| 35 | +must honor that. This would be near impossible if the complete history is a git |
| 36 | +repo that anyone can clone. |
0 commit comments