Post 9i6n9d7B5IW7JdV1Cy by bhtooefr@mastodon.social
 (DIR) More posts by bhtooefr@mastodon.social
 (DIR) Post #9i6k1tBn8Wt4zTH5iS by staticsafe@mastodon.zombocloud.com
       2019-04-23T17:34:49Z
       
       0 likes, 0 repeats
       
       My initial thoughts on the rich text formatting in Mastodon issuehttps://github.com/tootsuite/mastodon/pull/10629#issuecomment-485899092
       
 (DIR) Post #9i6k1tUvzMCRwqENYO by staticsafe@mastodon.zombocloud.com
       2019-04-23T17:44:15Z
       
       0 likes, 0 repeats
       
       In a more general sense, adding rich text formatting visibility in Mastodon blurs the lines between microblogging and more "traditional" blogging with things like WordPress or WriteFreely where you can format as much as you please.I am not entirely sure that line needs to exist and it is basically entirely arbitrary anyways.
       
 (DIR) Post #9i6k1to4qBVouDBfOK by staticsafe@mastodon.zombocloud.com
       2019-04-23T18:44:36Z
       
       0 likes, 1 repeats
       
       "I really don't think we should do this."https://github.com/tootsuite/mastodon/pull/10629#issuecomment-485831461Eugen, I am going to put this as politely as possible:This is a terrible response. - Extremely disrespectful of Thib's work in this pull request.- Assuming people know why you think this PR is a bad idea. We are not mind readers. Bad communication.This response is worse than posting nothing at all. Antagonism was created where none was necessary.
       
 (DIR) Post #9i6kvZBShdk3A5fZSa by Gargron@mastodon.social
       2019-04-23T18:51:19Z
       
       1 likes, 0 repeats
       
       @staticsafe You know I follow you so you might as well tag me, no?Thib and I work together for a long time and often communicate in private. My response was addressed to him, the only participant of the pull request at the time, and I do not think it was particularly disrespectful. It's not a new discussion and my position on it has been communicated before, it was simply a re-iteration.Now that people have brigaded the post and completely misrepresented what the PR actually does, (1/2)
       
 (DIR) Post #9i6kvZeswFHGdLR4K0 by Gargron@mastodon.social
       2019-04-23T18:51:29Z
       
       0 likes, 0 repeats
       
       @staticsafe I went back and wrote a detailed response (2/2)
       
 (DIR) Post #9i6kva4lO1yfvbXjeq by staticsafe@mastodon.zombocloud.com
       2019-04-23T18:53:40Z
       
       0 likes, 0 repeats
       
       @Gargron yes I saw that detailed response just now, that should honestly have been your first response
       
 (DIR) Post #9i6n9cpo7sceRlN98K by Gargron@mastodon.social
       2019-04-23T18:55:26Z
       
       0 likes, 0 repeats
       
       @staticsafe It would have been if it was a high-profile PR. It was not. Look, even the most exciting PRs, usually nobody ever looks at. It's basically internal communications between regular contributors.
       
 (DIR) Post #9i6n9d7B5IW7JdV1Cy by bhtooefr@mastodon.social
       2019-04-23T19:00:10Z
       
       0 likes, 1 repeats
       
       @Gargron waitso when someone complains about a feature being deployed to RCs or release builds, you complain they should have said something on GitHubwhen people say something about a discussion on GitHub, the medium that you've directed people to for discussion of future Mastodon functionality, you complain that the post was "basically internal communications between regular contributors"something wrong here tbh