RSS Feeds - Service Status

[#1]

I get RSS feeds from http://usertools.plus.net/status/status.xml and the links in the postings recently look like this a copy of the last announcement here -

http://snipurl.com/3m9c1'>http://snipurl.com/3m9c1 [usertools_plus_net]

First question - why are we now using snipurl
Second question - what is first part of the link for as it gives this result

Quote

404 Not Found Not Found Unfortunately, the page you requested (/status/archive/%3Ca%20href=) was not found on this server.

[#2]

Bob has probably already forgotten about the one from the User group  http://usertools.plus.net/quick_link/

[#3]

The problem with the link in the service status RSS feed, Usertools archive and email is known.
It relates to changes of the format on the service status pages on the portal, but despite being told several time it will be fixed, it hasn't.
The problem is a Usertools one.

[#4]

Quote from: Oldjim

First question - why are we now using snipurl

Why not? TBH, I personally started using it as it was easier. I have a browser button that automatically converts the current URL and copies it to my clipboard. We were using TinyURL before which is no different really.

Quote

Second question - what is first part of the link for as it gives this result Quote 404 Not Found Not Found Unfortunately, the page you requested (/status/archive/%3Ca%20href=) was not found on this server.

Not sure what you mean. If I browse to http://snipurl.com/3m9c1 I get a Service Status post. The reason the URL is mangled is because we made some code changes a while back to convert URLs to hyperlinks on the (portal) Service Status pages, and that's broken the Usertool's feed. I mentioned this to Colin the other day and he said he'd take a look at getting it fixed when he gets the chance.

[#5]

Quote from: Bob

Why not? TBH, I personally started using it as it was easier. I have a browser button that automatically converts the current URL and copies it to my clipboard. We were using TinyURL before which is no different really

Checking back on the postings from the end of August backwards I didn't see any tinyURL just the full code.

[#6]

<rant>I don't like SnipURL, TinyURL, or any other similar website. I like to know where a link is taking me before I click on it. When I see a TinyURL link, I have no idea where it's taking me. I see that you've started putting the website name in text afterwards, but why not just put the full URL in the first place?</rant>

[#7]

I've said on the PUG forums and I'll say it here. You should be using the quicklink facility on the Usertools site, e.g. http://users.plus.net/QL:C5FF71DE
The link is a Plusnet URL and I'm sure Rob and other people would be a lot more comfortable clicking one of those compared with a SnipURL or TinyURL link.
The facility to create quicklinks can be found here: http://usertools.plus.net/quick_link/

[#8]

Quote from: jelv

I've said on the PUG forums and I'll say it here. You should be using the quicklink facility on the Usertools site, e.g. http://users.plus.net/QL:C5FF71DE

Seems reasonable to me. I'll go with whatever people prefer. Was just a little easier for me to use snipurl. We'll start using the usertools link generator moving forwards.

[#9]

Is it just me or does the phrase "moving forwards" (as used in the previous post) annoy other people?
What exactly is supposed to be moving?
Why don't you use "from now on" or "in the future"
You have been infested with MarketingSpeak

[#10]

I try purposefully not to.
I'll have a word with Marketing Bob.

[#11]

I hope you touch base with him later and framework a paradigm shift.

[#12]

The broken links on the RSS/status feeds should now be fixed thanks to Colin.

[#13]

Quote from: geewizz

I hope you touch base with him later and framework a paradigm shift.

/chortle
B.

[#14]

Maybe I'm just being fussy, but I think that the quicklink facility on the Usertools site still has the same problems as TinyURL does. I still don't see what's wrong with using the actual URL.

[#15]

Often the links will be of such length that they would spread over more than two lines on http://www.plus.net/supportpages.html?a=2&?helpheader=servicestatus
Also, when people are receiving the postings by email they may be too long and be split by their email client meaning that they have to manually reconstruct them to follow the link. There were complaints in the past about this with people demanding that something like quicklink was used.