Good day: We've had a few requests to mirror public-inbox archives that originate on other systems so they can also be searchable and viewable via lore.kernel.org. I've been dragging my feet on these requests, because they are a potential liability in terms of GDPR compliance.
If we are merely mirroring the archive from some other location, then there should be a clear indication of the origin of the data and contact information of the maintainer of the remote archive where someone could send requests for any data removal. It's best if this is visible both via the web view and in raw messages retrieved via our service, e.g. via an "X-Archive-Origin:" header or something similar. Any thoughts on this issue? CC'ing the folks who have been dutifully asking me to mirror their lists on lore, and who I'm sure are sick and tired of me not getting any movement on this issue. -K
