And now, the end is near…

We’ve been saying for a while that since our acquisition by AVOS, Trunk.ly would eventually shut down.  Now with the launch of the twitter connector into Delicious that time has come.

While there are other connectors in Trunk.ly, the Twitter one represents about 90% of the active usage with most of the others used by only a small handful of users.  Some, like our Hacker News connector will likely never transition (there was only about 50 users and we had permission only while the volume was low), while others like Facebook are on the Delicious roadmap, but don’t have enough volume to warrant maintaining Trunk.ly just for that.

It’s now time to say goodbye to Trunk.ly.  There’s never a perfect time to wrap things up, but now feels about right. We will shut the doors on Trunk.ly for good on Monday 12th of March.

Thank you for your support and use of Trunk.ly over the last 16 months or so, it’s been our pleasure to provide this service and we hope you’ll join us again at Delicious as we build new and exciting tools to help you share collect and share content with the world.

Update on Trunk.ly shutdown – we’re extending it another month to 20th of Feb

It’s been exciting times for Alex and I over the last couple of months since we’ve started working with Delicious. We’ve made great progress with some of the integrations as well as getting involved in other features too.  However, as we approach the original deadline for closing Trunk.ly  (January 13th) it’s clear that the most critical of these (the Twitter and Facebook integrations) won’t be completed.

When we announced the shut-down for Trunk.ly I was conscious of a couple of things:

  1. I wanted to give a firm date.  We felt our users deserved some certainty.
  2. I didn’t want it to be unrealistically long; after all it’s inefficient to run two bookmarking services!

But we never wanted to leave people without an alternative either.  So we’ve decided to leave Trunk.ly up and running for another month, until February 20th.  This will allow more time for the Twitter and Facebook integration which is now underway to be completed.  While I’m fairly confident we’ll be completed by then, we will review it once more as we approach the next date.

Cheers,

Tim

AVOS Acquires Trunk.ly to Enhance Link-Saving in Delicious

We’re excited to announce that as of today, Trunk.ly has been acquired by AVOS, the new owners of Delicious http://www.avos.com/avos-acquires-trunkly.

As a result, Trunk.ly will be discontinued, and we will immediately start working to integrate our technology and insights to accelerate the link-saving and searching capabilities in Delicious.

So what does this mean for you?

  • Effective immediately we will no longer accept new sign ups for Trunk.ly.
  • We will continue to operate the site for another two months to allow you time to migrate your links.
  • As we are now working full-time on Delicious, we won’t be able to provide more than basic operational support.

To migrate your links you can export them here http://trunk.ly/settings/export/ and easily import them to another service (including Delicious).

Finally, thank you for your support – we never expected that 12 months ago we would grow Trunk.ly to the success it’s become and we really do owe that to you, our users who have helped us, supported us and promoted us along the way.  

We really hope you’ll join us at Delicious, we’re very excited to be working with them, there is a great team there with ambitious plans and together we hope to build the best way to discover and collect the web.

Cheers,

Tim and Alex

TV Spot – Trunk.ly mentioned on CyberShack in Australia

From the department of light entertainment, we were thrilled to be mentioned on CyberShack, a local tech show on Australian TV.  I wish I could pitch Trunk.ly as succinctly as they do – hitting all the high points in just under 40 seconds!

http://www.cybershack.com/tv-episode/trunkly

 

 

New iOS5 update – now it’s even easier to save links into trunk.ly

We’re working hard to make trunk.ly the easiest way to save links.  With the new Twitter integration in iOS5 for iPhones and iPads, that saving has got even easier!

Now when you’re browsing an article in mobile safari, you not only have the option of emailing it to yourself in trunk.ly, but now, you can tweet the link directly from the article as well (just click the “forward” arrow icon coming out of the square and choose Twitter).

With one click you’ve just shared the link with your friends and if you’ve connected the Trunk.ly twitter connector, you’ve also just taken care of saving it and indexing it so you can find it again later.  Trunk.ly really is the easiest way to save links and now with iOS5 and our Twitter connector, it’s even easier to share and save the link for later too.

 

Change to link importing – now supporting “dead / hidden” links

Previously we’ve only stored links that we could reach.  One of the key things we do is to download and index the web page for you, so if we can’t “see” the link from our server, then this can’t happen.

In the past this practice seems to have caused little to no issue with regular users of Trunk.ly, perhaps because they are using the connectors into Twitter and Facebook and these links are also almost always public too.

But with an increasing influx of Delicious users and some changing behaviour (increasing numbers of people using the direct bookmarklet as well) this was beginning to cause some confusion.  The most obvious time you would see this is if you imported a bookmark file of say 1,000 links, Trunk.ly might say “950 links imported”.  What this really meant was that we couldn’t see 50 of these links, most likely because they were “dead” or perhaps because they were hidden behind a firewall or similar.

The release of the private links feature also means that people are now more likely to bookmark private content that’s perhaps behind a firewall or similar too.

So we’ve changed the behaviour.

Now when you import links we’ll import every link, even if we think it’s “dead”.  We’ll also store links that you can see but we can’t.

We are planning to expose these dead links at some point in the future so you can review and tidy them up if you wish however right now you can’t tell specifically from a link if we think it’s dead or not.

We think this change is a logical evolution in the service.  It also means that users importing thousands of links from Delicious will get a more predictable / expected link count even if some of those links are no longer live (which isn’t unusual, especially considering that some people import 10′s of thousands of links).

Disabled Connectors

So one of your connectors is disabled?  What does this mean and what do you do about it?

If a connector is disabled it means that Trunk.ly can no longer collect links from that source.  It almost always means that the credentials we have stored for you are no longer valid.  Fortunately it’s easy to fix, simply remove the connector if you no longer need it, or just add it again and re-authenticate it and everything should start working again fine!

Why does this happen?  It can happen for several different reasons:

  1. In some systems, like Facebook, the token we store becomes invalid when you change your password, forcing us to need you to re-authenticate and store it again.
  2. You might have removed our authentication directly from the application.  In most applications that use Open Authentication (OAuth) like Twitter, Facebook and LinkedIn you can remove the authorization for the connecting client (in this case Trunk.ly) directly from the application.  If this happens, we no longer have permission to gather your links and will disable a connector.
  3. Occasionally it “just happens”.  Facebook in particular will de-authenticate apps and change the tokens “because it feels like it” or if it’s concerned about your security for example.
If you see this error, there’s no need to worry – just re-add the connector and we’ll reauthorize everything.  If you continue to have problems, let us know and we’ll look into it further.  Most times a simple re-connect resolves the problem.

Send links from your iPad and mobile apps like Flipboard straight into Trunk.ly using the email connector

If you’re like me, you love using mobile devices as an alternative way of consuming content.  Applications like Flipboard are a great way to browse the contents and articles out of your Twitter and Facebook streams, but until now it’s always been hard to save these for reading them later or just for future reference.

This is where Trunk.ly’s email connector works a treat.  With the email connector every user has their own personal trunk.ly email address, which looks something like this timbull+1234@post.trunk.ly.  It’s comprised of your trunk.ly username, a secret key which you can set and it’s sent to the special mail domain, post.trunk.ly. You’ll find your trunk.ly email address on the Link Sources screen.

Put this into your address book (especially one that syncs with your mobile devices) and you’re good to go!  TIP: It’s handy to give it a name that’s easy to remember like “Mail Trunk.ly” or similar.

So now when you’re using an iPad application like Flipboard to kick back and catch up with the news of the day…

You just click the forward icon, select “Email Link” and send it straight to Trunk.ly.

Within a couple of minutes (depending on the number of links being processed) you’ll see the new link show in Trunk.ly.

One word of caution – the email collector processes ALL links in the email, so it does mean you’ll see a link to Flipboard show as well, however as we don’t duplicate links, it will only ever show once.  This can also be an issue when you email Trunk.ly from your personal email (as I like to do when I’m sharing links with colleagues internally), you’ll want to make sure you remove your email signature.  We have plans in the future to provide some form of filtering to help with this.

Note – if you’ve used the email connector in the past and had some issues with it not saving the links, we’ve overhauled it significantly to improve it even further today.  However if for some reason links don’t show, let us know and we’ll look into it straight away.  Unfortunately it’s just not possible for us to test every possible combination of free form email from all mail clients and applications, however we are confident that this new version will work extremely well for all the use cases we’ve thought of.

See that empty “title” bar? How you can help.

If you use our browser bookmarklet or the “Add Link” on toolbar,  you might have seen an empty “title” bar like this:

What was happening behind the scene was this. When you  added a new link, we will request the actual web page and save them into our search engine so that you can find it later.  Sometimes we couldn’t download the web page either because the remote website is down temporarily or our little robot friend who actually went out and downloaded the link just had a hiccup.  (Note that we will retry three times before we gave up and less than 0.5% links ever had problems.)

This affects you as a user because you won’t be able to find the link later.   We are working hard to resolve issues like this.  With the help from user infoholic and zephyr, we just release an improved version that should work a lot smoother. Now, if you even see the above “empty title” show up again, please drop us a note so that we can investigate further.  Our email address is contact@trunk.ly.

Trunk.ly – the easiest way to save links online, behind the scenes on the new design.

When we launched the new trunk.ly last week, I promised that we’d highlight some of the new features and why we are the easiest way to save links online.

As we said when we very first launched trunk.ly back in December last year, the nature of bookmarking is changing it’s:

now a rolling social rumble of retweets, likes, favorites, sharing, commenting and general discussion…

Fast forward almost 10 months later and that hasn’t changed.  We still firmly believe that the future of bookmarking is not just manually tagging and curating your way around the internet, but rather it’s about hooking in to your natural online behaviours and using automation to collect what interests you and search to quickly find it again.

But the old trunk.ly was still somewhere half way between the two worlds of “traditional” bookmarking and our vision of automation and search.  With the new trunk.ly we wanted to achieve several things:

  1. Make the goal of trunk.ly much clearer to new users.
  2. Ease the path of new users into the product with a better sign up experience.
  3. Improve the speed of trunk.ly
  4. Clean up the UI and set up a new design that will allow us to extend the features without the clutter.

Make the goal of trunk.ly much clearer to new users

Our new landing page clearly outlines the key features in trunk.ly.  What’s always been interesting about trunk.ly is that with the exception of occasional PR spikes where someone might write a blog post about us, our new users are primarily driven by word of mouth.  This often meant that people hitting the homepage would sign up regardless (because someone had recommended it to them) but that they really didn’t know what we did.  They often came because someone tweeted something like “Trunk.ly is awesome!”.

By outlining the new features, we’re clearly introducing users to the benefits of Trunk.ly.  This has meant that our “bounce rate” (people hitting the home page who go away) has slightly increased – if I know what you do and it’s not for me, I no longer need to bother signing up to find out.  That’s OK – the great news is since the new release the total number of users finding us through search and by referral has significantly increased and although in percentage terms about 10% fewer sign up, in real terms the total number of users that do sign up has doubled and is growing.

Ease the path of new users into Trunk.ly

The clearer home page helps, but the big improvement in people correctly setting up Trunk.ly is mainly due to the new wizard.

This new wizard achieves two things.

  1. It guides new users through the most important actions that will get them the most benefit from trunk.ly like connecting it to Twitter or Facebook.
  2. It does so in a way that means that by the time the user arrives at their home page, they typically see their latest links already indexed.
Those of you that have been with us on this journey since day one might remember how woeful this initial experience was.  Initially when we launched (especially as we had some scaling problems), new users might wait 4 – 6 hours to see a link.  Now when you use trunk.ly for the first time, your links are typically there and waiting for you on the first use.
The previous design lead to all sorts of frustrating issues, including one user who took seven months to understand what trunk.ly was and how it could help him (for him then to become a supportive convert).  For every user that persisted for seven months, more would have disappeared.  Clearly that experience needed some work.  I’m sure we can do better, but we’re really nailing the key issues with this and couldn’t be happier with the take up we’re seeing.
To put some figures around that – there is a 100% increase (or near enough to) in the number of signed up users that complete a key step like connecting Trunk.ly to automatically extract their links from Twitter and Facebook.

Improve the speed of trunk.ly

Lots has been done to make this happen, much of it behind the scenes.  One significant change is to the timeline (although it’s still visually similar).
Previously the way this was done meant that something like around 75% of the resources in our database were being used to maintain the timeline.  We completely redesigned it and improved it which means that it’s much snappier and we could remove that hungry collection from the database all together.
Other things like the tags were not only primitive in terms of functionality, but the way they were implemented was causing the database to slow down (and users to occasionally see 500 errors).  We also re designed these which means that now, they don’t slow the site down and a lot of much needed tag functionality is being implemented (there’ll be some new features soon).
We also make a lot more use of compression and caching to improve the speed.  Trunk.ly today is significantly faster than it was previously.
There have been lots of studies which show that there is a strong correlation between the performance of a site and user satisfaction.  We haven’t quantified it, but we think this is really important.

Clean up the UI

This is perhaps the most controversial of the changes.  While most users love it, we do have some people that strongly prefer the previous version.  Judge for yourself:
Picture of the Trunk.ly user home page
The previous UI was far too subtle.  We were written up by The Next Web on one occasion who said about the old design:
If I have a criticism, it’s that there’s no main, Twitter-style aggregated feed of all the links shared by people you follow – you have to visit their individual pages.

It’s there on the left in the old design (actually it’s what’s selected in that picture above).

We received emails about the old design that said things like:

Because the only part that interests me, is a tiny tiny sentence… lost in a sea of irrelevant content.

And there was a lot more.  We sat down with users and they told us they wanted to be able to search their links.  They said that they wanted to be able to manually add links.  Both features which are core to Trunk.ly and have been since our launch.  But they couldn’t find them.

The design needed to change.  The new look introduces a lot more contrast.  The use of colour is more subtle, but in turn is intended to draw your eye to important news.  Error messages have largely been standardised and work the same way throughout the site.

By moving content to the slide-out panel we could improve the loading speed and predictability of the page layout over the old version (large images sometimes took up the whole page).

The whole site is now much more cross-browser compliant and works well on iPads as well as Internet Explorer, Safari and Opera – not just Chrome and Firefox.

We deliberately went very minamalist and the feedback has on the whole been great.  While some users want the old design back, the majority who’ve commented like the cleaner layout, the new fonts and the subtle use of colour.  Still, there are a few items we’re reviewing (particularly the edit and delete links) and we’ll continue to tweak it (like we tweak everything) to try and improve it even further.

Where to from here?

There’s a huge road-map ahead of us.  In the short-term we’re very focused on polishing this new release.  We’ve made literally hundreds of small changes to the site in the last couple of weeks, fixing bugs, tweaking text and improving things in response to feedback.  Most days we’d push 5 or more changes to production.  There are also few consistent items of feedback we’ll continue to monitor and decide if we want to change the layout a little more in response to these.

We’ve got even more improvements to the tags coming, including some bulk edit features.  We’ll implement people search to make it easier to discover and find users to follow.  We’re overhauling the emails. We’re launching more connectors (on the immediate list are Disqus, GPlus and StumbleUpon) and we’ll continue to work hard to keep improving trunk.ly and making it the easiest way to save links online.

In summary, this new design has met all our design objectives, it’s cleaner, engaging more users and has the space we need to continue to add and expand on Trunk.ly.

Follow

Get every new post delivered to your Inbox.

Join 787 other followers