this post was submitted on 22 Jul 2026
55 points (96.6% liked)

Selfhosted

60934 readers
872 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
55
Self-hosting, data sovereignty and cyberattacks [AIT] (aussie.zone)
submitted 3 days ago* (last edited 3 days ago) by SuspiciousCarrot78@aussie.zone to c/selfhosted@lemmy.world
28 comments fedilink hide all child comments
 

https://lemmy.world/post/49736885

If you follow AI news at all as part of your self-hosting interests, you may have become aware recently that open AI (the frontier lab between behind chat GPT) has admitted (loosely) culpability in an cyber attack against HuggingFace (the major repository of open-weight models.)

The details that present are somewhat sketchy, but the gist of it is that open AI seems to have given unrestricted access to a AI agent, which then attacked hugging face, who in a twist of deliciousness, used an open source agent to defend themselves.

I'd joke and tell you to make sure that you haven't left any open ports on your router, but if you're here reading this I think probably you know better than that.

Less comically, there's a weird intersection here between self-hosting, sovereignty and encroachment by big tech that is worth pay attention to.

It should certainly spur people on to seriously consider self-hosting as much of their infrastructure as they can (and securing it) if this is the preview of things to come.

Something is rotten in the state of Denmark.

I just wish I'd bought more SSDs.

you are viewing a single comment's thread
view the rest of the comments
[–] nitrolife@hikki.team 6 points 3 days ago (1 children)

I think the problem has been slightly exaggerated. If you're not hosting several dozen services, you can reduce your attack surface down to one Nginx server. For an even stricter setup, just enable mTLS.

[–] TeaWithDani@lemmy.world 1 points 13 hours ago* (last edited 13 hours ago) (1 children)

Prevent password logins where ever possible too, especially SSH. Use ed25519 keys. Perform server actions with least privilege users, prevent root logins. Immutable systems and containers are a helpful tool too.

I also just host my public facing stuff on a VPS. DDOS protection and just otherwise isolated. 2FA on the VPS too.

[–] nitrolife@hikki.team 1 points 12 hours ago* (last edited 12 hours ago) (1 children)

Just don't expose SSH to internet. It's a complex protocol with many CVEs. And you realyy don't need access to SSH from anywhere. Replace access from ineternet to a WireGuard tunnel that has almost zero attack surface area and properly configured iptables rules. And that’s it.

[–] TeaWithDani@lemmy.world 1 points 11 hours ago

Sure, that goes with it. Good reminder.