Conversation

Notices

1. Embed this notice
   on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ (lain@lain.com)'s status on Wednesday, 06-Mar-2024 17:01:28 JST on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ
   some new "local blockwart call devs idiots and 'extremely alarming'" sesh, this time with lemmy: https://github.com/LemmyNet/lemmy-ui/issues/2384
   
   I kinda doubt that it's even possible to even make a gdpr-compliant general AP server, there's no way to 'take back' posts and no way to know how far a post federated.
   • Haelwenn /элвэн/ :triskell: and kaia like this.
   • Embed this notice
     kaia (kaia@brotka.st)'s status on Wednesday, 06-Mar-2024 17:10:37 JST kaia

     in reply to
     @lain drama tiem :SoraWow:
     on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Wednesday, 06-Mar-2024 17:17:06 JST 

     in reply to
     @lain >telling g*rmans with their bureaucracy to fuck off
     Kinda keyed, if I dare to say so.
     ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 06-Mar-2024 17:33:55 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @lain You can somewhat know how far a post federated with hard-requiring signed fetches but that's only the first step, you'd also need things like batch deletes ("Let's send out one Delete per post" is pure madness).
     But at the end of the day, something sent to a ton of independent servers tends to stay forever so the "right to be forgotten" is quite limited (but we could do better).
     on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 06-Mar-2024 17:57:28 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Phantasm
     @phnt @lain You don't work around GDPR that way, it's not a technical standard, it's a law.
     
     Also I think you've missed the "somewhat" keyword, I'm not talking about guarantees but about doing better (GDPR or not in fact).
     
     > Generally what you put on a decentralized network will stay on it for almost forever.
     
     Here you're literally rephrasing what I've already said here:
     
     > But at the end of the day, something sent to a ton of independent servers tends to stay forever so the "right to be forgotten" is quite limited (but we could do better).
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Wednesday, 06-Mar-2024 17:57:29 JST Phantasm

     in reply to

     • Haelwenn /элвэн/ :triskell:
     @lanodan @lain I don't see this ever happening. You can try to minimize the number of servers that have your message/post, but it's never guaranteed to be that way. The Mastodon way of sending out rejects to every instance that might have the object is pretty close to what you can achieve without relying on servers not lying. Generally what you put on a decentralized network will stay on it for almost forever.
     
     GDPR is a joke anyway. Most parts of it got worked around in weeks.
   • Embed this notice
     narcolepsy and alcoholism :flag: (hj@shigusegubu.club)'s status on Wednesday, 06-Mar-2024 18:00:00 JST narcolepsy and alcoholism :flag:

     in reply to

     • kaia
     @kaia @lain trauma time?
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 06-Mar-2024 18:07:33 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • Phantasm
     @phnt @lain For example even without GDPR or whatever privacy concerns, having deletes working is important in the same way a working garbage collector is.
     It's often useless to keep invalidated data and in the case of ActivityPub, things like not having proper deletes of following relationships means higher network loads, and no delete of accounts means higher database loads. And as far as I can tell both aren't really working properly.
     on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ likes this.
   • Embed this notice
     on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ (lain@lain.com)'s status on Wednesday, 06-Mar-2024 18:25:48 JST on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ

     in reply to

     • joe
     @joe lemmy BUSTED
   • Embed this notice
     joe (joe@social.thisisjoes.site)'s status on Wednesday, 06-Mar-2024 18:25:49 JST joe

     in reply to

     @lain He looks like that thunderfoot guy lol

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 06-Mar-2024 18:58:05 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Marcin Mikołajczak
     @mkljczk @lain Which for me has more issues related to spam, and interoperability rather than privacy ones, like you could just block threads.net (in your instance or user) or quarantine it (in your instance) if it's a concern.
     Like threads.net could be like gmail.com, which is de-facto the one setting the standards of how email works while being one of the biggest sources of spam.
   • Embed this notice
     Marcin Mikołajczak (mkljczk@pl.fediverse.pl)'s status on Wednesday, 06-Mar-2024 18:58:06 JST Marcin Mikołajczak

     in reply to

     • Haelwenn /элвэн/ :triskell:
     @lanodan @lain and yet some complain about Threads federation going to be opt-in