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.
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.
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 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.
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.
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
If a process needs Unix time it's much easier for that process to convert Human-Readable time to Unix time than it is for me to mentally convert Unix time to Human-Readable time... But yeah, having both would not be a problem. Having neither is.
I was really ranting about the log files that have no datetime stamp at all. I can't figure out if the problem I've got is recent, or has been going on for months. 2000 lines of log, all identical.
♻ Laurel L. Russwurm @laurelrusswurm: Replying to @BobJonkman @chillicampari @artsyhonker My twitter bridge is broken, and mustard is pooched. I'm doing too much politics to forgo that connectivity; haven't figured it out yet.