You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Me using Session can be seen by my internet provider, at least because it uses special port. Also, there's no such thing as "being online" in Session Messenger: every message is just sent as separate package. Now, if I write a message, my provider sees that the new package was sent at 13:26:31, and at 13:26:38 new message has appeared in group X by user named Bob. of course, this is not ultimate, but this can be repeated 10 or 20 times, until provider sees clear 99,9% correlation between some IP conneting to Session and some user named Bob writing a new message.
SOGS are easiest places to monitor users' activity, yet in some really rare cases (where we have a doubt that some person is this session user) this could be done also in P2P chats.
Am I correct, or did I get it all wrong? If I am, how could we solve that? Part of the solution could be #3271. Another part could be Session using standard port, of in some other way make connection to Session hard to separate from a connection to anything else.
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing request for feature?
What feature would you like?
Me using Session can be seen by my internet provider, at least because it uses special port. Also, there's no such thing as "being online" in Session Messenger: every message is just sent as separate package. Now, if I write a message, my provider sees that the new package was sent at 13:26:31, and at 13:26:38 new message has appeared in group X by user named Bob. of course, this is not ultimate, but this can be repeated 10 or 20 times, until provider sees clear 99,9% correlation between some IP conneting to Session and some user named Bob writing a new message.
SOGS are easiest places to monitor users' activity, yet in some really rare cases (where we have a doubt that some person is this session user) this could be done also in P2P chats.
Am I correct, or did I get it all wrong? If I am, how could we solve that? Part of the solution could be #3271. Another part could be Session using standard port, of in some other way make connection to Session hard to separate from a connection to anything else.
Anything else?
No response
The text was updated successfully, but these errors were encountered: