Server'd allow for automatically stripping metadata such as IP of recipients, or client agent #163
Labels
No labels
Android
CS::needs customer feedback
CS::needs follow up
CS::needs on prem installation
CS::waiting
Chrome
Design:: Ready
Design:: in progress
Design::UX
E2EE
Edge
Firefox
GDPR
Iteration 13 IM
Linux
MacOS
Need::Discussion
Need::Steps to reproduce
Need::Upstream fix
Needs:: Planning
Needs::Dev-Team
Needs::More information
Needs::Priority
Needs::Product
Needs::Refinement
Needs::Severity
Priority::1-Critical
Priority::2-Max
Priority::3-Impending
Priority::4-High
Priority::5-Medium
Priority::6-Low
Priority::7-None
Progress::Backlog
Progress::Review
Progress::Started
Progress::Testing
Progress::Triage
Progress::Waiting
Reporter::Sentry
Safari
Target::Community
Target::Customer
Target::Internal
Target::PoC
Target::Security
Team:Customer-Success
Team:Design
Team:Infrastructure
Team:Instant-Messaging
Team:Product
Team:Workflows
Type::Bug
Type::Design
Type::Documentation
Type::Feature
Type::Improvement
Type::Support
Type::Tests
Windows
blocked
blocked-by-spec
cla-signed
conduit
contribution::advanced
contribution::easy
contribution::help needed
from::review
iOS
p::ti-tenant
performance
product::triage
proposal
refactor
release-blocker
s: dart_openapi_codegen
s::Famedly-Patient
s::Org-Directory
s::Passport-Generator
s::Requeuest
s:CRM
s:Famedly-App
s:Famedly-Web
s:Fhiroxide
s:Fhiroxide-cli
s:Fhiroxide-client
s:Fhirs
s:Hedwig
s:LISA
s:Matrix-Dart-SDK
s:Role-Manager
s:Synapse
s:User-Directory
s:WFS-Matrix
s:Workflow Engine
s:dtls
s:famedly-error
s:fcm-shared-isolate
s:matrix-api-lite
s:multiple-tab-detector
s:native-imaging
severity::1
severity::2
severity::3
severity::4
technical-debt
voip
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Matthias/conduit#163
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Feature request: The server should automatically strip unnecessary metadata, such as the IP of recipients
Description
Once a message has successfully been delivered to a recipient (for example a read receipt has been received from the addressee), then the server should automatically after some short amount of time by itself in default configuration already, strip the metadata from a message that are no longer necessary for preserving that message on the server, such as the IP address of the sender, as well as their client identifier, and the recipient (which's attained during transport, but later no longer necessary to keep).
This'd be a great feature over Synapse, which doesn't take any care to protect, and not store user metadata when not necessary.
changed title from Server{- shoul-}d automatically strip metadata such as IP of recipients to Server{+'+}d automatically strip metadata such as IP of recipients
changed the description
changed the description
As far as I know we don't save IP addresses ourselves. Of course they still show up in apache logs and depending on the configuration in conduit logs, so if you clean those from time to time you should be good.
That being said we want to implement the matrix feature in the future where a user can see the ip addresses of each device of his account
@timokoesters In addition to that, an option for the server admin to configure the number of hours/days after which in periodic intervals of that specified period the IP/location metadata should be automatically deleted each time from the server logs also by themselves (if the admins don't want to think about always doing it manually), would be useful as well.
Thanks,
changed title from Server'd automatically strip metadata such as IP of recipients to Server'd {+allow for +}automatically strip{+ping+} metadata such as IP of recipients{+, or client agent+}
changed the description