Privacy

31951 readers

432 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
Don't promote proprietary software
Try to keep things on topic
If you have a question, please try searching for previous discussions, maybe it has already been answered
Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
Be nice :)

Related communities

Chat rooms

[Matrix/Element]Dead
Discord

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago

MODERATORS

[email protected]

534

Signal Is More Than Encrypted Messaging. Under Meredith Whittaker, It’s Out to Prove Surveillance Capitalism Wrong (www.wired.com)

submitted 2 months ago by [email protected] to c/[email protected]

272 comments fedilink hide all child comments

https://ghostarchive.org/archive/0QgXq

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 2 months ago (2 children)

They could be waiting until it becomes a big issue

I guess I don't see that as a problem if its causing a big issue.

Let me throw it back to you: If you were providing a service and a third party client was using your resources and causing a "big issue" like you stated, would you not want to remediate the problem? Lets say you introduced a new feature, but it doesn't work for 15% of your user base because they're using an outdated third party client that may not get fixed for another year or two - if ever. What would you do?

Here's another example, lets say someone develops a client that lets you upload significantly bigger files and has an aggressive retry rate that as more people start using your client, it starts increasing the hardware requirements for your infrastructure. Do you just say "oh well", suck it up and deal with having to stand up more infrastructure due to the third party client doing things you didn't expect? Is that reasonable?

[–] [email protected] 1 points 2 months ago* (last edited 2 months ago)

https://hackertalks.com/comment/4806772

They have demonstrated history of asking third party clients to not use the signal name, and not use the signal network. The client that currently exists that do this do it against the wishes of the signal foundation

you keep moving the goal posts, Ive justified my position in the original comment.

By all means, use signal, I do. But let's not deny the realities. I think we've covered all that we need to cover in this discussion thread. We don't have to agree and that's okay, and I wish you a good day, but I'm not going to respond anymore

[–] [email protected] -1 points 2 months ago

The servers should absolutely not trust the client. Likewise, the client should not trust the server. When that is the case it is impossible for the third client to have more functionality than the mainstream client.