Privacy

32177 readers

389 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

322

Finally deleted my LinkedIn account! (hachyderm.io)

submitted 8 months ago by otl@hachyderm.io to c/privacy@lemmy.ml

96 comments fedilink hide all child comments

Finally deleted my LinkedIn account!

After putting my account into "hibernation" for the past few weeks, I finally closed it. But I'm still looking for work. Thankfully I can still find positions (SRE and software dev) by just going directly to the company's site and finding a Jobs page.

Good luck to everyone else out there looking for work!

#privacy @privacy

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

[–] bionicjoey@lemmy.ca 4 points 8 months ago (1 children)

My understanding is that Activitypub federation and that sort of privacy are somewhat incompatible. Because someone could always just create a new instance and then federate the stuff you don't want shared with them.

[–] sugar_in_your_tea@sh.itjust.works 2 points 8 months ago* (last edited 8 months ago)

The point would be sharing data that's not useful without the key. So you could share your public key and public metadata, but to access private data you'd need to get approved first. An approval request would be encrypted with your public key and contain a response key, and your response would contain your response encrypted with their key.

You obviously wouldn't be able to control what they do with your data once decrypted, but all of that back and forth can happen in the clear without giving up private information. It's the same way GPG/PGP works over email, just on a fediverse instead of SMTP.

It really wouldn't be all that hard to implement, I just don't think it would get any meaningful traction because LinkedIn is so reliant on the network effect.