>>44602
The problem is a bit involved to explain, but I'll try:
The way the current website works is that certain features are divided up into modules. So for example, the chan is one module, the blog is another, etc. This also counts for authentication and user management. So there's a separate module that cares about handling login and so on.
Each module has its own subdomain on the server (*chan*.tymoon.eu, *blog*.tymoon.eu, *auth*.tymoon.eu, etc). However, which subdomain a module chooses is not strictly specified. So, depending on what kind of login/authentication module you use, the subdomain for that could be different, so the login page could be somewhere entirely different.
In order for the chan to offer a link to the login page it has to know what that URL is. It obviously knows its own URLs, so it can link to its own stuff, but it cannot (currently) know where anything of any other module is, so it can't link to it. The problem becomes even more complicated when you take into account that routing might remap URLs to something completely different.
Offering some kind of mechanism by which modules can access other module's resources and resolve them is something that I haven't figured out yet and I've thought about it for quite a while without coming up with a good solution. Obviously I could just make a kludge and write the static URL into the link that is only valid for tymoon.eu, but I don't want to do that because it wouldn't work for any site other than ours.