Removing plugins for non-existent websites

[DVD-DAVIDE]

Many of the websites that are supported do not exist anymore. Their domain isn't even registered (npm run check:sites). Should they be removed? Or are they being kept for compatibility or some other reason?

[Rojikku]

I asked this briefly before on discord, and was just told "We don't delete them."

Idea probably being the domain could come back?

Personally, I looked at mihon recently, which I neglect, and it has a bunch of plugins marked obsolete.
It would be nice to have an implementation like that, and remove dead stuff to prevent complaints - or at least mark it and filter it out automatically, if it's not.

[DVD-DAVIDE]

I see. They could be useful sometime in the future, could they not?

In that case, couldn't we just find a way so that the obsolete plugins cannot be installed (idk, maybe just don't compile them or whatever equivalent TS uses)?

[rajarsheechatterjee]

If you’re sure they no longer exist and won’t be coming back, we can remove them. That said, having an obsolete or down status would be useful.

[Rojikku]

If you’re sure they no longer exist and won’t be coming back, we can remove them. That said, having an obsolete or down status would be useful.

Realized .broken works pretty well.
We could just utilize that. None of the code has to vanish, but it doesn't clog up the plugin list, either.
Currently doesn't work with multisrc.

I could open a feature request for an Obsolete/Orphan status on the main app for plugins who don't have a corresponding ID in the repositories. Would be useful for users to realize why their plugin isn't getting updates, if they have an old one, or one from another source, installed.