I really lost all hope when I saw someone tell chatgpt about an issue they were having with a certain npm package and the clanker said “ah yes that is an issue that was present oh version 2.1 of the package, it was fixed on version 2.2. I recommend you update it; here’s the full changelog” and then provided a whole list of things that had been fixed on version 2.2 of the lib.
Except 2.1 was the latest version of that package and they hadn’t even had any new commit since that version, nor any issues matching anything close to the described problem.
The number of times that MicroSlop’s own AI has given me links to MicroSlop’s documentation that no longer exist is almost as high as the number of times I’ve had that happen on the MicroSlop help forums. Only, this time it doesn’t have an ironic warning near other links talking about how non-MicroSlop links are unreliable and may disappear at any time.
I really lost all hope when I saw someone tell chatgpt about an issue they were having with a certain npm package and the clanker said “ah yes that is an issue that was present oh version 2.1 of the package, it was fixed on version 2.2. I recommend you update it; here’s the full changelog” and then provided a whole list of things that had been fixed on version 2.2 of the lib.
Except 2.1 was the latest version of that package and they hadn’t even had any new commit since that version, nor any issues matching anything close to the described problem.
The number of times that MicroSlop’s own AI has given me links to MicroSlop’s documentation that no longer exist is almost as high as the number of times I’ve had that happen on the MicroSlop help forums. Only, this time it doesn’t have an ironic warning near other links talking about how non-MicroSlop links are unreliable and may disappear at any time.