It doesn’t take a genius to realize that a long-running account on any platform can easily be used to build a profile of someone.
Since many discussions on Lemmy and other platforms can often cause someone to write about their job, family, hobbies, where they live (city/community), etc., there’s a lot of concern about non-private post history being used against someone.
Other than using fake names, throwaway emails, etc. are there any other best practices for handling this?
Should we be creating new accounts/profiles every once in a while?
I think the concern (for anyone) is that with enough post history, just about anyone would be able to identify you AND would have knowledge of just about every aspect of your life.
This goes beyond what Amazon or Google might do, since they’re just concerned about monetizing.
Nobody can anticipate all risks, especially if it comes out of the blue from an ex-employer, ex-partner, political opponent, neighbor, friend or ex-friend, etc.
Since many of us are new to Lemmy, and have an opportunity to blunt this kind of profile building right from the start, I was hoping that there may be some strategies we could use right away.
Right. You can’t anticipate how historical posts can affect you later, but are there strategies to limit this exposure?
I haven’t done this (yet), but I know some people will create numerous profiles and limit certain topics/subreddits/lemmy communities to specific profiles. That way, if profile A never discusses work or family, but only gardening, there’s almost no chance that someone targeting that profile could do much harm.
I guess, this would be the same as having multiple email addresses or alias/forwarding email addresses… to limit what information someone could possibly get from you, even if they had access to all email related to that single account.
I’d say no. Your fooling yourself if you think you can. The best you can do is make it harder, but that is only true compared to computing power. Problems that were hard, are now possible because computing power has increased.
Any one profile could give enough to out you. A textual analysis can tie separate text posted by different accounts to the same person. (Varying degrees of accuracy for this. If anyone would do parse all Lemmy comments to do this is separate issue.)
In short, don’t post anything that might compromise you. But how fruitful are conversations if you’re always hiding anything that might out you? Stick to only non personal stuff? Information about local shops, movies, etc etc can all narrow down your location. But even with that, narrowing down to a town with 50 people in it, is different to a town with 1 million people.
It isn’t only what you post. Someone else can also out you. Someone who knows you, or someone that you don’t know. Your PC can be hacked, etc etc. The options go on and on.
Define what your risk is. Define who your adversaries are. Then plan how to operate with acceptable risk tolerance.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !privacyguides@lemmy.one
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:
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:
We prefer posting about open-source software whenever possible.
No soliciting engagement: Don’t ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don’t repost topics which have already been covered here.
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.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
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.
No misinformation: Extraordinary claims must be matched with evidence.
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.
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.
There is no privacy online. Enough incentive your history across accounts, instances, usernames can be combined.
Think about risks instead. Who is going to use your post against you? How much effort are they going to go to? What’s your risk?
If you’re hiding from the a government, best not to be online. If what you post will get you killed, don’t post it.
I think the concern (for anyone) is that with enough post history, just about anyone would be able to identify you AND would have knowledge of just about every aspect of your life.
This goes beyond what Amazon or Google might do, since they’re just concerned about monetizing.
Nobody can anticipate all risks, especially if it comes out of the blue from an ex-employer, ex-partner, political opponent, neighbor, friend or ex-friend, etc.
Since many of us are new to Lemmy, and have an opportunity to blunt this kind of profile building right from the start, I was hoping that there may be some strategies we could use right away.
Then stick to “don’t be online” as you no matter what you do, you can’t anticipate how that will expose you later.
Right. You can’t anticipate how historical posts can affect you later, but are there strategies to limit this exposure?
I haven’t done this (yet), but I know some people will create numerous profiles and limit certain topics/subreddits/lemmy communities to specific profiles. That way, if profile A never discusses work or family, but only gardening, there’s almost no chance that someone targeting that profile could do much harm.
I guess, this would be the same as having multiple email addresses or alias/forwarding email addresses… to limit what information someone could possibly get from you, even if they had access to all email related to that single account.
I’d say no. Your fooling yourself if you think you can. The best you can do is make it harder, but that is only true compared to computing power. Problems that were hard, are now possible because computing power has increased.
Any one profile could give enough to out you. A textual analysis can tie separate text posted by different accounts to the same person. (Varying degrees of accuracy for this. If anyone would do parse all Lemmy comments to do this is separate issue.)
In short, don’t post anything that might compromise you. But how fruitful are conversations if you’re always hiding anything that might out you? Stick to only non personal stuff? Information about local shops, movies, etc etc can all narrow down your location. But even with that, narrowing down to a town with 50 people in it, is different to a town with 1 million people.
It isn’t only what you post. Someone else can also out you. Someone who knows you, or someone that you don’t know. Your PC can be hacked, etc etc. The options go on and on.
Define what your risk is. Define who your adversaries are. Then plan how to operate with acceptable risk tolerance.