August 23, 2005
| Movable Type |
movable_type
|
I wasted some hours on this few days ago so I think I want to share this information. We changed server and the new machine is a 64 bit one. The Storable.pm perl module was giving me this error
An error occurred: Byte order is not compatible at ../../lib/Storable.pm (autosplit into ../../lib/auto/Storable/thaw.al) line 363, at [path to MT directory]/lib/MT/PluginData.pm line 28.
I yahoo!ed a lot and I found only wrong paths. For example this forum thread suggests to change the code of lib/MT/PluginData.pm. After a lot of attempt changing the code, I found this post. I asked by email to Roger if he solved the problem and he replied that he used the trick described at Freebsdblog. And Yes, this worked! So I copy here the solution hoping to give it higher prominence in search engines.
After changed hosting, the perl version is different on the new server, MT-Blacklist can't read the database data due to the different byte order, error message looks like:
Plugin error: plugins/Blacklist.pl Byte order is not compatible at blib/lib/Storable.pm (autosplit into blib/lib/auto/Storable/thaw.al) line 363, at lib/MT/PluginData.pm line 28 Compilation failed in require at lib/MT.pm line 291.
The problem was fixed after I deleted all records in the table mt_plugindata.
Simple, eh? And think that I lost a lot of time changing the code of the perl module and testing it out on different machines ;-(
Hopefully, people with the same problem will find this post or the original one on freebsdblog and save a lot of time.
April 27, 2004
| Blogging |
blogging
|
| Movable Type |
movable_type
|
If you want to use Movable Type for your blog but don't have an always connected computer or simply don't want to install it, you can use Weblogs.us, free MT blog hosting.
I'm using MT for this blog but, if I had to choose the blog server today, I would probably choose WordPress (read a short review). Note that WordPress is free software while MT is not.
November 17, 2003
| Blogging |
blogging
|
| CoCoA |
cocoa
|
| Movable Type |
movable_type
|
| Recommender Systems |
recommender_systems
|
| Semantic web |
semantic_web
|
| Trust and Reputation |
trust_and_reputation
|
I've just used blam! in this review of Revolution OS.
Basically blam! add some semantic information to your blog entry when this is a review. The semantic information can be understood by a computer program so that it will be possible to, for example, aggregating all the reviews about a certain book or movie.
Read about OpenReviews and their possible uses from Accordion Guy.
I'm planning to do something similar for my project CoCoA.
The semantic format for reviews is RVW (Review Module for RSS 2.0), created by Alf Eaton. Read an explanation of RVW from Corante.
The RVW specification is a module extension to the RSS 2.0 syndication format. RVW is intended to allow machine-readable reviews to be integrated into an RSS feed, thus allowing reviews to be automatically compiled from distributed sources. In other words, you can write book, restaurant, movie, product, etc. reviews inside your own website, while allowing them to be used by Amazon or other review aggregators.
There should be more than enough RVW metadata out there floating around at this point. The next step is for someone to build a decent aggregator that collates reviews of a particular topic or two. Because of RVS, creating aggregate rating scores and summarizing opinions should be very straightforward. It's really not in the best interests of Amazon, epinions and the like to lose control of their review content, but RVW makes controlling review content impossible in the long term. Anyone got some pull at the Google skunkworks?
Blogware supports the new format and there is also a RVW plugin for Movable Type but I don't understand how it works.
Seb likes RVW and also point out how this semantic information could be used to generate personalized recommendations.
In the case of item types that describe reviews, overall average ratings on any particular product are easy to look up. However, if you choose to provide a description of your personal web of trust to those interfaces (think of blogrolls as a proto-example), you can efficiently get a sense of what your tribe of like-minded individuals thinks of that product. It's the microblogosphere idea again - look up Recommender systems and the microblogosphere for more.
This is essentially what my PhD Research Proposal: Trust-aware Decentralized Recommender Systems is about.
