They were removed from MAINTAINERS, which is what identifies the people responsible for maintaining a piece of code, a subsystem of Linux, not the credits, which is encoded in the git commit history.

A very similar situation to that analysed in this paper that was recently published. The quality of what is generated degrades significantly.

Although they mostly investigate replacing the data with ai generated data in each step, so I doubt the effect will be as pronounced in practice. Human writing will still be included and even curation of ai generated text by people can skew the distribution of the training data (as the process by these editors would inevitably do, as reasonable text could get through the cracks.)

Neat idea. This could be refined by adding a git hook that runs (rip)grep on the entire codebase and fails if anything is found upon commit may accomplish a similar result and stop the code from being committed entirely. Requires a bit more setup work on de developers end, though.

These models have so many parameters that, while insufficient to memorize all text it has ever seen, it can end up memorizing some of the content. It is the difference between being able to recall a random passage versus recalling the exact thing you need. Both allow you to spill content verbatim, but one is problematic while the other can be helpful.

There are techniques to allow it it ‘read on demand’, but they are not part of the core model (i.e. the autocmpletion model / LLM) and are tacked on top of it. For example, you can tie it search engine, which Microsoft’s copilot does, and is something which I don’t think is enabled for ChatGPT by default. Or allow it to query a external data bank (Retrieval Augmented Generation).

There is a difference with adding an instance and accessing it that way (via their API - bypassing the server you signed up on) and via federation using the server you signed up on. Only in the latter case can you vote using the account already registered.

Try using the search feature to access the community via federation (e.g. “!cats@lemmy.world”) rather than adding the instance directly.