Random quick rough mock I made this morning, but only posting it now @scottjenson https://social.coop/@scottjenson/115300084480889349
-
Random quick rough mock I made this morning, but only posting it now @scottjenson https://social.coop/@scottjenson/115300084480889349
-
Random quick rough mock I made this morning, but only posting it now @scottjenson https://social.coop/@scottjenson/115300084480889349
@cheeaun @scottjenson I've sometimes felt that "private" implies more privacy than is actually included without e2e encryption. Maybe there is a clearer term like "limited" or "restricted"?
-
@cheeaun @scottjenson I've sometimes felt that "private" implies more privacy than is actually included without e2e encryption. Maybe there is a clearer term like "limited" or "restricted"?
@abraham @scottjenson I start to iterate using โprivateโ because both requires login. But I get your point on it being related to privacy stuff. Though we already have โPrivate mentionโ here ๐
-
@abraham @scottjenson I start to iterate using โprivateโ because both requires login. But I get your point on it being related to privacy stuff. Though we already have โPrivate mentionโ here ๐
-
@scottjenson @cheeaun @abraham I agree. Having the private mention interface in the same UI as public posts is a huge source of accidental leaks on Mastodon. I realize they only differ in addressing, but it's far too easy to make a mistake.
We have a draft spec for E2EE messaging over ActivityPub in the W3C social community group right now, btw. Implementers wanted!