2·
3 days agoAll set thanks!
Mod alt of @curbstickle@anarchist.nexus
If you need to DM me, please reach out to me there, this account is primarily for dealing with reports.
- 0 Posts
- 74 Comments
Joined 4 months ago
Cake day: June 6th, 2026
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
@frey@lemmy.world please update with the appropriate tag per rules 7/8Thanks
Its a pretty big stretch to call this self-hosting related…
Locking the thread.
Thats about all that we can control on this side, though. It would be great if more people made use of https://ai-declaration.md/, its what the rules here are (mostly) based on for disclosure, but half the time even a proper readme is more than what a repo will contain.
At least as a post here we can address appropriately.
Having a discussion on this is perfectly fine, but I want to remind of two things.
- Rule 1: Be civil.
- Use the report button. Your comment is not a report. I do not get an alert about your comment unless its reported.
Lets keep it friendly and constructive.
but i will only hate/judge/completly ignore programms/tools/documentation thats clearly vibecoded slop.
If its disclosed and tagged, then keep that thought to yourself - its now OT (rule 3) or potentially a rule 1 violating comment depending on how its phrased. In either case, its not appropriate for the post.
If its not disclosed and/or tagged, report it.
Don’t disclose - slop
“Don’t disclose” means report, not commenting.
Disclose with AIP - not specific enough, still assume slop
Not specific enough because it requires a disclosure, any comments of “slop” should be reported not interacted with.
Disclose more specifically - “slop”
“Slop” with an appropriate disclosure is a rule 1 violation. Report.
Disclosure is for the post, not comments.
If you see it in comments but not in a post, report it. Not comments, but reporting, otherwise its just more cleanup later.
Please add your disclosure. See rule 8. Locking for now + cleanup.
What I might consider is a “winterized” variable per hose/pipe that may be a concern, and only notify if winterized is false for those, and have the notification list specifically not winterized.
That state would be manual per, but then you would be able to get a more meaningful reminder to only those that would be at risk.
Please review rule 7 and tag as appropriate. If AI assisted at any level, please also add the required disclosure.Thanks!
For the record, the disclosure should look like this for readability/consistency, you can copy/paste if you’d like:
AI Disclosure:
- Implementation - Assisted
- Testing - Assisted
- Documentation - Assisted
The items without assistance do not need to be listed, but you can also put n/a there or none if you want.
Because it creates an OT discussion and the tag doesn’t apply. A discussion I won’t necessarily know about until after its gone on and gotten heated.
Comments aren’t for rule policing, just use the report button please.
Italics = fixed crappy autocorrect. Be a use? Wtf.
Up until the point the resources available (CPU/ram/storage) become a problem.
That said, managing those apps as installations can be troublesome, which is why people like podman/docker. Updates are more contained, system updates don’t break services, and vice-versa.
A more comprehensive option is to use Proxmox or similar to manage services as a combination of Virtual Machines, LXC’S (Linux containers), and maybe podman/docker on a VM. Note that Proxmox techincally supports importing a docker container as an LXC, but this is a one-time action. Not recommended. (EDIT: For the record, there is a Proxmox on pi effort, but its community supported not Proxmox supported as of the last time I looked.)
Navidrome and pihole are the easy ones on that list also. Jellyfin itself is easy, but you aren’t going to be transcoding video on the fly, so make sure its in a format that is friendly to all of your devices, transcoding in advance if needed.
Use the report button, not the comments.
And as covered already - no it isn’t.
I’d sum it up with:
“Ew.”
Its one thing to offer bespoke customization for businesses. Its entirely another to work to prevent any indication that the software is being run by someone other than the creator of the software. IMO, it goes against self hosting as a practice.
It could be everything I want and more, and it would immediately turn me away. Which, in turn, would also turn me away from recommending it to others, including businesses.
I’d call it a pretty bad strategy.
This post is off-topic for the community.
That said, its a topic people here are quite passionate about, which is why it gathered quite a bit of comments already.
I’m going to leave it up, but locked.
Secure enough I suppose.
f2b at the FW, auth with MFA for anything exposed, anything local only has restricted access at the FW level, with exposed (via proxy) and local-only (separate proxy) on different vlans. Each service is (typically, with some exceptions) an LXC, with additional rules and templated out based on use case. The few cases where docker is involved is local-only and that has its own vlan with additional rules.
There is no differentiation around “who” in self-hosting. I would even say it should be encouraged to have companies support open-source tools like Anubis, especially financially.
If you want to start a meta discussion about it go for it, but I won’t remove this discussion just because a business is involved. Especially considering many of us self-host for our own personal businesses as well, it would seem pretty arbitrary to me.