@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
Timeline
Post
Remote status
Context
4
@SuperDicq @hj Pleroma backend is slopware according to their definition. Don't tell anybody. *shush*
@SuperDicq @hj Pleroma backend doesn't explicitly forbid LLM assisted contributions. Which is enough to be on that list as you can see in the social media table. Can't speak for frontend since that is mostly hj's realm. And besides that, there are some small chunks of LLM code in the backend already.
The reason why GTS is the only alternative is because they explicitly refuse contributions if they were in any way done with LLMs.
The reason why GTS is the only alternative is because they explicitly refuse contributions if they were in any way done with LLMs.
@phnt @SuperDicq @hj they should add iceshrimp.net and snac2 to the list then, listing gotosocial as a misskey alternative is a joke
Replies
6@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