Clarify "Ban" module replacement - support for contrib modules that require "Ban"?

Hi Julian, thanks for your interest in the module.
Advban is a sort of fork of the core Ban module and uses its own table.
Advban can be used by other modules, such as Perimeter, as a ban provider if they want to of course.

Thanks @goodboy - technically that would mean that these modules need to switch from ban to advban in their .info.yml right? Or could advban work on top of ban in the future, "hot-swapping" / overriding ban without the need to remove the ban dependency in the contrib modules? (That would be fabulous architecturally!)

@anybody, yes, that's right, modules should change module dependencies. Initially, advban was made as a fork, not an extension. Perhaps this was incorrect, but I wanted to be independent of the ban core module. However, ban is now considered obsolete and will be removed from the core in Drupal 12, so module developers will have to change the dependency anyway. In this sense, advban and ban are on the same level, so why not choose advban in this case?