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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 30 days old, your post is exempt from this rule as long as you continue to engage in comments.
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
Some people have serious ethical and quality concerns about AI usage in code in a way that's just irrelevant to the OS and IDE used to code it.
I understand that people have concerns, but those concerns are only relevant if they come from a maintainer or repo owner point of view. There is an entire spectrum of how AI is used in code, and it's not a simple yes or no thing. I am for example completely against vibe coding as it's just a risk and liability in the long run. However, to use AI to brainstorm, get suggestions, discuss architecture, learn with examples, and assist basically like someone else is sitting next to you while you code yourself... that is something completely different, and results in a completely different outcome.
In the end, it depends on can the person at the steering wheel take full ownership and accountability of the code they produced, with or without AI.
This just isn't true. Whether I'm a developer or not, I have to deal with the security issues that come with running the code. I have to deal with the bugs that come from it. I have to decide if I'm willing to support practices I may consider unethical used to produce the software, especially if I'm considering donating to the project. I don't need to be a topic expert to understand that AI code is prone to bugs and security vulnerabilities, nor do I need to be one to consider the massive ecological damage and copyright violation required to train the plagiarism machine.
Generally, people take the most issue with using it to actually generate code in any capacity. There are purists who might insist you not even touch AI, but I think most draw the line at including code or graphics not written by a human.
If we presume ethically neutral tools, sure, but the massive damage to ecosystems and towns that comes with training, using, and powering AI are seen by many as outweighing the utility they're able to provide.