MoinMoin does not recognize all URI schemes
If you make one of the new xmpp URIs for instance like:
MoinMoin makes a mailto link out of it. Ok, most browser will not handle XMPP/Jabber URIs right now, but I would consider it a good idea to rather forward this as is to the device/browser, so
xmpp://tpfennig@gmail.com
I like to discuss another approach to URIs in MoinMoin. -- ThiloPfennig 2006-11-24 18:50:13
Consider this:
- If you edit a HTML page and do an experimental URL scheme your browser ALWAYS gets this information
If you do this in MoinMoin you only get links that MoinMoin recognizes or
- that you have configured
Suggestion
Rather than recognizing URIs MoinMoin should pass through all URI-Schemes, so everything that follows a scheme like defined in RFC 3986 -Uniform Resource Identifier (URI): Generic Syntax.
This would allow people to put all kind of standard or non-standard URIs in a wiki. Interpreting XMPP URIs as emails is just plain wrong. Maybe we can make this new bewhaviour optional via configs and call this rfc3986-compliant? So than we could make patch(es) that do various things to make MoinMoin behave like this RFC suggests?
I think the suggestion to add EVERY URI that comes through my mind to the config is not a good way, because the content is user specific and I do not want to tell my users which URIs are legal and which are not. The interpretation of an URI should be more the task of the user client.
The problem is that generic uri syntax is a not very specific scheme:something - so you should know at least what schemes you search for to avoid all sorts of misdetection like in "my favourite penguin:tux" (this is not a URI with scheme "penguin" with path "tux", but just a missing blank). This is different from html where you explicitely state href="...".
Well ok, but then one can at least try to find a good regex. Spaces are not valid. See also RFC 2396.
XMPP link should be like mail links
for example:
xmpp:tpfennig@gmail.com
and NOT
xmpp://tpfennig@gmail.com