Privacy

32130 readers

1214 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

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago

MODERATORS

Signal's new version notification keeps popping up (self.privacy)

submitted 1 year ago* (last edited 1 year ago) by Extrasvhx9he to c/privacy@lemmy.ml

8 comments fedilink hide all child comments

Hey just wondering if its a problem on my end but a self update notification indicating a newer version of signal keeps popping up. I already have the latest version of the apk, 6.40.4, installed from their website, but the notification does not go away. I click it and then it states the application has been updated but after a few minutes later it pops up again. Not sure where to ask this but I would assume this place is one of the best places to interact with people that also use signal's non-playstore apk. Is this a bug on my end or are you experiencing it too?

Edit: forgot to mention I'm on grapheneos if thats a factor

Edit 2: apparently it was already reported on github and I missed it

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

[–] CommunityLinkFixer@lemmings.world 3 points 1 year ago

Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: !signal@lemmy.ml