Yes it’s the first thing I read, and it’s awesome work! I advise all thread readers to really go through it. It’s helping me a lot . I’m not knowledgeable enough to offer critique, though. Some strikethrus disappoint me, because I really want to use those fields (which is not a valid gripe!).
[Note: emphasis below is for readability, not because I’m shouting]
Mostly what I want is general guidance (from anyone, not necessarily you). Principles that one employs to arrive at the conclusions you made. You seem to have your head screwed on straight in this matter, and I don’t, so I’d like to develop a decision making strategy like yours when I handle the data I collect.
The reason I want a narrated, more general guide is because:
- General principles can guide us even when information changes
- I collect info beyond the api (about/more, reachability, admin handles, etc.)
- I need to break some rules (like instance anonymization for my instance picker), and want to know what I’m getting into.
- Mastodon has a unique ethic regarding privacy, which I wish to honor (but don’t know what it could be!!)
For example, I didn’t consider low user count to be a factor in identifying people, until you brought it up. I’d like to know stuff like that before being told.
Not that I’m asking you personally to write an essay. It’s just a general note to the Mastodon community — some of us do want to be careful with toot/instance data, but we feel lost how to do it…