oh, it is the plugin Sample I am wondering why need 'main' for $m->connect() I want to the urel htpp://domain/hello instead of htpp://domain/main/hello go to HelloAction
The reason main is there is because it restricts the username registration less. For example, on your site now you can't have a user called 'hello' because their profile will be unreachable.
By putting things under main, you haven't placed any more restrictions on usernames. That's why a lot of the default actions are placed under there, like login, logout, subscribe, block, etc.
I find TwitterBridge plugin use hook onRouterInitialized instead of StartInitializeRouter, however the path 'twitter/authorization' is not under 'main', and I checked that 'twitter' could not be registered as a nickname.
Does StatusNet have a default nickname blacklist? and where is it?
Comments
I am wondering why need 'main' for $m->connect()
I want to the urel htpp://domain/hello instead of htpp://domain/main/hello go to HelloAction
For example, on your site now you can't have a user called 'hello' because their profile will be unreachable.
By putting things under main, you haven't placed any more restrictions on usernames.
That's why a lot of the default actions are placed under there, like login, logout, subscribe, block, etc.
If you must have /hello instead of /main/hello, hook StartInitializeRouter instead, and your pattern will be first.
Does StatusNet have a default nickname blacklist? and where is it?
---------------------------TwitterBridgePlugin -------------------------------
function onRouterInitialized($m)
{
$m->connect('twitter/authorization',
array('action' => 'twitterauthorization'));
$m->connect('settings/twitter', array('action' => 'twittersettings'));
$m->connect('main/twitterlogin', array('action' => 'twitterlogin'));
return true;
}
-------------------------------------