> But isn't the entire "fb_social" namespace within the "fb" namespace?
Yes, but that's the edge-case for which no solution exists. There are various node_* or views_* or user_* modules, which all have to make sure that none of them unintentionally breaks the functionality of the "parent" namespace. That said, "fb_social" is only able to break the "fb" namespace in case "fb" implements stuff that starts with "fb_social". Sounds rather unlikely to me, but I also don't know your code. In any case, this namespace conflict sounds easily resolvable through a gentle agreement of both maintainers. sun
