lemmy’s approach still relies on audience targeting for privacy, just like mastodon. using a distinct object type (which is off spec btw) is “more secure” just because nobody else knows what lemmy is doing
Comment on The fediverse has a bullying problem
rikudou@lemmings.world 5 days ago
Who would’ve thunk that misusing the same type for both public and private posts (with a sprinkle of weird mention rules to determine the visibility) could backfire?
Well, definitely not Mastodon devs. Lemmy’s current approach of using an entirely different type is much better.
If you’re interested in some details, I recently wrote a comment about it: lemmyverse.link/lemmings.world/comment/14476151
iltg@sh.itjust.works 4 days ago
rikudou@lemmings.world 4 days ago
I said better, not more secure. It’s not as easy to accidentally leak the message. It’s equally easy to intentionally leak it.
PhilipTheBucket@ponder.cat 5 days ago
Yeah, the whole thing of “if #public is in
toand the user is incc, it means one thing, but if it’s the other way around, it means something different” just reeks of “IDK I just wanted to hack it up and move on and IDGAF how platforms other than Mastodon are going to wind up handling it.” Which is fine… as long as your users universally understand that that’s your level of care towards honoring non-public visibility settings they’re setting on their posts.rikudou@lemmings.world 5 days ago
Yep. Sadly, Lemmy will move on to implement this exact horrible mess in future versions.
The current ChatMessage approach is much better than crazy shenanigans with to/cc/mentions.