About the only thing I agree with: "We're looking at Mastodon breaking off from OStatus and becoming its own thing sometime in the not-too-distant future..." https://trysdyn.dreamwidth.org/3027.html
The article attributes lots of statements to the authors of both #GNUsocial and #Mastodon, things that I've never heard either state online (nothing that reached my timeline, anyway). The whole article seems to make the difference between #GNUsocial and #Mastodon much more acrimonious than I've experienced.
@bobjonkman And after creating yet another somewhat walled garden GS/the Fediverse will be back to what it was before the Mastohype. This minority will just keep existing as it did for nearly 10 years now and I'm quite happy with that.
The author's explanation of expectation of "security" or "privacy" in #Mastodon is concerning. Knowing that !OStatus provides no privacy or security at all, bolting privacy and security features onto #Mastodon isn't going to work. This is not the fault of #OStatus, nor is it a shortcoming of #GNUsocial that it doesn't implement security or privacy with #OStatus, but recognizes that constraint.
How well known is it amongst #Mastodon users that their privacy features don't really work outside of their own instance? Perhaps some admins know, but much of the flaming is coming from people angry that #GNUsocial doesn't follow the privacy conventions of #Mastodon. But being angry that the #GNUsocial developer(s) aren't creating the same illusion of privacy is really misdirected anger.
The big thing that's prevented me from even trying #Mastodon is the lack of support for !Fedgroups. And that's not a wrongful implemenation of #OStatus; I believe #Fedgroups are implemented as a specific client behaviour, nothing to do with OStatus.
I'm perfectly happy that #Mastodon exists, and if it implements #ActivityPub in a future version, more power to it. And if it drops #OStatus support, well, that's what forks (or reimplementations) like #Mastodon are for. But don't blame #GNUsocial developers for not following #Mastodon's road map for the future.
@bobjonkman @taiganaut I think it sounds pretty accurate, except that "blissfully unaware", "pro-Masto" and "anti-Masto" are the only three categories of users listed.
They're missing the huge categories "aware, don't care", "can't we all just get along" and "nice to see all these new people, hope they figure out the pond is bigger than it looks" and the small category "I have six alts to tie this mess together".
Oh, now I even noticed that I read this backwards. They're actually stating GS instances blocking Masto as the prime case and Masto blocking GS as the vice versa. o_O
> Have a look at XMPP for proper privacy and security.
I don't get this argument, and I've seen several people make it. Without E2EE, XMPP or email is no more inherently secure than OStatus+mastoflags or AP.
It's just that we don't have an existing base of implementations that put your XMPP or mail conversations on the web. That's a valid argument, but one cannot make it in the same breath as "[all it takes is one malicious Masto instance]" or "[the web is inherently insecure]".
Security in XMPP and SMTP is just as bolted-on as any other except those E2EE-from-birth protocols where e.g. your pubkey is your identity.
@clacke I accept most ofbyour arguments and yes, I make the assumption the user chooses a secure client. But with !xmpp your keys when using encryption are stored locally with your client and not the server - that is close to impossible with the web.