this post was submitted on 03 Jan 2026
39 points (93.3% liked)

Selfhosted

54534 readers
740 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] irmadlad@lemmy.world 6 points 1 week ago (1 children)

Every so once in a while I get the notion to run a honeypot, but it doesn't seem prudent for me to attract that much attention to my network. I can already see the traffic using ntopng, and pfsense/unbound/suricata/pfblockng and robust ruleset do all the heavy lifting. I block everything, then only allow what is absolutely necessary. If it were run solely on a small VPS or droplet, it'd be an interesting project, but I'm not sure I want to poke the bear that much on my local network.

[–] drkt@scribe.disroot.org 1 points 1 week ago

You shouldn't run a honeypot for any other reason than fun and research, but if you're into either of those, go for it!