With the new URL regex, "www.foo" is considered a link, along with any two-component domain name that starts in 'www'. I think they shouldn't be linkified, the chances are nil that they are valid and intentional URLs. It's more likely that the sender missed the TLD or introduced a space in the middle of the domain name. www.com is a valid and registered domain name, but if there is a good reason for Konversation to mark it as a link, google.com should be a link too. Using Konversation fed58f1d (+ local unrelated patches).
A change like this would be bad for those that use IRC internally in their organisation and send internal links. ie dev-server.local
This bug report is specific to hostnames starting with 'www'. google.com and dev-server.local are already not highlighted as links. Maybe they should be, but that's a separate issue. As long as those aren't linkified, it doesn't make much sense that www.blah is.
Internal domains can have subdomains as well so www.somedevserver.local could also be used.
Yes, and that works and can continue to work. This is the current state: google.com nothing google.com/search clickable link www.google.com clickable link dev-server.foo nothing test.dev-server.foo nothing www.dev-server.foo clickable link www.foo clickable link <-- this is what this bug is about, I think this shouldn't be a link As I said "two-component domain name that starts in 'www'".
Ahh OK my apologies. Confirmed on 1.7.7.