Hello BHW,
Today's release is very important. It significantly furthers BlogSense's power as a remote publishing tool for both status updates and remote blog posting.
For the longest time BlogSense, like many other WordPress plugins, has struggled with incorporating mass bookmarking services such as Ping.FM and HelloTxt because of their tightness on providing API keys to software developers. Finally we've found a potent replacement (Pixelpipe) that will allow us to further expand our automation efforts beyond Twitter.
Before I write a blog post, let me go over the powerful improvements now available to BlogSense users.
INTERNAL SPINNING
We now have a couple of extra spinning options that include this option ‘Salt with ASCII'. It turns out that letters can be converted to HTML ASCII that looks something like this: ‘hi ‘, which Google and web browsers read as ‘hi', and at the same time consider it a unique rendering of content. We've added this option for those who would like to experiment with it's extra uniqifying quality.
PIXEL PIPE - REMOTE PUBLISHING
We can use pixel pipe to remote publish to web2.0 properties such as blogger. The downfall of this module, currently, is that we must use email to send the content, and PixelPipe does not support html emails. Pixelpipe, in this case, is better used for status-update type bookmarking.
PIXEL PIPE - BOOKMARKING & STATUS UPDATES
In addition to Twitter, we can now use PixelPipe as a bookmarking source. Like remote publishing, we use email to send the status updates to a special pixelpipe email address. This works very well as the title & a link to the original content is sent to all the designated sources. Within BlogSense, we can add as many pixelpipe accounts as we want, and route content to specific pipes by using routing tags. We can also now select which accounts we want associated with our campaigns by selecting and deselecting them inside the campaign editing section.
Available PixelPipe Services
TWITTER - BOOKMARKING IMPROVEMENTS
Like we mentioned above, we can now select which Twitter account we want associated with an account, as well as create custom hashtags for each account within a campaign. This further opens up our Bookmarking module to more campaign-based quality control practices.
REMOTE PUBLISHING - EMAIL OUT
We now have the capability to export campaign content to an email address. It's as simple as this. If you are interested, watch this video demonstrating how I use this feature with Google Groups.
How to use BlogSense to publish to Google Groups
http://www.youtube.com/watch?v=0Laq8WsnQ-Q&feature=related
[/INDENT]
INFORMATIONAL PIECE ON HOW TO BEGIN A BLOG NETWORK USING BLOGSENSE'S REMOTE PUBLISHING API
[INDENT] Due to popular request, I've attempted to make a two-part video documentation set on how to remote publish to other BlogSense blogs; aka how to have a master hub and autoblog to many other BlogSense blogs.
[B]Setting Up Your Own Link Network with BlogSense[/B]
Part I - [url]http://www.youtube.com/watch?v=-HYgt_aa67o[/url]
Part II - [url]http://www.youtube.com/watch?v=HKdAn_hw4CA[/url]
[/INDENT] It's also should be announced that BlogSense no longer supports lifetime licenses. We rather provide 10.00 / mo. licenses and 95.00 / yr. licenses. We also still support single-blog licenses for $20.00ea.
[URL="http://www.blogsense-wp.com/news/blogsense-9-1-0-2-remote-publishing-with-email-remote-publishing-with-pixelpipe-bookmarking-with-pixelpipe/"]
More about Remote Publishing with BlogSense[/URL]
