3 posts tagged “tool”
EDIT: Thanks for all the volunteers - I think I'm set on the alpha testing crew (who I will be contacting as soon as I can get the front-end tied to the back-end and make sure it's not going to break when you type in your vox address). If you missed your chance to volunteer for testing - don't fret; I don't think the testing process will take all that long and I'll be opening it up for general consumption just as soon as I possibly can.
Okay, I'm not actually quite ready for alpha testers just yet, but soon I will be initializing the alpha version of the Vox export tool to those willing to help me test it out prior to making a formal release to the masses. I wanted to get names of people interested in helping now, so that as soon as I'm ready I can contact you individually and get you started on the testing process. Please read below and if you are interested in alpha testing the tool, please email me at VoxPorter@gmail.com . I NEED A VALID EMAIL ADDRESS from each alpha tester so I can be in communication about updates, bug fixes, and requests for more information if I'm trying to figure out what went wrong in your setup. I will NOT be communicating this through Vox comments or PMs, so if you're not willing to email me, please don't volunteer.
Testers should:
- Be willing to try out the tool (possibly multiple times if bugfixes are required)
- Be able/willing to import the resulting file into a WordPress blog (instructions may be provided if you don't know how) (free WordPress blogs can be created at WordPress.com, or you can set one up on your own server if you know how)
- Be able/willing to review the resulting blog for problems/errors in the import process (i.e. checking to make sure content imported properly, blog post titles, dates, and tags appear correct, etc)
- Be able/willing to inform me of any problems you experience or notice, as well as provide comments/questions about using the export tool, the process as a whole, and any specific areas you think need improvement. You won't need to be available to run the tool the same day I send you notification, but please only volunteer if you think you can support the testing in a timely manner (i.e. within about a week of getting a notification for testing).
Again, if you are interested in alpha testing the tool, please email me at VoxPorter@gmail.com . I'll select testers based on my current needs and the number who volunteer.
Oh, and FYI, the current planned Alpha version of the VoxPorter (name still in flux) tool includes the following:
- Export all publicly viewable blog posts from a user's blog to a WXR .xml file (WordPress import file)
- Importing this file into a WordPress blog will import blog titles, posting dates/times, content, and tags from posts to the new blog (note: links and media [pictures, music, videos] will still link to their current Vox enclosures for now)
- Select whether trackback pings and comments will be globally enabled or disabled on all imported posts
Future improvements planned once this version is tested and available in a steady-state form:
- Option to also export post comments (would show up under each blog post, just like they do on Vox)
- Automatic splitting of WXR file on the fly into 2 MB sections for blogs with massive archives
- Secondary tool to allow you to quickly and easily download your entire uploaded photos library for use on your new blog
- Secondary tool to allow you to quickly and easily see what other social media services your Vox neighbors use (along with links to their individual accounts) so even if you decide not to stick with Vox, you can still stay in contact with your 'hood through other apps or sites
Other improvements possible but less likely (given the time I have to work on this):
- Converting Vox links to your blog posts on the fly so they link to other posts in your new blog
- Converting to other blog formats besides Wordpress (Blogger, MovableType, etc)
- Automatic widget/banner creation that you can post on your Vox blog to point people to your new blog location
Note: The post below is extremely geeky and probably not interesting to anyone except those who would like to follow along with the progress of HOW I'm implementing a Vox export tool. If you're just interested in hearing when I'm done with it, this is not the post for you - that'll come soon.
I'm more laying this out for my own thought processes than in any sort of attempt to educate on how the export tool is going to finally work. The good news is I have a tentatively working solution that will theoretically import a full Vox blog onto a self-hosted Wordpress installation. The bad news is that the solution in mind will NOT work for (free-hosted) Wordpress.com installations, so I'm still trying to figure out an alternative for those. Preferably one that does not involve someone having to find a friend with access to a self-hosted version to do an intermediate conversion for them.
After countless hours (days? weeks?) of half-assed research online, here's a summary of what I've come up with regarding exporting from Vox (VoxPorting? Anyone got a better name for the eventual tool I'll be posting?)
- Blogging services SUCK at normalizing on an export standard. Every single one of them is different. Likewise, almost all of them try to trap you into their service by only allowing you to import their export types and/or only export a type that will be incompatible with other services. This means people have to get crafty if they want to jump from one platform to another, especially if they do it more than once.
- The big
contenders for free (hosted) blogging services out there seem to be (in
no particular order): Vox, LiveJournal, Blogger, and Wordpress (hosted on Wordpress.com). Yes, MySpace and its clones exist, and no, I'm not going
to even try to get content over on to them.
- Additionally, you've got Wordpress (self-hosted) and MovableType (self-hosted) which are free, but require you to host them somewhere.
- Paid services exist (TypePad, etc.) but since they require you to front money, I'm not focusing on trying to export to them.
- That being said, looking at the free services, I've found the following:
- I'm
not looking to import into Vox, since that's obviously contrary to the
whole point of a Vox export tool. I believe there are easier ways to
migrate content from one Vox account to another than
exporting/importing. That being said, if you're just trying to back up
your Vox blog, you can either use BlogBackupOnline (to back up online only) or Simon Wistow's VoxSlurp (to back up to an .mbox file) - more on these in another post.
- Apparently exporting to a file to import to LiveJournal is out, as LJ doesn't even appear to be able to import its own export files.
Unless you're planning to repost every individual post on LJ, probably
not an option. I'm not even considering this at the moment.
- Blogger only imports "Blogger export files". There are solutions out there that seem to use Blogger APIs to get around this limitation, but this looks like A LOT of work. I looked at what the Blogger export files look like and don't know that I can forge one to duplicate a Vox account onto a Blogger blog. Holding this out as a last resort option, especially as there seems to be an alternative (see a couple bullets down, below).
- Wordpress (self-hosted or on Wordpress.com) seem to be the most likely choices. I've had success importing an RSS feed from Vox to a self-hosted Wordpress blog. It would be fairly trivial to expand this to create a custom RSS .xml file to encompass a full Vox blog, and import that into a new Wordpress blog. HOWEVER, Wordpress.com blogs (free-hosted) do NOT have the "import from RSS" as one of their options (for some bizarre reason, they don't offer this??) Instead:
- Wordpress.com imports from
Wordpress export files, called WXR (WordPress eXtended RSS). Both
self-hosted and free-hosted solutions export to WXR files, and both can
import from the other (I believe). Furthermore, once you've got a WXR
file, you can use a solution to convert this into a Blogger-compatible format to import to Blogger! Sounds like the winner, if I can figure out how to properly create a WXR file from a Vox blog. Except documentation on the WXR format seems to be pretty much non-existant,
so the only way to figure it out is to analyze an existing blog's
export file, the Wordpress import code, and experiment. Not the ideal
way to make sure I'm doing it correctly, and definitely a way that's
going to take more time to get to complete.
- One added
benefit to doing a WXR file - if I set it up properly, I could actually
scrape the Vox blog posts for comments, and forge new comments to be
imported along with the blog posts - this way, not only would you be
importing your hard work to a new blog, you'd be carrying along the
comments (which oftentimes are as informative/entertaining as the
original post!) Currently the plan is to do the first pass with just
blog posts, and then once I get that up and running, consider devising
the import w/ comments. The big problem is my approach to getting the
content off the Vox blog will vary tremendously depending on whether or
not I'm capturing comments - if I am, I have to do the much more
tedious (and much slower) page-scraping, as opposed to taking advantage
of the Vox RSS feeds that I would be using for the other non-comment
method. I'm not sure I'd want to commit to doing a page-scrape for every Vox export - I currently am doing that for my Picture and MP3 backup tool and it takes a bit of time - this would be even worse, given that some people have thousands of posts on Vox.
- Movable Type also seems to be able to import WXR files. Definitely looks like WXR is the way to go, and then provide that file to the user for their use in importing to Wordpress or MT (directly) or Blogger (via the converter).
Since I know you CAN import
to a self-hosted Wordpress blog from Vox and then export that right
back out to a WXR, the cynical part of me says I should post this
solution and then people who self-host can go ahead and import, and
people that don't can find someone to do it for them. Heck, I might
even go ahead and do this as an intermediate step to the final
soltuion. But in the end, I don't want to create half a solution and
have most of the users have to fend for themselves. People shouldn't
be penalized just because they signed up for a free blog on Vox and now
want to have a free blog somewhere else instead.
What is (or would be) your DJ name?
Actually, the correct tense would be 'What WAS your DJ name?' And in my case, I'm ashamed to admit I didn't have one. I'd just introduce myself as Ross when I was backannouncing. A couple of the other folks at the station had kickass DJ names - like one gal called herself NJ Gauthier (pronounced NJ Go-tee-ay), and of course we had our resident electronic music spinner, DJ Audiorapture. I was just Ross though.
That didn't prevent me from acting like a true DJ though, picking my own music and filling some requests when I could. We used to get collect calls from the nearby prison inmates requesting songs. The call would go something like this:
"You are receiving a collect call from:" "Anything by Tool except Schism" "would you like to accept the call?
(At which time you were supposed to hang up and decide whether you were feeling generous and could fit in something for the poor inmates, who probably were listening to the radio while lifting weights or some other boring activity.)
Unfortunately, at the time, Tool's "Schism" was on the heavy rotation list, so it got played a couple times a day. Since local station guidelines prohibited us from playing anything by the same artist within a certain timeframe, I don't think I was able to help out with this request. Not that I would have minded - most of the Tool songs off of the Lateralus album are over 5 minutes in length...which means an extra long break for the DJ.
I feel a little bit guilty about not being able to play some Tool that day...so here's some for all you inmates with computers out there...and I've made sure it isn't Schism. Enjoy!