malokiApr 27, 2017

Yesterday Gargron helped me get his take on the project, so that I can write a mission statement. But, I would also love to hear your take, so I can combine the two into our collective statement.

This is me trying to be more transparent with the process.

Feel free to help me answer these questions:
1. What does Mastodon mean to you?
2. Where do you want to see the project go?
3. How do you talk about Mastodon with your friends?

#MastoTalk #MastoDev

Show threadShawna ScottApr 27, 2017
@maloki
2. I want to see the project prioritize safety and privacy by adding more fine tuned controls for users and admins, as well as prioritize accessibility (both technically and through outreach to underrepresented marginalized communities, esp. communities of color).
Show threadmalokiApr 27, 2017
@Styger regarding the latter, @creatrixtiara had some good comments regarding that. When we reach out we have to think about what value it adds for them to be here.
Show threadShawna ScottApr 27, 2017
@maloki @creatrixtiara agreed! Not suggesting dragging people here to meet some arbitrary standard. I think there is value in advertising the community creation and boundary setting that can be possible with Mastodon, especially if fleshing out those features is prioritized.
Show threadCreatrix TiaraApr 27, 2017
@Styger @maloki yes! If safety and access were being actively worked on, it'd make this place more compelling for marginalized folk.
Show threadmalokiApr 27, 2017
@Styger @creatrixtiara what do you feel is missing right now? except for account side server blocking, which is coming
Show threadjonApr 27, 2017
@maloki @Styger @creatrixtiara on th process side, regular discussions with people here (and people who *aren't* here) and making sure that the resulting feature requests get prioritized. organizationally, have people explicitly focused on user safety and access - and over time make these into funded positions at the same pace as others
Show threadjonApr 27, 2017
@creatrixtiara @Styger @maloki actually I should have said "making sure that the resulting feature requests get prioritized *and reviewed*". the change in federated PMs in this release is something that should have been looked at through a safety lens - to understand what the risks are, see if there was a better way of accomplishing this, potentially decide not to implement it, better inform people, etc.,
Show threadCreatrix TiaraApr 27, 2017
@jdp23 @Styger @maloki I honestly still don't understand the federated PMs thing
Show threadjon

@creatrixtiara @Styger @maloki right. and there isn't a good description - when @polymerwitch posted the announcement on toot.cat, the link was to the PR on github - which isn't exactly the most friendly documntation. @boots suggested elsewhere that it would be good to put change notices in the modals up front....

the organizational point is, have empowered people focusing on stuff like this this

Apr 28, 2017 at 1:03amWeb
Show threadmalokiApr 28, 2017
@creatrixtiara @Styger @[email protected] @boots @jdp23 hey guys, sorry for the mass tag.
We clearly had a bad release communication last night, even though the features are highly requested. We, both me and Eugen, need to get used to our new hats and in relation to each other. Hopefully we can get into this soon.
I'm really sorry about how this got communicated, and am already looking at how to improve this.
Show threadjonApr 28, 2017
@maloki an exciting first day on the job for you! i wasn't trying to give you a hard time or anything (hope it didn't come out that way), just to highlight the value of a team focusing on this ... and also to underscore @Styger's point about prioritizing safety and privacy