@kev @natecull @switchingsocial things don't have to be surprising to be notable

@aral still, both email and ap's "privacy guarantee" is the same: your messages will be private to the servers that receive them. that doesn't preclude the "rogue admin" threat model, but it doesn't make either "public" per se.

even if your measuring stick for privacy is e2ee, you're basically making the mistake of equivocating existing implementations with the spec itself. pgp exists for email, but hasn't been done yet for ap. it's like saying xmpp is public despite omemo

@cwebber @bhaugen

@mmn @dansup @bob I think there's a difference between letting 3rd parties build tools vs. building them yourself and packaging them in by default.

For example. some vain Instagram users download apps that show graphs of follows, unfollows, etc. But users have to seek those out and developers have to build those. Should the pixelfed project's official stance be to enable or encourage that use case? Implementation and design will matter.

@mike @bob I'm not personally invested in zot as a protocol, nor in activitypub, but I think AP is a bit easier to understand and more widely applicable. For example: if a service is intended to be public or almost always public, then what benefit does a rich permission system add? In the case of PeerTube, for example, videos are served via WebTorrent, which benefits from having more peers much more than it does from privacy.

ugh i really hope crossposters don't slowly choke mastodon like they did to diaspora*

if you're just crossposting everything you tweet on birdsite then what even is the point of making a mastodon account? that's glorified spam at worst, and a recipe for abandonment.