This looks like a legitimate bug to me. In the meantime, what about using something like bit.ly?

tamhanna wrote:

This looks like a legitimate bug to me. In the meantime, what about using something like bit.ly?

That would do as a temporary workaround

And with that, the problem is solved.

This lesson served me well while coding Symbian, so ;)

Problem is not solved with bit.ly. There are number of people who don’t like url shorteners, because they don’t know where they will be after redirect.

Hi Denis,
I fully agree. But it is a workable solution for now ;)

tamhanna wrote:

Hi Denis, I fully agree. But it is a workable solution for now ;)

Yes a temporary workaround, until it gets fixed

tamhanna wrote:

Hi Denis,
I fully agree. But it is a workable solution for now ;)

And please don’t reply to my posts with a ‘yes’ or ‘i agree’.

I’ve created bug report QTWEBSITE-119 [bugreports.qt.nokia.com] for this bug.

I just voted on the issue.

xsacha wrote:

Hardly. A wiki could never run with external websites listed with URL shorteners.
People want to know where to go. It’s not really workable. I wouldn’t put a site on the wiki with a shortener.

And please don’t reply to my posts with a ‘yes’ or ‘i agree’.

No point in posting I Agree in response to something I don’t agree on. I don’t see shorteners as as dangerous as you perceive them to be.

tamhanna, they are dangerous, because you don’t know what will be after redirect. Maybe url was posted by spamer and you will go to virused site instead of going to news site. Url shorteners are of course good thing but only in some cases (like twitter).

Hello,
well, this is an issue of course. But on Twitter, you also don’t know who posted it…

(IMHO: there must be an URL shortener which shows the URL target before it forwards you there)

This is not twitter. And I would not follow links of URL shorteners. Let alone that they are cumbersome to create.

Hello,
ok, I admit that they are a bit cumbersome to create. But for now, it is the only solution we have.

Thanks, I’ll follow it up on the bug report Volker created.

mariusg wrote:

Thanks, I’ll follow it up on the bug report Volker created.

mariusg,

This is yet another thread for which I didn’t receive any email notification.