1·
11 hours agoMod 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
- 84 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.
See comment you replied to about “size” and “enterprise”. At no point did I comment on quality.
My comment was this thread is not the place for this discussion.
Would you buy a car with a big dick and balls for a logo, but you can pay extra to have it removed?
Have you ever seen corporate branded truck nuts? Because I have, and those companies paid to add it in.
There are plenty of small businesses that use “enterprise” as well, and have wonderfully descriptive forms like “small to medium enterprise” and my absolute favorite - “micro enterprise”, for organizations with (generally) under 10 people.
Again, I support there being a meta discussion about this so the community can have a consensus, but we aren’t doing that in this thread.
That was not the issue with tesseract or its dev, let’s be honest.
This is… beautifully without any soul or personality. Its so fitting.
I want to remind everyone to keep on topic. Disparaging people for whatever reason is not on topic.
If you see something problematic, please report rather than respond. Your comment in response will be nuked along with the original problem comment.
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.
All set thanks!
@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.