My statement was more: *if * there's a good app, surely it's worth the price of sandwich.

As an example, I paid for Gravity (a good app, no complaints), but mostly I just use @dabr in the browser because it's faster.

My statement was more: *if * there’s a good app, surely it’s worth the price of sandwich.

As an example, I paid for Gravity (a good app, no complaints), but mostly I just use @dabr in the browser because it’s faster.

Just seen your Tweet, (http://twitter.com/pixelpipe/statuses/2043971546), glad to hear that you're a) listening and b) there's a fix coming.

The Share Online setup *is* confusing and a step by step guide would be best, maybe for each OS/integration option.

'@flickr' vs 'flickr' – who knows?

James.

As I explained briefly on twitter the Routing Tags are all prefixed with an @ character. We scan the body of the post and look for corresponding tags associated with your destinations. If we find a tag that's been associated with one or more destinations we override your default services for upload and just send to those associated with the routing tag. So in brief you needed to include “@flickr” and not simply “flikr” as a tag to be utilized for routing.

Here's a few tips:

- Turn off TwitPic and other services that send to Twitter as a default destination and only enable through routing tags

- You can create groups by giving the same tag to multiple services eg. @friends, @status

- We create a tag with the service name by default however you can rename and add additional tags eg. Facebook: @fb,social,all. Now I can include any three of those tags and Facebook will be included in the upload as well as any other service that includes these tags.

Hopefully that makes things a bit more clear then my brief explanation on Twitter, customer support can be frustrating at a 140 char limit. Thanks for all of the feedback, we're incorporating a few of your suggestions now to make things a bit more obvious.

-Brett