Posting RSS Feed to Post in Blogger Blogspot Blogs

From Sudelwiki

Jump to: navigation, search

LazyCrazyMazy.

Mizzion: bored, exploit auto-blogging on blogspot.com.

Howtoz:


Nazza Approach: http://com-uk.us/uncategorized/autoblogging-on-blogger-definitive-guide/

  • Get Free Hoster
  • Set up WP
    • Set up Autoblog-Plugins
  • Set up blogspot-blogs
    • Mail-to-Blogger
  • use feemyinbox-website and feed rss-feeds as mails to your blog BUT: that sucks.

Thiz kid iz wizzing zum tresting thoughts:


Rezultz?

One lazy afternoon spend on digi-shit - if u want solutions code yourself or combine toolz on your own - but coding yourself your own solution might even be faster and teaches you more.

Toolz that might be exploited:

  • ScribeFire, a Firefox-Blogging-Plugin, checking that
    • it'z GPL2 so source should be available...
svn checkout http://scribefire.googlecode.com/svn/trunk/ scribefire-read-only

Whut?

Now we stumbled from Autoblogging to writing Firefox-Extensions - that much about "simple".


Might be simpler to start from scratch - with a simple .php-Script to do the autoblogging for us

  1. Scrape content from Websites or Feeds
  2. Post content (that needs Blogger-Authentification aka Cookie-Saving, say "simple" again)
  3. Put Script on a free server that has all the functions you need and is not easily traceable back to you (just a habit)

Gna!

Might even be easier to just run a massive posting-party from an internet-cafe-machine from time to time.

Actually i decidead to create the HelloWorld-Firefox-Extension out of pure Boredomination and it was quite easy.

So the next step would be to tweak the ScribeFire into the AutoBlogMachineGun-Extension for blogger-blogspot-blogs - so basically ripping the login-part from scribefire and feeding some rss-feed into the posting-part - guess that needz clozer look to the scribefire-architecture...

... processing ...

... Blog-Account-Management seems to happen via parts of "Performancing"-Extension-Scripts - actually this ScribeFire-Thing does way more than we want to do - so - we might as well - simply look at the Google Blogger API directly:

And wasn't there something like google-code or so where you can host your scripts? Gotta look that up... ... leads to lotzofoptionz:

  • cURL
  • wget
  • PHP
  • combos

Playing it Local with wget

wget it, parse it, post it.

wget can emulate user-agents like firefox and save cookies - can it post stuff to?

if yes, we could parse content with sed in a shellscript and then post it, or sth. like that.

yes - it can.

wget http://blablablblaRSSblablbaURL -O rss.xml

from man wget

 --post-data=string
       --post-file=file
           Use POST as the method for all HTTP requests and send the specified data in the request body.  "--post-data"
           sends string as data, whereas "--post-file" sends the contents of file.  Other than that, they work in exactly
           the same way.

           Please be aware that Wget needs to know the size of the POST data in advance.  Therefore the argument to
           "--post-file" must be a regular file; specifying a FIFO or something like /dev/stdin won't work.  It's not quite
           clear how to work around this limitation inherent in HTTP/1.0.  Although HTTP/1.1 introduces chunked transfer
           that doesn't require knowing the request length in advance, a client can't use chunked unless it knows it's
           talking to an HTTP/1.1 server.  And it can't know that until it receives a response, which in turn requires the
           request to have been completed -- a chicken-and-egg problem.

           Note: if Wget is redirected after the POST request is completed, it will not send the POST data to the redirected
           URL.  This is because URLs that process POST often respond with a redirection to a regular page, which does not
           desire or accept POST.  It is not completely clear that this behavior is optimal; if it doesn't work out, it
           might be changed in the future.

           This example shows how to log to a server using POST and then proceed to download the desired pages, presumably
           only accessible to authorized users:

                   # Log in to the server.  This can be done only once.
                   wget --save-cookies cookies.txt \
                        --post-data 'user=foo&password=bar' \
                        http://server.com/auth.php

                   # Now grab the page or pages we care about.
                   wget --load-cookies cookies.txt \
                        -p http://server.com/interesting/article.php

           If the server is using session cookies to track user authentication, the above will not work because
           --save-cookies will not save them (and neither will browsers) and the cookies.txt file will be empty.  In that
           case use --keep-session-cookies along with --save-cookies to force saving of session cookies.

Tip on wget post header data:

... 1 AM ... finally got a prototype of a self-coded shellscript ready ... wget to rule dem all ... but ... i muzt admit ... only thing i can do now is post prepared .xml-Files from my Terminal-Commandline to my Blogger-Blog - BUT - that's one important basic-step forward. Now i can

  • Login via Google Blogger API with ShellScript
  • Publish via Google Blogger API with ShellScript

So the next step will be

  • Parsing RSS-Feeds with ShellScript and save the content in postable XML-Format
  • Auto-Generating loooooooooong List of Feed-Addresses

Posting / Publishing to Blogger API via PHP

Nice Script:

Personal tools