@bob I think there are quite a few benefits that GNU Social could get by supporting AP. I hope there isn't too much "burn" by seeing it as a "Mastodon vs GNU Social" battle. I tried pretty hard to avoid that; @mmn and @deadsuperhero both at least can verify that I did try to get GNU Social and everyone else involved. I know that's not an obligation for GNU Social t…
@cwebber The only reason !GNUsocial doesn't have #ActivityPub yet is because I have a fulltime job and noone else has been up for the task .] Though I'm pretty sure it'd still just be the 100% public parts of AP that would be used/promoted, as I'm pretty much convinced there's no such thing as privacy in the social sphere anyway and anyone using "private" communicatio…
@cwebber Indeed you and others involved with AP spec development have been very inclusive, inviting and encouraging. I very much appreciate your (and everyone else's) efforts that have been put into #ActivityPub.
@nightpool @cwebber Whether e-mail is used or not is more a question of legacy than that it would respect anyone's privacy. My argumentation is primarily that an environment where the only difference between publishing your sensitive posts/pictures privately or publicly etc. is the value of some checkbox - then it's not appropriate for private communication. Even less…
@platano Very true. My point is however that those things (leaks) can never be reduced to zero due to people being people. However, I don't want to see a system where these things can happen by accident. Compare with the policy changes at Facebook, where suddenly things you _thought_ you had set to private suddenly weren't because Facebook's idea of a "friend" (or wha…
@gargron While it's obvious I would code it like that, my argumentation is that any evil person anywhere could set up an evil node and users would have no idea...
@cwebber Unless it was a feature with this certain host. Email is however considered like delivering via envelopes while social web platforms are like bulletin boards or at least relatively large group meetings.
@cwebber Then again, the "expected usecase scenario" with !XMPP is like with e-mail. There's no UI (or expectation of any UI) that has a button which says "share this with the world instantly and publicly". Or any kind of accidental tagging-someone-into-a-conversation-and-thus-maybe-letting-them-get-some-conversation-history issues. I'm not talking technical and crypt…