Posts Tagged ‘ping.fm’
I like using the HootSuite bulk uploader, and round the time I posted the post HootSuite Bulk Uploads I had set up a Google Docs file to produce the csv file it requires as input. It can simply be made by uploading the example provided by HootSuite to Google Docs and using that as a template.
As I was explaining the features of HootSuite to my mother, including the bulk uploader, I suddenly realized that I could make my spreadsheet more valuable for myself and others by adding a check to see whether it has 140 characters. I wasn’t able to use the regular Docs Data Validation, so I decided to roll my own in the script editor, which meant adding a Trigger to the script so it is called after the spreadsheet is edited. Read the rest of this entry »
In December of 2010 HootSuite enabled bulk scheduling of messages to FaceBook, Twitter and the other services it supports. This was during my HootSuite hiatus, which means I missed it. I think it’s such a cool feature that I wanted to spend some time on it. It’s so easy to schedule future messages by creating a .CSV file, as the example below:
Go to the compose message and press the calendar icon, which opens the calendar (image on the left). Press the Schedule in Bulk button to open the uploader (image on the right). Here you can select a social profile and upload a correctly formatted .CSV file with up to 50 messages. HootSuite will schedule these messages for this profile. Any errors are concise, they usually relate to problems in the file due to invalid input or duplicate messages.
In the last two days I’ve not been posting so much, and focussing on updating my “Social Media Syndication” flowchart. During the building of this which includes over 100 services I made some configuration errors, which lead to a number of services taking their input from Ping.fm or Twitter and reposting this to another site which reposted this to Twitter or Ping.FM. This has show me that in principle the application of Social Media Syndication can be an even more powerful tool than I first realized. (Which I will explain in a later post.)
As I have always said is that I make mistakes so my clients don’t have to, and in this case I made some mistakes which is helping me to create a new flowchart which can – under the terms of Creative Commons Attribution-ShareAlike 3.0 – be used by all to ensure that they can be available on multiple platforms. Naturally this doesn’t remove the essential human element that is the primary part of Social Media.
I will be able to share this with the world at the end of November, I’m going to release more than just the result image this time and will release the source document in an open format so that it can be extended for mashups and remixes can be made.
Image source: geishaboy500
As you might have noticed I’m slowly coming to appreciate Ping.fm as a tool to update my microblogs, or status. Some Twitter and Brightkite subscribers started complaining that they were getting two messages. The first was a update from Ping.FM directly to Twitter. The second went from Ping.fm to Brightkite – which adds the geolocation – and was then posted to Twitter.
It looked a little like this:
Sitting at home about 2 hours ago from Ping.fm
As Brightkite sends the message on to Twitter with my current geolocation added it wasn’t necessary for Ping.fm to directly update Twitter.
The only things I still have which updates Twitter directly are:
- TwitterFeed (for my blog)
You might have noticed that some subjectless, single blog line posts are added to this blog during the day, they may contain a location or an activity as would be more appropriate for a Twitter or a BrightKite feed. These truncated blog posts are actually the microblogs – or status updates – which I’m sending with my GTalk client for the CrackBerry to Ping.fm – which syndicates my microblogs to 20+ sites including Twitter. Sadly enough these messages are erroneously being posted to WordPress by Ping.fm.
I am currently employing two options for correcting this:
- Use my custom trigger (shortcut #ms) to post to all my microblogs – by way of Ping.fm – with the exception of WordPress
- In case a message is posted incorrectly, remove the WordPress item from the blog manually
This does mean that typos cause these microblogs to appear here until I manually remove them, however leaving WordPress active in Ping.fm still makes it possible for me to write a blog post in Ping.fm and have it syndicated to all my blogs. Were I to decide to remove WordPress from Ping.fm I would most likely lose a good part of the automated syndication of my blog postings.
UPDATE: I think I’ve been able to disable this for WordPress, we’ll wait and see…