• 2 Posts
  • 107 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle





  • I suppose it’s a call to arms - the intended audience is those who are familiar with all those acronyms. It’s meant to ignite a fire in the belly to spur individual action against the proposed Chat Control legislation.

    I know what you mean though. The reality of “resisting” is actually kinda messy. Using all the mentioned tooling is exhausting. Much like I don’t think that consumer recycling is going to save humanity, I don’t think that if everyone “made the little effort required to secure their data and their communications” it would end crazy proposals like Chat Control. TLS is so common now (in HTTPS) and WhatsApp (implementing e2ee) is incredibly popular. Yet here we are.

    The article briefly mentions open-source software. To me this is where I see more private & secure by design stuff like you mention. I’m happy that things like Lemmy exist making countermeasures like 3rd party cookie blocking sand URL cleansing irrelevant.












  • I agree. ActivityPub messages are not necessarily public information; implementations like Mastodon and Lemmy just assume it - and there’s nothing stopping the services relaying the messages elsewhere afterwards.

    Actually in my fiddling with ActivityPub I’ve made some posts and comments to a Lemmy instance which were not relayed to other instances, even though they would have been if I made them using Lemmy. So there’s definitely opportunity for systems to implement features inbetween “totally public” and “single recipient”.



  • Yeah I’ve always found that AllowedIPs name a little bit misleading. It is mentioned in the manpage:

    A comma-separated list of IP (v4 or v6) addresses with CIDR masks from which incoming traffic for this peer is allowed and to which outgoing traffic for this peer is directed.

    But I think it’s a little funny how setting AllowedIPs also configures how packets are routed. I dunno.