I thought of a completely trivial way for #Mastodon to implement all their soft security stuff w/o content leaking when it federates to incompatible servers.
It's such an obvious idea that I can't help but wonder if @Gargron is already doing it...
The idea: Put sensitive content in a non-standard XML element (e.g. <scopedcontent> instead of <content>). Poof, the problem just goes away, until a node is actually malicious.
@JollyOrc Not quite.
If I understand correctly, if you set a post to "followers only" that disables boosting in the UI and prevents the toot from appearing on public timelines.
As I understand it, GNU Social doesn't implement either of those behaviours.
The scoping features require cooperation from the receiving server, much like deletion does.
They've got the content, but implementing the implied social contract is work not all have done - or want to do!
