Selfhosted
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:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
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.
-
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:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
@selfhosted
@curbstickle I didn't make Wanderer, I just deployed it on my servers. Weather or not they used AI is no business of mine and I don't think it is reasonable to ask me to investigate every service I deploy for their use of #AI. I don't really care if they used it or not. It isn't my project.
Ah, got it, I misunderstood from the post, sorry about that
@eric @selfhosted @curbstickle
If you choose to selfhost an app, I think its fair for people to criticize you for it being vibe coded. Choosing to run it on your servers and then telling people you've done so is an effective endorsement you can't just handwave by saying you didn't code it.
Also as the owner and maintainer of your server, you should do some due diligence on what you host. Code without a community backing it is more likely to have security flaws go unnoticed, especially if the code isn't even being written by a human.
The same way emdashes and negative parallelisms get overused by LLMs, so will security flaws. Someone will find an exploit and that same exploit will then be usable against tons of vibe coded projects, in a way human written code, which is more varied even if "worse" in other ways, would have prevented
That really isn't the issue, and no, that would not be permitted here. It would be one thing to note that an LLM was used in some part of the project, it would be entirely different to criticize the poster based purely off whether or not there were any contributions involving LLM.
That would be a rule 1 violation.
If you want to comment on a known vulnerability, thats one thing. Commenting that its vulnerable because an LLM had a pair level patch is not.
@thepaperpilot @selfhosted @curbstickle
I actually learned about it from one of the top posts in this community so if anyone is endorsing it...