<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Priocept</title>
	<atom:link href="http://priocept.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://priocept.com</link>
	<description>internet technology consultants</description>
	<lastBuildDate>Mon, 13 Feb 2012 19:27:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Why Twitter Links are Broken</title>
		<link>http://priocept.com/2012/02/09/why-twitter-links-are-broken/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=why-twitter-links-are-broken</link>
		<comments>http://priocept.com/2012/02/09/why-twitter-links-are-broken/#comments</comments>
		<pubDate>Thu, 09 Feb 2012 14:08:22 +0000</pubDate>
		<dc:creator>David Lampkin</dc:creator>
				<category><![CDATA[Other]]></category>

		<guid isPermaLink="false">http://priocept.com/?p=2482</guid>
		<description><![CDATA[It is well known that Twitter enforces a maximum size of 140 characters per tweet. This lead to the adoption of link shortening services as a workaround for posting tweets containing long links, which worked OK until Twitter implemented their own "t.co" link shortening which is a not-very-good copy of a workaround that was not ideal in the first place.]]></description>
			<content:encoded><![CDATA[<p>It is well known that Twitter enforces a maximum size of 140 characters per tweet. While completely arbitrary (originally chosen for SMS compatibility), this limit is part of the charm, identity and appealing simplicity of the service (ignoring those that choose to annoyingly tweet long paragraphs as multiple tweets).</p>
<p>But Twitter also doesn&#8217;t have any concept of structured data or attachments associated with a tweet, which means that links have to be posted in the body of the tweet content. Aside from causing ugly looking content, this also causes a problem with long URLs that use up most of the 140 characters.</p>
<p>Twitter originally left the solution to this problem (shortening of links via an intermediary link) to third party services like <a href="http://tinyurl.com/">http://tinyurl.com/</a> (and then <a href="http://bit.ly/">http://bit.ly/</a> for those desperate to save another four characters).</p>
<p>However, more recently Twitter implemented its own link shortening service that converts all links to the form <em>http://t.co/abcdefgh</em>.  Twitter describes this new service as follows &#8211; <a href="http://t.co/"><em>&#8220;Twitter uses the t.co domain as part of a service to protect users from harmful activity, to provide value for the developer ecosystem, and as a quality signal for surfacing relevant, interesting Tweets.&#8221;</em></a> &#8211; whatever that means.</p>
<p><strong>Here&#8217;s why this t.co approach is completely broken:</strong></p>
<ol>
<li>First of all, link shortening is now not only automatic but is also enforced &#8211; you can no longer insert a link that is NOT shortened. This doesn&#8217;t make sense and <a href="http://support.twitter.com/entries/109623">Twitter&#8217;s rationale</a> is weak, but by enforcing link shortening it just magnifies the impact of all the related issues that follow below.</li>
<li>&#8220;Shortened&#8221; links can actually get longer (<em>&#8220;visit priocept.com&#8221;</em> becomes <em>&#8220;visit http://t.co/abcdefgh&#8221;</em> which increases the link size from 12 to 20 characters!).  Twitter originally only implemented link shortening on links of <a href="https://dev.twitter.com/discussions/1062">19 characters or longer</a>.  But now they just <a href="http://support.twitter.com/articles/78124">&#8220;shorten&#8221; everything regardless</a>.</li>
<li>Shortened links also means that references to brand names that look like web addresses get messed up and the brand name is lost, for example the tweet &#8220;I just checked out brandname.co.uk &#8211; great site&#8221; becomes &#8220;I just checked out http://t.co/abcdefgh &#8211; great site&#8221; which loses all its context and actually loses all value completely if you are offline and can&#8217;t click the link to find out where the link goes to. If you have a company name that ends in .com then you&#8217;ll have to put it in quotes every time or Twitter is going to strip your company name out!  <a href="http://support.twitter.com/articles/78124">Twitter claim that the original link will still be shown</a>, but this doesn&#8217;t apply if you are viewing the tweet from a third-party application that doesn&#8217;t implement the &#8220;unshortening&#8221; process.</li>
<li>The reliance on the .co top level domain (assigned to the Republic of Colombia) is also very strange and unwise. Here we have a key piece of internet infrastructure used by millions and it relies on a domain run by Colombia? Who could presumably switch off the t.co service if they chose to?</li>
<li>Next there are the security implications of shortening links and hiding their ultimate destination. If I see a link to companyname.com, then I can take a view on whether I trust that company and wish to follow the link. But if I see http://t.co/abcdefgh then I have no knowledge of where I am going to end up and if it is a safe site to visit. So I have to fall back to trusting the tweeter who posted the link.</li>
<li>Next there is the issue of information loss with the use of t.co links. If I archive Twitter feeds, then there is a chance that in years to come when I look back at those Tweets, that any t.co links may not work. The domain may no longer exist, the service may have been taken down by Twitter, or Twitter may not even exist as a company any more. And if you think this seems likely, consider that historians could be reading through today&#8217;s tweets hundreds of years from now. Samuel Pepys&#8217;s diary wouldn&#8217;t be much use to us now if it contained content like &#8220;today I walked down abcdefgh street&#8221; and the lookup from abcdefgh to the real street name had been lost in the intervening hundreds of years.</li>
</ol>
<p>But ultimately, the main reason that the whole t.co approach is truly broken is that it is a copy of a workaround implemented by tinyurl.com, bit.ly, etc. Twitter own the underlying platform so could have implemented a better solution rather than just copying someone else’s solution.</p>
<p>Why did they not just simply add support for structured metadata attached to a tweet? Then we could have links that were separate from the body of the tweet. This would eliminate the whole link shortening business, and also allow for big improvements in the user experience and readability of tweets by moving all that nasty http:// mess out of the body of the content.  Even the<a href="http://www.theinquirer.net/inquirer/news/1558680/berners-lee-regrets-double-slash"> inventor of aitch-tee-tee-pee-colon-double-slash admits that it is a bit of a mess</a> so we should be trying to use it less not more!</p>
<p>As one of the internet&#8217;s key services and most iconic brands, we should expect more innovation from Twitter and more focus on the user experience.</p>
]]></content:encoded>
			<wfw:commentRss>http://priocept.com/2012/02/09/why-twitter-links-are-broken/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Russia and Middle East launch new Niquitin websites</title>
		<link>http://priocept.com/2012/02/09/russia-and-middle-east-launch-new-niquitin-websites/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=russia-and-middle-east-launch-new-niquitin-websites</link>
		<comments>http://priocept.com/2012/02/09/russia-and-middle-east-launch-new-niquitin-websites/#comments</comments>
		<pubDate>Thu, 09 Feb 2012 13:20:09 +0000</pubDate>
		<dc:creator>Priocept News</dc:creator>
				<category><![CDATA[EPiServer]]></category>
		<category><![CDATA[GlaxoSmithKline]]></category>
		<category><![CDATA[Priocept News]]></category>

		<guid isPermaLink="false">http://priocept.com/?p=2511</guid>
		<description><![CDATA[Niquitin.ru and Niquitin-me.com are the latest internationalised websites to be launched on the Priocept developed web platform for GlaxoSmithKline.]]></description>
			<content:encoded><![CDATA[<p>Local country websites for GlaxoSmithKline&#8217;s Niquitin products have now been launched in Russia and the Middle East following the successful go-live of the new Niquitin UK site in December 2011.</p>
<p>Using EPiServer CMS at its core, the Priocept developed Nicotine Replacement Therapy (NRT) platform allows the various GSK international markets to build and manage localised versions of their Niquitin product websites using a standardised set of templates, imagery, applications and custom extensions.</p>
<ul>
<li>Niquitin UK – <a href="http://www.niquitin.co.uk/" title="Niquitin UK">http://www.niquitin.co.uk/</a></li>
<li>Niquitin Russia – <a href="http://www.niquitin.ru/" title="Niquitin Russia">http://www.niquitin.ru/</a></li>
<li>Niquitin Middle East – <a href="http://www.niquitin-me.com/" title="Niquitin Middle East">http://www.niquitin-me.com/</a></li>
</ul>
<p>This is the latest in a long line of international web platform development projects successfully delivered by Priocept, who continue to help GSK with their global rollout of digital products and services for their consumer healthcare brands.</p>
]]></content:encoded>
			<wfw:commentRss>http://priocept.com/2012/02/09/russia-and-middle-east-launch-new-niquitin-websites/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lotus Exige Development 2012</title>
		<link>http://priocept.com/2012/02/02/lotus-exige-development-2012/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=lotus-exige-development-2012</link>
		<comments>http://priocept.com/2012/02/02/lotus-exige-development-2012/#comments</comments>
		<pubDate>Thu, 02 Feb 2012 22:16:30 +0000</pubDate>
		<dc:creator>Priocept Racing</dc:creator>
				<category><![CDATA[Technical]]></category>

		<guid isPermaLink="false">http://priocept.com/?p=2448</guid>
		<description><![CDATA[For 2012 the Priocept Racing Lotus Exige is being further developed ready for an attack on the Silverstone 24 hour race in September.]]></description>
			<content:encoded><![CDATA[<p>For 2012 the Priocept Racing Lotus Exige is being further developed ready for an attack on the Silverstone 24 hour race in September.</p>
<p>This includes:</p>
<ol>
<li>Chargecooling the supercharger setup and running more boost so we can mix it with the front running GT cars.</li>
<li>Fitting a larger (even larger that we have already) fuel tank, this is a custom tank that we have designed with <a href="http://www.atlltd.com/indexuk.php">ATL</a> which will be a very tight fit, but we won&#8217;t disclose its capacity here!</li>
<li>Numerous improvements in the reliability, redundancy and cooling aspects of the car.</li>
<li>A sophisticated instrumentation / telemetry system for continual remote monitoring of the car&#8217;s performance and condition.</li>
<li>Air jacks and new hubs for quick tyre changes.</li>
<li>Various improvements to the engine management, fuel level monitoring and fuel endurance computer.</li>
<li>Weight reduction and aero improvements.</li>
</ol>
<p>Then we will retire it to a museum or perhaps the Priocept reception area!</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://priocept.com/2012/02/02/lotus-exige-development-2012/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Priocept Racing &#8211; Into The Night 2011</title>
		<link>http://priocept.com/2011/12/24/priocept-racing-into-the-night-2011/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=priocept-racing-into-the-night-2011</link>
		<comments>http://priocept.com/2011/12/24/priocept-racing-into-the-night-2011/#comments</comments>
		<pubDate>Sat, 24 Dec 2011 18:01:25 +0000</pubDate>
		<dc:creator>Priocept Racing</dc:creator>
				<category><![CDATA[Priocept Racing]]></category>
		<category><![CDATA[Race Reports]]></category>

		<guid isPermaLink="false">http://priocept.com/?p=2427</guid>
		<description><![CDATA[A Priocept film production of the Britcar MSA British Endurance Championship three hour night race at Brands Hatch, November 2011.]]></description>
			<content:encoded><![CDATA[<p>In November 2011, the Priocept sponsored Lotus Exige driven by Dan Norris-Jones and Fulvio Mussi competed in the final round of the <a href="http://www.britcar24hr.co.uk/">Britcar MSA British Endurance Championship</a>, a three hour night race at Brands Hatch.</p>
<p><a href="http://priocept.com/wp-content/uploads/2012/01/dnj_mussi_640.jpg"><img class="aligncenter size-full wp-image-2426" title="Priocept Racing - Into The Night 2011" src="/wp-content/uploads/2012/01/dnj_mussi_640.jpg" alt="" width="500" height="276" /></a></p>
<p><strong><em>&#8220;Priocept Racing &#8211; Into The Night 2011&#8243;</em></strong> is a short film that tells the story of the team&#8217;s preparations and endeavours on race weekend.</p>
<p>You can watch the film in the player below, or select the &#8220;Full screen&#8221; option and then &#8220;720p&#8221; for full HD viewing.</p>
<p style="text-align: center;"><iframe width="500" height="281" src="http://www.youtube.com/embed/B7xaMOqr6vc?fs=1&#038;feature=oembed" frameborder="0" allowfullscreen></iframe></p>
]]></content:encoded>
			<wfw:commentRss>http://priocept.com/2011/12/24/priocept-racing-into-the-night-2011/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Priocept launch new Niquitin.co.uk website</title>
		<link>http://priocept.com/2011/12/23/priocept-launch-new-niquitin-co-uk-website/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=priocept-launch-new-niquitin-co-uk-website</link>
		<comments>http://priocept.com/2011/12/23/priocept-launch-new-niquitin-co-uk-website/#comments</comments>
		<pubDate>Fri, 23 Dec 2011 11:00:11 +0000</pubDate>
		<dc:creator>Priocept News</dc:creator>
				<category><![CDATA[EPiServer]]></category>
		<category><![CDATA[GlaxoSmithKline]]></category>
		<category><![CDATA[Priocept News]]></category>

		<guid isPermaLink="false">http://priocept.com/?p=2505</guid>
		<description><![CDATA[Priocept have launched the first of the redesigned Niquitin websites for GSK in the UK market.  This follows a six month design and development of a new internationalised web platform using EPiServer CMS.
]]></description>
			<content:encoded><![CDATA[<p>Priocept have today relaunched the <a title="Niquitin.co.uk" href="http://www.niquitin.co.uk/">Niquitin.co.uk website</a> following a six month project to develop a new internationalised platform for GlaxoSmithKline using EPiServer CMS.</p>
<p>This new web platform for GSK&#8217;s Nicotine Replacement Therapy (NRT) products provides local markets with a set of tools and templates which enforce a standardised look and feel, yet can be customised and extended to meet the specific needs of each country website.</p>
<p>Further local market websites will be rolled out in 2012 along with new versions of the NRT Behavioural Support applications also being developed by Priocept.</p>
<p>Niquitin.co.uk: <a title="Niquitin.co.uk" href="http://www.niquitin.co.uk/">http://www.niquitin.co.uk/</a><br />
Niquitin Quitmasters: <a title="Niquitin Quitmasters" href="http://www.quitmasters.co.uk/">http://www.quitmasters.co.uk/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://priocept.com/2011/12/23/priocept-launch-new-niquitin-co-uk-website/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

