View allAll Photos Tagged metaweblog
Ruby code to access/post on a Wordpress blog using xmlrpc interface
And now a possible solution to this problem. (Click on "all sizes" to zoom in)
But questions remain, and some links are not yet defined properly.
With the right tool however, I could get most of the above solution to
The problem is of course that the tool needs to support both RSS and
Metaweblog API as both input AND output, making it, effectively, an
RSS/Blogging router. RSS-as-input and Metaweblog-as-output are the big
issue here, hardly any tools i know of support these functions. Examples
that do though: Flickr can post (output) to blogs with Metaweblog, and
Movable Type can accept generic RSS imput for inclusion in the main blog
Most other tools can accept RSS too, but usually in the form of a special
widget (Facebook, Myspace, Wordpress).
My assumption is that the open source projects (Wordpress, Movable type)
will have many plugins available that can do this. But its a lot of manual
labor, and I have no clue about Linux/PHP, etc. So a hosted solution that
does this out of the box would be the easiest way to go for me.
Do-it-yerself is of course nice, but I lack the knowledge to do it...
perhaps, if i cannot find the right combination of customisation and cost
in the hosted world, it will motivate me enough to go learn Linux and some
basic web languages.
Screenshot for a gateway script allowing users to post their Flickr photos straight to their tumblr logs.
XMLRPC2TUMBLR in the Flickr app garden.
I wanted to tag all of my posts on my wordpress blog with 1750 posts. I started researching how it could be automated. The first problem was to access all of the content. Blogs hosted on wordpress have sitemaps of all published posts and pages at /sitemap.xml. Using LINQ, I was able to go through each page and download a copy to my hard drive.I wanted to get the raw data of the original post, including metadata. For this, I found a few API's built upon the XML- RPC.Net platform. XML-RPC for dot net came with a few interaces including Blogger API, MetaWeblog API, and Movable Type API. Wordpress supports a combination of the various API's, and extends them.I noticed that I needed to hard-code the API endpoints. Some metho!
ds were supposed to be available to set the URL, but the author forgot to inherit the IXmlRpcProxy on both IMetaWeblog and IBlogger. I added it and this got me up and running to get some posts. The methods available only provide a way to get the most recent posts (no paging). When I attempted to get all of my posts, I got exceptions. I found that I could parse the identification of my posts with a regular expression against the HTML content that saved to my local hard drive. I was able to directly access individual posts by their ID.I ran into problems with enclosures (podcast audio files). I tracked the problem down to an error on a bad implimentation of the MetaWeblog API by wordpress itself. The file length is supposed to be an integer, representing the number of bytes. It is returned as a string. I changed the interface so that the length of enclosures is treated as a string.After that, I started to have a new problem. None of the data included!
any tagging information. I got down to bypassing the Xml-Rp!
c library and making a direct call with a WebClient to fetch a known page with tags. The response not only included the basic structure defined in the MetaWeblog API interface, but it included a ton more fields, including mt_keywords. With this new knowledge, I was able to add the following fields:mt_keywordswp_slugwp_passwordwp_author_idwp_author_display_namedate_created_gmtpost_statuscustom_fieldsstickyThe custom fields introduced a new structure as well with id, key, and value fields. Each field was a string except for sticky (a boolean), and the date created in GMT (a date). Armed with this updated interface, I was able to download all of my posts once more and serialize them as xml to be saved on my local hard disk. I had some nice caching built in to load up the serialized xml objects as a cache rather than hit against the website. I did this for other files as !
well including the html, but that was saved as raw html rather than as an object.I now had a list of all published links in my site, and the serialized data for each published post. The next trick was to automate the keyword extraction. For this, I used Yahoo! with the content analysis API for Term Extraction. You can try this out for yourself without needing to learn how to program by copy & paste text into the form provided at Yahoo! Keyword Phrase Term Extraction Form on SEO Tools (Search Engine Optimization). In fact, I had originally used this form to discover keywords for a few of my posts before venturing out to find an automated solution.I signed up for an application id and started going to work. Since I was limited to 5000 request per day, and my blog had almost 2000!
posts, I decided to cache the results of the keywords for ea!
ch post as well so that I didn't hit it twice for the same content. I soon had a full list of keywords for the entire site.The keywords were unfiltered and unbiased. After merging keywords with existing ones on each post, I decided to refine them. I first started by creating a dictionary to hold the count of each keyword used across the site and then used LINQ to sort the end-results by the values.var qTags = from tag in TAGS orderby tag.Value descending select tag;foreach (var tag in qTags)Debug.WriteLine(tag.Value, tag.Key);I often found partial names of people I knew, such as "crap" or "mariner". To prevent things from looking vulgar, and to keep people from thinking that I talk about fecal matter, I transformed the tags into the first/last names. (i.e. "crap" becomes "crap mariner") I was also careful to remove references to the Lindens or their product to make an effort to avoid copyright infringement. Other tags were very generic, and so I removed them as well.The end result was a post that was ready to be updated. I made a few test runs first, and saw that my results were turning out great. The update calls seem to take quite a bit of time actually and may run for the entire night. From Dedric Mauriac via bloghud.com
Re-test of a 1280x1024 post with edited layout.
Posted via OE on PC (!!! testing only !!!).
Removed Flickr CSS, using fallback to blog CSS.
Switched from Blogger API to Metaweblog API.
Subject and content should appear correctly on Roller main-page.
Paragraph breaks are accomplished by double %lt;br> tags.
HTML is unescaped, hence bold works.
- is there really such a term as "nieces-in-law" ?
This photo is being emailed from my iPhone to flickr.
An embed of the flickr photo (not the actual photo) should then automatically get sent on to my posterous site since I just created a way to set up a posterous site in flickr's blog sharing settings. For some odd reason I couldn't find a way to do this provided by flickr, so I have set up a kind of MetaWeblog API proxy endpoint to connect your flickr account to your posterous sites and do the techie bit for you.
There is naturally a way to send/email photos to posterous which can then be sent on to flickr, but what happens then is you end up with two copies of the photo. One on posterous servers and another on flickr.
As discussed with @Documentally and @ilicco today on twitter, this can cause issues with copyrights etc, which flickr historically handles very well, so why not just have a single copy in your control managed by your flickr settings!? ;)
Well, here you go! Marvellous. Splendid. Etc.. :)
If this works then I'll share how to do this.
Fingers crossed and thumbs up!
edit: It worked! :) see: post.ly/11psx
Covers RSS 2.0, Atom, AtomPub, ROME, MetaWeblog API and more... Download it at refcardz.dzone.com
When trying to set up QumanaXP to work on a Roller Weblogger blog using MetaWeblog API
2. 「WordPress、 Movable Type、 MetaWeblog および Blogger XML-RPC 投稿プロトコルを有効にする。」
After a few failed attempts I seem to have the phonecam --> email --> Flickr --> dasBlog thing worked out. For anyone googling how to get this working, specify the MetaWeblog API@ Flickr, and point it at www.yourblog.com/blogger.aspx Seeme this end point handles both the blogger api and the metaweblog one.
I keep thinking that I am almost finished with reading email, but something new keeps comming up that directs my attention. I need this to be very stable, as I will be posting messages to my blog almost every day through it.Today I have a simple template ready to go. It is much like the one that bloghud uses, except that I include a slurl to the location. I haven't watermarked the image either. I have mixed feelings about that. I would also like the image to link back to a full sized image. I have a few more things to consider.Where would I like to store the files?What is the naming convention for images?What is the structure that I would like to save data in the database?How do I avoid spam?What will the final pop3 email account be?Should I open this up to others later on?Should I embed EXIF information into the images?After all of that, I also need to look into the wordpr!
ess API's supported such as Blogger API, metaWeblog API, and Movable Type API. These pretty much use XML-RPC to post content to my blog. Maybe I can post the images to be hosted on wordpress itself. I'm already finding some interesting support for "media objects" in the meta weblog api. From Dedric Mauriac via bloghud.com
Flickr でモブログしてみようと思い立ち、xpWiki に XML-RPC の MetaWeblog API を実装してみた。
とりあえず、Flickr で利用するため最低限必要な blogger_getUsersBlogs, metaWeblog_newPost メソッドに対応させてテスト中。 :-D
Feed.Us can auto-import content from a variety of sources. RSS feeds, email and Metaweblog API.