40
This Week in Privacy #5 (blog.privacyguides.org)
submitted 10 months ago by jonah@lemmy.one to c/privacyguides@lemmy.one
all 3 comments
sorted by: hot top controversial new old
[-] jet@hackertalks.com 2 points 10 months ago* (last edited 10 months ago)

I'm excited that Samsung's offering more years of support. But it's not clear to me that Qualcomm is actually going to provide the hardware device security patches for that time frame. Samsung may be doing something on top. But I want to make sure the extra years of support are fully up and down the hardware stack

For instance previous fairphone devices offer many years more "support" then the hardware vendor does. Meaning there's a Gap where they're just patching Android issues but not hardware issues

[-] jet@hackertalks.com 1 points 10 months ago

This brings up an interesting question. Should large organizations be forced to disclose their privacy related bug backlog? I realize this could be used for exploitation, but if they're not willing to fix it we should at least know about it

this post was submitted on 20 Jan 2024
40 points (100.0% liked)

Privacy Guides

16263 readers
1 users here now

In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.

This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.


You can subscribe to this community from any Kbin or Lemmy instance:

Learn more...


Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!

Want to get involved? The website is open-source on GitHub, and your help would be appreciated!


This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.


Moderation Rules:

  1. We prefer posting about open-source software whenever possible.
  2. This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
  3. No soliciting engagement: Don't ask for upvotes, follows, etc.
  4. Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
  5. Be civil, no violence, hate speech. Assume people here are posting in good faith.
  6. Don't repost topics which have already been covered here.
  7. News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
  8. Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
  9. No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
  10. No misinformation: Extraordinary claims must be matched with evidence.
  11. Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
  12. General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.

Additional Resources:

founded 1 year ago
MODERATORS