@hj@shigusegubu.club I would get on this if I were you and get Pleroma added as the alternative instead of GoToSocial. https://codeberg.org/small-hack/open-slopware#social-media
Post
Remote status
Context
3The reason why GTS is the only alternative is because they explicitly refuse contributions if they were in any way done with LLMs.
Replies
8@phnt @SuperDicq @hj they should add iceshrimp.net and snac2 to the list then, listing gotosocial as a misskey alternative is a joke
@mkljczk@pl.fediverse.pl @phnt@fluffytail.org @hj@shigusegubu.club They seem to have a very biased preference for projects who are explicit and vocal about excluding LLMs.
@SuperDicq @hj @phnt that’s why i mentioned two projects with explicit ‘AI’ policy
@SuperDicq @hj @phnt someone should start drafting AI_POLICY.md in pleroma-meta so there's a chance it gets merged in 10 years
@mkljczk@pl.fediverse.pl @hj@shigusegubu.club @phnt@fluffytail.org I honestly think there's no need to write an "AI Policy".
If you submit a pull request and it is slop code, you're not going to merge it. That's basic fucking common sense and that shouldn't have to be a "policy".
@SuperDicq @hj @phnt wow open-slopware repo doesn't have LLM policy so i can just ask copilot to add them
@phnt@fluffytail.org @hj@shigusegubu.club Yeah I personally do not subscribe to this definition of "slopware".
I don't see an issue with small sections of code (that you would otherwise copy from stackoverflow) being generated by LLMs.
As long as the LLM code is properly understood and verified by humans it will not make a difference if a human wrote it without LLM assistance.
Still don't want to encourage people to use LLMs for software development yet though, as they are all still very much proprietary.
I would consider projects to be "slopware", when developers are just generating code and not even actively trying to understand the output, and just pushing it as long as it "works".