Yup, I'm posting another this week. Sorry.

This week I'm hoping we can wrangle a solution around AI and our selfhosted community. There are plenty of strong opinions (both pro and con), but one thing is for certain - there needs to be better disclosure in promo posts. Two options (that aren't mutually exclusive):

  • Any posts of an AI focused, AI Developed, etc software gets an [AI] tag. No, a [Not-AI] tag is not needed to accomplish this, thats kind of a "non-golfer" sort of tag.
  • Comment requiring an AI disclosure response to every promo post, if its not detailed in the post itself. Specifics (generating docs for commands, translation, whole-boat vibe-coded this app, etc) would be requested.

I will say that having disclosure and/or tagging would mean that comments that just say "slop" or "fuck ai" or whatever would be off topic at that point, that information is already provided, so its just noise (and sometimes pretty uncivil - I've been light on that for now due to the need for a rule on this).

The tag [AI] would make it easy to filter out (or search for, if that's your thing), but there is a wildly different degree of AI use out there, and from the posts with a positive score, its usually due to responsible AI use (translations, a snippet they had to do something obscure with, available to use with AI but doesn't require it, whatever), which is why I think the disclosure has a place as a benefit to everyone.

Please provide any input or alternative options on this, and I can then put it to a vote like the last one. Comments seem to be the best approach without involving something off-site, but if you have a better idea/option, please share.

top 83 comments

sorted by: hot top controversial new old
[–] 77 points 4 months ago* (2 children)

+1

Home-AI oriented channels like Reddit's localllama are filled with self promotion garbage, and more will trickle here over time.. I'm not even against self promo or heavy coding assistance, but 9-times-out-of-10, the linked repo is nonsense, or straight-up fraudulent. And being obviously vibe-coded is a common tell.

Good to get ahead of this.

Also, +1 on supressing driveby insults. If the post is tagged up front, there's no need. That being said, it should be okay for users to call out an obvious grift, or a "nonsense repo" that's actually pure slop.

  • source
  • hideshow 2 child comments
  • [–] 21 points 4 months ago

    That being said, it should be okay for users to call out an obvious grift, or a “nonsense repo” that’s actually pure slop.

    Especially if the disclosure is blatantly a lie, absolutely. I'd also say if you see any indicators that they are lying in the disclosure, its still worthy of reporting - but I would say report and separately message the "why", to limit visibility of seeing those indicators.

  • source
  • parent
  • [–] 18 points 4 months ago

    Not a fan of a tag, since it's not transparent enough. Sounds like every minor use of AI would warrant a tag, which seems past the point.

    The disclosure comment I feel works well. People that care about if/how AI was used can check it to get a proper impression of the scale of and workflow for AI usage, and those who don't care can ignore it.

  • source
  • [–] 20 points 4 months ago (3 children)

    I would still prefer an additional [Non-AI] tag. Even if people are arguing against it - it is not same omitting an [AI] tag and consciously saying "I never used and never will use AI". And the latter is the thing most users who want the AI-tag are looking for.

  • source
  • hideshow 3 child comments
  • [–] 10 points 4 months ago

    Same. It removes the ability to have plausible deniability of "oh I just forgot to tag it"—no, if you tagged it "non-AI" and it was actually vibe-coded, you clearly deliberately and consciously lied.

  • source
  • parent
  • [–] 10 points 4 months ago* (last edited 4 months ago)

    I really like having the disclosure comment pinned for a more nuanced explanation of what, if any, AI went into a project or post. I think just a tag can't capture the levels of AI use.

    I'm personally a never-genAI, but, unless we go No AI as a community, I don't think it makes sense to group all projects that touch AI for documentation with all that use it for testing with all that completely let the AI generate all their code, etc. And I don't think setting a threshold for which get tagged makes sense either. Basically, a tag is misleading no matter how it's implemented.

  • source
  • [–] 30 points 4 months ago (8 children)

    I want a community where people can use AI to help build a tool and be able to post about it here. But unfortunately, I’m just not seeing that. The AI-generated apps seem to be coupled to a drive-by, AI generated post (and comment replies) all full of em dashes and the standard Claude slop language.

    So, yes, mandate an AI tag. Hold posters to it and remove violators, because it seems to always be the same class of “contributors” that are cosplaying as software developers.

    Not sure if your rule changes are touching this, but the worst offenders I don’t want to see here are:

    • posting and commenting text written entirely by AI
    • not open sourcing or giving any visibility into their code
    • adopting a paid model

    The people doing that remind me of the people who would approach me 20 years ago saying “hey I have an idea for an app I want you to build and I’ll give you 5% of my company. It’s like Facebook for dogs, but I need you to sign an NDA before I say any more”.

  • source
  • hideshow 8 child comments
  • [–] 6 points 4 months ago (1 child)

    i agree with you. i have been working orofessionally as a software developer for over 27 years. i'll use ai to help research something but i cant atand low effort full ai projects being posted.

    i always saw non devs using ai to fully generate something for them personally to fix a very custom need but why do these people post projects thry honestly had no hand in.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 0 points 4 months ago

    Man it is great for creating custom apps to scratch your need. I have custom programs to filter out blocklists for one country and dynamically update firewall rules on unified gateways. Stuff that well never be put in as it would hurt their paid subscription.

  • source
  • parent
  • [–] [S] 4 points 4 months ago (1 child)

    The first bullet is, the other two are covered in the current rule 7 that just went live this week.

    While part of promo, this is just about its own item here. In part because it could be something like "I wrote some of this script, got some ai help to talk to this closed device, here's what I'm using" which doesn't really fit promo, but still garners a lot of negative attention and comments.

    I'm a bit hopeful this one would be of slightly broader benefit than just the straight up promo posts (which has a good amount of requirements now to filter out the garbage, though it does put some delays on f/loss projects that are well intentioned).

  • source
  • parent
  • hideshow 1 child comment
  • [–] -3 points 4 months ago (3 children)

    I want a community where people can use AI to help build a tool

    Sure, that's github

    and be able to post about it here

    Fine, but others including myself want that slop as far away from here as possible. Maybe start another community? I suggest calling it c/vibehosted.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 9 points 4 months ago* (2 children)

    Fine, but others including myself want that slop as far away from here as possible

    And there are people like me who are fine with moderate AI use and would rather judge the project themselves rather than have them rejected outright.

    Maybe there should be a community poll

  • source
  • parent
  • hideshow 2 child comments
  • [–] -1 points 4 months ago (1 child)

    Why a vote to switch up an existing community? The admins have proposed the [AI] tag to mitigate slop projects.

    You said you wanted a community to post vibe coded projects, go ahead and set it up. I don't see why it needs to be foisted onto c/self hosted, unless you have some vested interest in boosting sloppy mcslopface projects.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 6 points 4 months ago

    I'm not sure I understand. First off I'm not the same person as GP. Second, the admins are proposing an AI tag, which I'm supportive of. I'm just saying that I am OK with AI-assisted projects being posted to this community (with the AI tag of course)

  • source
  • parent
  • [–] 35 points 4 months ago (5 children)

    I don't have a problem with AI. I have a problem with vibe-coded apps released as a one-shot and then never maintained or supported. That's slop.

    I also have a problem with the trace apps (lifttrace, nutritrace, etc.) because while they're entirely vibe-coded, they are actively developed, but they're posted here by a brand promotion account that doesn't otherwise contribute to the community. If there's any "x% self-ptomotion" threshold, they fail it, because it's 100% self-promotion.

    I know I also reported another post as slop recently but I don't remember what it was.

  • source
  • hideshow 5 child comments
  • [–] 11 points 4 months ago (3 children)

    Yeah. Abandonware isn’t cool generally

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 4 months ago (2 children)

    Honest question intended to spark discussion.

    Does this mean that all “single developer” projects can be considered abandonware (that aren’t open source/forkable)?

    Or really “all” non open source software really. Companies “can” die.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 4 months ago (1 child)

    IMO, abandonware means software that is a dead-end upon its very release, with no hopes or plans for anyone to every build upon it. Abandonware is generally not extensible, follows no good design philosophy that would let someone else build it up, and embodies essentially nothing.

    Even a 100-line throwaway Python script has more utility to someone when it is published on PasteBin or whatever. But something like a binary executable released with no source code, with no support, and with no intent by the developer to ever make anything more of it, that's abandonware.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 8 points 4 months ago

    Sounds like a good solution for me. I think most users dislike completely vibe coded apps, not ai supported apps. So maybe we should be more specific here.

    For example: [Vibe-Coded]

    This would also support new users finding the right tag.

  • source
  • [–] 7 points 4 months ago*

    Personally. I want an AI tag so I know to look more carefully.

    I don't mind AI speeding up a skilled engineer.

    But I do mind a crypto bro, turned AI bro, with little experience, too eagerly advertising their vibe coded app.

    Its too exhausting to audit everything I may be interested in and the AI tag would help me to budget and optimize my time.

  • source
  • [–] 7 points 4 months ago* (14 children)

    Also:

    Anything with an [AI] tag, first thing in the title, will have a drive-by downvote issue.

    Not sure how to deal with that, or if its even a concern.


    EDIT:

    Maybe it should be something else that's not such a loaded keyword?

    [ML] for Machine Learning? [SAI]? [LAI]?

    I've been messing with 'AI' for a decade, and even I hate what the term has come to represent.

  • source
  • hideshow 14 child comments
  • [–] [S] 4 points 4 months ago (12 children)

    Oh I'm sure it will be. I don't know if its a concern though - TBD I suppose.

  • source
  • parent
  • hideshow 12 child comments
  • [–] 8 points 4 months ago* (11 children)

    TBD indeed. But it will effectively 'downrank' posts and their visibility, maybe into the negative vote range. I've seen highly negative scores across the board in more machine-learning focused subs, and that's without a tag that catches the eye so easily.

    I think even modifying the acronym could make a difference, though (as I ninja edited).

  • source
  • parent
  • hideshow 11 child comments
  • [–] [S] 4 points 4 months ago (10 children)

    I do like the idea of a different tag, still easy to filter but less of a target like the ai generated communities out there.

  • source
  • parent
  • hideshow 10 child comments
  • [–] 2 points 4 months ago* (8 children)

    For what it's worth, I asked my self-hosted LLM (MiMo 2.5, no network access outside my desktop), and it came with [AIT] (AI-Topic).

    ...I think that's my favorite so far. [AIP] would work too.

    I feel like that "obfuscates" the tag enough to blunt impulse downvotes in /new and feeds, without being deceptive or anything.

  • source
  • parent
  • hideshow 8 child comments
  • [–] [S] 3 points 4 months ago (6 children)

    Actually both are pretty good - AIT for it as a more discussion oriented, AIP for a project post.

    I like it, I think something like that would be a great idea

  • source
  • parent
  • hideshow 6 child comments
  • [–] 3 points 4 months ago*

    Oh, both! Yeah. I didn't even think of that, but [AIT]/[AIP] as separate tags makes a lot of sense.

    I'd like being able to filter by either, actually.

    I guess two tags runs the risk of "rules too complex for some to follow," but that's more of a moderation load question. I have no say in that, heh.

  • source
  • parent
  • [–] 2 points 4 months ago (4 children)

    Where should the line be drawn for what is AI coded vs AS assisted (in some manner) and thus tagged?

    XerahS is very openly coded with AI and should be tagged. But what about the recent debate about the use of LLM in cURL?

  • source
  • parent
  • hideshow 4 child comments
  • [–] [S] 1 point 4 months ago (3 children)

    So thats one of the questions that will need to go to a poll, but if I were to give my opinion it would be that any use would mean a tag, and the disclosure area is where it can be detailed.

    Otherwise we'd end up with a bajillion differing tags, so a disclosure section makes more sense.

    Not tagging for assisted would also mean setting arbitrary lines, and would be way too subjective imo.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 4 months ago (2 children)

    any use would mean a tag

    So when I write code, I regularly ask an LLM how to do things. A few examples from my history is how I could overlap rows when generating PDF files (have a library for this), how I could assign an empty Char and to create a singleton class. A LLM never changes any of my files, I use it as super-search-engine.

    Would that constitute an AI tag?

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 2 points 4 months ago (1 child)

    Yes, because it is a bit different than a search engine. It may not be changing the files, but it is telling you the way to do it. It might give you an outdated method/pattern, it might ignore conventions, and most importantly, it doesn't really understand the problem its solving. Its not finding the optimal answer, its finding the most common.

    So the resulting answer may work, but not necessarily be right. In a disclosure (see the new thread) that would be referred to as "hint" for lllm use.

    That doesn't mean the answer you got was necessarily wrong either, just an answer based on an amalgam of the most common for all the code fed into the model, no matter when the code was written.

    It would be put into an ai disclosure, so it qualifies for a tag. Make sense?

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (-1 replies)
  • [–] -1 points 4 months ago

    Maybe it should be something else that’s not such a loaded keyword?

    Yes, since "AI" doesn't exist, maybe we should use more accurate terminology. That would certainly deter those who don't believe in the imaginary grift in "AI".

  • source
  • parent
  • [–] 6 points 4 months ago

    Yep. It is a time-suck to see an interesting new project only to check it out and find out it's AI slop. For some apps, it doesn't bother me... They may not require the access or stability of critical apps. Other times, I just can't trust a slop app, and it would be very helpful to know which it is in advance.

  • source
  • [–] 6 points 4 months ago

    Thanks for grappling with this @curbstickle@anarchist.nexus

  • source
  • [–] 6 points 4 months ago (3 children)

    I think this should be a thing. At the same time, I would also want something similar for funding or platforming fascists, but that is unlikely to end up being done. I think a simple tag, the [AI] one would work, is the best current solution. I think extra detail in the post is a good thing to do, for example AI assisted documentation, AI assisted bug finding, AI assisted vibe coding. They are all different and have different effects on the product and community. If someone uses AI to find bugs in their own code I am all for it, that is a great use if it. If they use AI to write their login system I am not keen at all given the likelihood of intense security issues and the low likelihood that they will ever fix it.

  • source
  • hideshow 3 child comments
  • [–] 11 points 4 months ago (11 children)

    I like the AI tag idea. I'm someone who has what I'd call a noderate approach to AI, not an AI bro but any means but I'm also okay with some things built with AI if they're done with care. If others don't want to see it, fine, then that's what a tag could be useful with. However the fuck AI/slop comments on something that admits to being AI is annoying to me. (We know it's AI, they literally said it is).

    If it becomes too much content, then yes would be okay with bi-forcating the community, buy only after it becomes a problem.

  • source
  • hideshow 11 child comments
  • [–] 10 points 4 months ago* (last edited 4 months ago) (10 children)

    I'm not consistent about it yet, but because of exactly this, I'm trying to differentiate the two when I talk.

    Responsible automation? I use ML or machine learning.

    The grift consuming the world? A Tech Bro? "AI"

    I think one of the saddest things is the conflation between the two, like you can't even talk about one without invoking the other. Or it opening up that whole ethical debate, when you're just talking about, like, a 100M transcription model trained by one research in some university on a potato.

  • source
  • parent
  • hideshow 10 child comments
  • [–] 2 points 4 months ago (9 children)

    Yeah it's heresy on Lemmy, but I do find it genuinely useful. My only regret is that I have to use Claude/Anthropic more than I'd like, which is why I have a vested interest in selfhosting myself. I'd rather figure out how to run the larger models myself and cut them off completely, but you even begin to mention that here and you'll get downvoted to hell.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 3 points 4 months ago* (last edited 4 months ago) (8 children)

    You don’t even need Claude anymore. GLM 5.2 API is good enough for 95% of the same things and vastly cheaper.

    MiMo 2.5 Pro and Kimi are also very good. And then there’s Cerebras API if you just want simple things done quick.

    The thing with self hosting, while awesome, is that it requires a lot of hardware and considerable time investment for what’s essentially a “base tier model,” or at best one step down for what’s still a very cheap API. I still love it, especially the privacy and control aspect, but you aren’t running Claude at home unless you’ve got a threadripper or server hardware collecting dust.

    …Hence I can understand why people don’t pursue it. Especially since a cursory Google search will lead you to trying the Deepseek distillation on Ollama (which is awful).

  • source
  • parent
  • hideshow 8 child comments
  • [+] 2 points 4 months ago* (last edited 1 month ago) (2 children)
  • [–] 2 points 4 months ago* (1 child)

    All while hiding any attribution to the underlying engine, just to start:

    https://sleepingrobots.com/dreams/stop-using-ollama/

    And that article isn’t comprehensive. A book could be written on damage and drama they’ve caused.

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (-1 replies)
  • [–] 1 point 4 months ago (5 children)

    That's where I am okay with hardware, but can't seem to fit the models on my 3090. I have dreams of something like an A100 someday, but not until there's a ton of used ones that hit the market. What do you use for your hardware?

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 4 months ago* (last edited 4 months ago) (4 children)

    I have a single 3090!

    That's the dream GPU, these days.

    And I have 128GB CPU RAM. So the best model I can run is MiMo 2.5 (a 300B model) at around 10 tokens/sec, using hybrid CPU inference.

    ...But that's the worst-case scenario, for speed. It's an IQ3_KT quant (a high quality "trellis" quantization type, but very slow on CPU), with a gigantic model that barely fits in my RAM+VRAM combined, with no DFlash or any kind of speculative decoding turned on. I could tune it to be much faster, but I mostly just want "max quality, fast enough to read as it streams, barely fits in memory" for this model.

    For speed, or prompts with lots of thinking or context (like agenic use), I just run Qwen 3.6 27B now. That would fit in your 3090 no matter how much CPU RAM you have, but you have to be smart about the backend and quantization you pick. If you just use Ollama, it's gonna tell you it won't fit, or use some horrible default that spits out garbage.


    ...This is what I meant to emphasize.

    It's not just the hardware. You kinda have to be part developer, part enthusiast to even follow this stuff, it up optimally, and keep it up-to-date. If you just try to Google "best LLM for 3090," you will get absolute garbage.

  • source
  • parent
  • hideshow 4 child comments
  • [+] 2 points 4 months ago* (last edited 1 month ago) (2 children)
  • [–] 2 points 4 months ago* (last edited 4 months ago) (1 child)

    It’s drops off, but not as much as you’d think.

    MiMo uses 5:1 SWA, so its long-context compute doesn’t increase as catastrophically as older models. That, and most of the “slowness” comes from the MoE layers being on CPU (whereas the attention layers that get heavier at high context are all on the 3090).

    That’s the beauty of these MoEs: they’re just the right size for the “compute-lite” parts to stay in CPU RAM.

    I will measure it tomorrow. It is a constant ~9-10TPS for short queries, but definitely slower near my current max context of 85K.


    And do you mean prompt compaction? I don’t automate that; when I use that particular model, I tend to use it in Mikupad, aka “raw” notepad mode, and manipulate the context directly. This is so I can do things like chop out conversations, pick different tokens from the logprobs, or edit its own replies/thinking and continue mid reply.

    I like manually handling this because, being a local model, prompts are cached. Streaming starts quickly if most of the prompt stays cached, which is actually a really nice advantage over APIs.

  • source
  • parent
  • hideshow 1 child comment
  • [+] 2 points 4 months ago* (last edited 1 month ago) (1 child)
  • [–] 3 points 4 months ago* (last edited 4 months ago)

    They 100% do. They’re probably serving “naive” FP8 via VLLM, which is worse than you’d think, especially if they flip on the awful FP8 KV cache.


    In a local quant, you can stop quantized models from falling apart at higher CTX by leaving the attention heads at a higher quantization. As an example, with MiMo 2.5, I have all the MoE MLP layers at IQ3_KT, the dense experts at Q6K, but all the attention layers at Q8_0.

    For Qwen 27B, I’m still experimenting, but leaning towards IQ4_KT for the MLPs, Q6K for attention, and Q8_0 for the small, very sensitive KV heads. Or a similar scheme as an exl3 quant.


    That being said, sometimes even unquantized models fall apart in certain long context scenarios because the max advertised context is a lie. You just have to test them and see, but Qwen has certainly done this in the past.

  • source
  • parent
  • load more comments (-1 replies)
  • [–] 1 point 4 months ago (1 child)

    I'll have to play around with mine then, because I've had not great luck with it, or at least very disappointing. The CPU offloading is fairly slow, but maybe I should try tweaking more

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (-1 replies)
  • load more comments (-1 replies)
  • [–] 10 points 4 months ago

    I think tags are a good idea. I would change the tag to [AI / LLM], and maybe some subtags like [chatbot], [image processing], etc. AI is here to stay, or a least until the US realize the hole under their entire economy (Or both in worst case scenerio) , so regulation is a good solution to this. (In my humble opinion)

  • source
  • [–] 9 points 4 months ago* (1 child)

    My 2 cents are that the issue is promotion not AI, if people started promoting stuff made without AI that would still be spam.

    From the rules:

    F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, your post is exempt from the 10% requirement. The exception does not exempt you from the account age requirement.

    I would propose making this the requirement and not an exception, forbid all promotion of closed source, and allow the 10% requirement for open source projects.

  • source
  • hideshow 1 child comment
  • [–] 4 points 4 months ago* (last edited 4 months ago) (1 child)

    Yes this is needed. Thank you for the proposal here.

    I would suggest that this probably needs to be really explicit about any AI involvement, i.e. a minimum if AI is used in any capacity in the coding process, it should require the tag. And ideally an explanation if it was used in other parts of the process.

    That last post that came up said they used AI 'for code review only'. In my mind even that deserves the tag, because these terms are so easy to work around. Someone can 'code up' the following:

    #include <studio.h> int main(void) { printf("Program that does X thing"); }

    (yes, I know the main arguments are not written correctly. You get the point)

    and then have the AI reviewer 'fix' their code by doing all the actual work. A strict requirement for this tag, for any AI involvement in the creation of the code seems like the key. The code part is going to be where the security issues crop up, and where it's really important to know who or what is producing the code you're about to run on your home server.

    I think we're fairly used to a world where people use templates for their websites, documentation, etc. AI use there bothers me less, but an honest disclaimer saying what the AI did would sure go a long way to reducing the hate comments. I think people will still drive-by downvote, but that can't (and IMO really shouldn't be) prevented. But without a rule, people aren't going to be honest.

    The scary part is just how emboldened people feel nowadays to just entirely use an AI for all the coding, documentation, website, and then not even put their name on the project. These to me feel like borderline state actor trojan horses disguised as open-source projects.

    Legitimate open source developers can spend years writing code to do something very sinplle but useful, and for them to be drowned out by a bunch of completely AI driven, slop posts really bothers me.

  • source
  • hideshow 1 child comment
  • [+] 1 point 4 months ago* (last edited 1 month ago) (1 child)
  • [–] 1 point 4 months ago*

    "This report draws on a survey conducted online by Wakefield Research on behalf of GitHub from February 26, 2024 through March 18, 2024 among 2,000 non-student, enterprise respondents in the U.S., Brazil, India, and Germany who are not managers and work at companies with 1,000-plus employees."

    I generally want to use smaller FOSS projects, and honestly dont care what tools enterprise companies are making their employees use. But I have college age children and know its being mandated there as well. Though it doesnt mean they have to use it in their own projects.

    As was discussed in precious slop threads, these projects are fairly easy to identify when they get posted here, today. Sure in a year that wont be as easy, but its clear from the downvotes thrown at projects since this rule was proposed that many people here just dont want AI-written running in their self hosted systems.

  • source
  • parent
  • load more comments (-1 replies)
    [–] 4 points 4 months ago

    I will say that having disclosure and/or tagging would mean that comments that just say “slop” or “fuck ai” or whatever would be off topic at that point, that information is already provided, so its just noise (and sometimes pretty uncivil - I’ve been light on that for now due to the need for a rule on this).

    The drive by down voting doesn't bother me at all. I sense that it does intimidate quite a few here. To me it's pretty darn silly because it's no longer a filtration mechanism as it was once intended, and now has become a way to vent displeasure, angst, and inner turmoil. However, it is what it is. I can deal with that with ease.

    The curb stomping is really the issue to me. I realize there are 8.4 billion other people on this planet and few will align with all of my core beliefs and convictions, which I see as a positive; yaaay diversity! I'm willing to give the space to agree-to-disagree and still be cordial and supportive where it's needed. (eg: the *arr stack) All I want to do is hang out with selfhosters, learn from them, and share with others what little knowledge I've gained along the way. I have no other agenda.

    I agree with the [AI] tag. I'm not really sure why that would trigger someone more than [SOLVED], and I agree with the 30 days in the hole. Two weeks would have sufficed imho, but 30 is fine.

    Thanks @curbstickle@anarchist.nexus

  • source
  • [–] 9 points 4 months ago* (3 children)

    I will say that having disclosure and/or tagging would mean that comments that just say "slop" or "fuck ai" or whatever would be off topic at that point, that information is already provided, so its just noise (and sometimes pretty uncivil - I've been light on that for now due to the need for a rule on this).

    good idea

    it won't solve the "noise" problem though. I was relatively active on !imageai@sh.itjust.works and we were constantly nagged by sloppies even though the community is clearly dedicated to generativeArt

  • source
  • hideshow 3 child comments
  • [–] 0 points 4 months ago* (1 child)

    it won’t solve the “noise” problem though. I was relatively active on !imageai@sh.itjust.works and we were constantly nagged by sloppies even though the community is clearly dedicated to generativeArt

    Maybe y'all would get less hate if the sub was called "generativeArt" instead of grifterly claiming to be "AI".

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 4 months ago (1 child)

    If you don't delineate, it will simply be easier to tag everything ai as there was ai involved somewhere and you're less likely to need to defend yourself.

  • source
  • hideshow 1 child comment
  • [–] 4 points 4 months ago

    I agree, there's valid points on both sides, let's be civil and request posts are tagged accordingly so that they can be filtered.

    Respectful coexistance, is the path forward.

  • source
  • [–] 2 points 3 weeks ago (3 children)

    We don't have a rule for that yet, but what's your stance on Llams posting to our community? Undisclosed even? https://lemmy.world/comment/26392175

  • source
  • hideshow 3 child comments
  • [–] [S] 2 points 3 weeks ago (2 children)

    Lemmy.world does, specifically for bots. They have to be set as a bot in profile and request permission first from the community.

    I banned yesterday and all of their comments should have been deleted as well, I'll check into that.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 3 weeks ago (1 child)
  • [–] [S] 2 points 3 weeks ago*

    Ugh they just made new ones.

    Yesterday was _cafe, today was _sh (for shitjustworks) and _lw for Lemmy.world.

    Please keep on reporting when you see it and I'll get to them as soon as I can.


    For the record, the Lemmy.world TOS requires that any bot account be set as such in their profile, and that any community they post to requires mod approval first.

    Generically speaking, I won't be approving any. What I mean is any bot request is going to need a valid and real reason for its use here, which I would then bring to the community to make that choice like I did for this discussion thread. I wish there were a better way than a basic upvote or downvote system, but its what we've got so its what I'd use.

    I have not posted about any new bots since I took over here a few months ago, so no new bots should be considered as having community approval.

    The acronyms and initialisms bot (can't remember the name right now) was approved before I joined and everyone seems cool with, I never get reports, so I haven't bothered with posting about it.

    Edit: WHY IS AUTOCORRECT CHANGING 'BOT'. So annoying. Anyway, fixed.

  • source
  • parent
  • [–] 5 points 4 months ago

    i want a community where AI is not tolerated at all. ai is a corporate grift and there's no room for it in a self built community founded on resistance of the tech status quo

  • source
  • load more comments
    view more: next ›