|
Top-level
 But what I can say with certainty is that _irrespective of what happens there_ this question is not going away, and "yelling at, harassing, and brigading individual developers" is not a good way to go about solving these problems. It does not scale, it does not extend to the next instance, and it does not even allow for a discussion of a solution for _this_ instance. What you _will_ do is drive away the people who you would _want_ working on this problem. Consistently and reliably. 9/ 4 comments
 @hrefna The ironic part is that ATP actually solved a lot of those shortcomings of AP. It gives you (in theoery, federation has yet to start) as a user much more control over who gets to access your data and allows you to take your data wherever you see fit, which is still not and probably will not be possible on AP.  The trend I've seen here of treating individual developers (which, in an OSS context are volunteers freely offering their labor- I mention this only because it's very relevant) like customer service staff at one's mercy at best, and hate-mob targets at worst is galling. It also says an awful lot about the sincerity of people who do this, while cloaking themselves in the appearance and language of leftism. |
Gregory's Server
Especially when there are far deeper problems rooted in the protocol and the architecture of major fediverse apps that, so far, people have refused to correct.
So long as those are unfixed and so long as expectations here are not better managed we're going to have this problem again.
and again.
and again.
So if we don't want to keep having this same conversation we have real work to do, and this behavior like what we saw yesterday will—at absolute best—only get in the way.
10/10