Thread:Talk:Extension default namespaces/What's the big deal?/reply

Agreed, this page has always only been a guide, never a rule. It's intended so that extensions adding new namespaces can try to collaborate and avoid forcing people to override default namespaces all the time because of extensions always overlapping. Every extension that defines a custom namespace should always have some method of configuring the extension to use different namespace numbers. And sites can define whatever manual namespace numbers they want and force extensions they install to use numbers that fit around that. The idea that 500-599 should be site specific is ridiculous even at a logical level... 1000+ would make more sense, 2000+ if we have to. Personally I have a site namespace of my own sitting at 112-113. Btw here Manual = 100, Extension = 102, API = 104. Frankly the 100-199 range has always made much more sense to me for site-specific namespaces. SMW is just an oddity which can have a config option set or we can just use the free ones around it.

Personally the thought that we should do away with this whole hardcoded namespace thing has been lingering in the back of my head for awhile. We really need some way for an extension to request a namespace on a first-come first-served basis such that after a number is reserved another extension will always get a different number even if the previous extension was uninstalled.