@shaknais Good question. I think it is very much an unanswered question whether AI code assistants violate copyright licenses. If you care about free software, I think your options are to avoid AI code assistants or train your own models using only code with compatible FOSS licenses.

While some many in the were busy fussing about support the dying car industry, an industry of the past, they were letting EU companies die, although that's clearly the industry of the future.

politico.eu/article/europe-sol

And is dying anyway, despite bailouts and all that attention.

@IzzyOnDroid @fdroidorg A blanket ban harms more than it helps. There needs to be trust in maintainers. That's what FOSS is about. It is easy to spot AI slop in code.

For example, we get merge requests created with AI that are tightly focused. If we don't allow such things, we set ourselves up to be DDoSed by AI bots. They can spam a project with small, reasonable fixes that then cannot be merged when anything AI is banned. We'd have to do weird things to fix bugs just because of the ban

Riding on the Slovak national railways, I'm fascinated by the choice of an Australian accent for their English announcements. It makes my head spin a bit being in this very European context with an official Aussie telling us the local information 😉

@mjg59 I think the right answer is to retain copyright, prevent it expanding, and bring it back to something like a 30 year term and limited to concerns about commercial distribution.

Judge does a review of in 😂

theverge.com/policy/979852/tha

That is highly entertaining to read. Let's see if actually follows the direct orders from the judge. They are so lawyered up paid for with those sweet sweet , I imagine they'll still fight.

For me, there is still a big open question: should @fdroidorg add itself to Google Play? On one hand, we don't support anything proprietary, on the other, it makes it easy to install safely

Show more
image/svg+xml Librem Chat image/svg+xml