this post was submitted on 04 Jun 2026
873 points (94.1% liked)

Selfhosted

60887 readers
923 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Please don't expect the community to give you answers to your questions which you then delete right afterwards. Those of us who put time into answering your questions are not doing so just to serve your personal needs, we are here to help build a community knowledge base that others can search and reference.

This has become a chronic issue with Lemmy and its starting to feel like it's a waste of time to answer questions.

you are viewing a single comment's thread
view the rest of the comments
[–] queerlilhayseed@piefed.blahaj.zone 13 points 1 month ago (3 children)

I have mixed feelings on post deletion. On the one hand, historical technical forum conversations are an incredibly valuable resource, and /c/selfhosted is a technical community. The value comes from having a history in context, and deleting part of the context damages the whole and makes the whole corpus less useful overall. It also allows incorrect or outdated information to fester when there isn't a strong historical context that can be referenced.

On the other hand, people are right to be concerned about leaving large tracts of text available on the open internet, where it can be scraped, profiled, and possibly de-anonymized. I am very sympathetic to those who delete out of concerns for their own privacy, and I don't know what a good solution is.

Maybe a compromise would be (on user "delete") to leave the contents of a post intact, but simply delete the username from the post, and the post from the user's history? Deletion on the fediverse is a bit of a sham anyway, and it would leave valuable discussions intact for other users.

[–] LovableSidekick@lemmy.world 14 points 1 month ago* (last edited 1 month ago) (2 children)

I think a good solution would be to create a community specifically to connect people who don't want to share their posts and people willing to provide individual help. They could find each other and DM a conversation. Milking a public forum for advice and then vandalizing it by deleting the post is definitely NOT a good solution, and I do not share your sympathy for people who do that. It's like curtaining off a few back rows of a bus to use all day as an office - although that could have been funny in a Seinfeld episode.

[–] queerlilhayseed@piefed.blahaj.zone 2 points 1 month ago (1 children)

There are good reasons for hiding a paper trail. Specifically in a self-hosting community, I understand operators wanting to hide their particular technical details from those who would wish to target them. This can be government agencies who like to arrest or kill dissidents, or freelance assholes who just like to attack queer infra where they can. I don't think deleting posts is particularly effective, and the privacy concerns would be better addressed with a safe alt or a burner account, but I get why some people do it. Privacy is hard and when the stakes are high, people tend to over-secure rather than risk under-securing.

[–] xavier666@lemmy.umucat.day 2 points 1 month ago

It's always standard OPSEC to anonymize/obfuscate your infra details.

If they are really concerned about privacy, host a local LLM and query it. You'll get a subservient AI which doesn't argue with you about data permanence, and all your data stays inhouse. Stop participating in public forums.

[–] frongt@lemmy.zip 0 points 1 month ago (1 children)

That would be any freelancing hiring platform.

[–] LovableSidekick@lemmy.world 2 points 1 month ago* (last edited 1 month ago) (1 children)

I spent many years as a software dev contractor working through agencies, but I still don't see the parallel.

[–] frongt@lemmy.zip 3 points 1 month ago (1 children)

I mean if you want personal, private, ad-hoc support, hire someone to work for you personally.

[–] LovableSidekick@lemmy.world 1 points 1 month ago (1 children)

And yet free opensource software exists. Lots of knowledgeable people are happy to help others during their free time.

[–] trackball_fetish@lemmy.wtf 4 points 1 month ago

It's me, I'm people

[–] ayyy@sh.itjust.works 7 points 1 month ago

If you post something to a federated platform, it is literally never deleted. There is no privacy to be gained from deleting posts from the fediverse.

[–] Deebster@infosec.pub 5 points 1 month ago

If people want to ask something that they don't want tied to them, they should use a throwaway account. Scrapers will probably grab the text quickly (especially if they're using ActivityPub) so it's a false sense of security to do it days later.