Social Networks
Comments
Submitted by Aldon Hynes on Sun, 07/20/2008 - 20:57EntreCard and SezWho
While I was off on vacation, EntreCard announced a partnership with SezWho. EntreCard is a site where bloggers can drop cards on one another as part of an advertising scheme to drive traffic to their sites. The folks at EntreCard note that adding comments is another key part of how to drive traffic to a site. So, they’ve partnered with SezWho, which is a site aimed at driving traffic through comments.
SezWho has gotten some mixed reviews early on. Apparently, early on, they had some distributed denial of service attacks which slowed down everyone who has using SezWho. In my case, I’m using Drupal for my blog, and their support for Drupal is in beta. So far, my experiences it that it is probably better to think of it as Alpha code.
When you install SezWho for Drupal, you need to go through the regular steps of a Drupal install. Then, you need to edit a configuration file, go in and tweak your theme files and hope things work.
In my case, they did not seem to work at all. The blocks showed up, but that was about it. After digging into the code, I found that it actually had synchronized some of my content, but a very limited amount. The posts that it synchronized didn’t have comments, so I couldn’t see what was going on. To complicate things even further, it seemed to have my content attributed to my old Optonline email address, while my comments were being attributed to my Orient Lodge email address, as was my registration and my EnterCard connection. This remains an outstanding issue which I hope will get addressed when their Drupal person gets back.
As I explored further, I found that their synchronize software only synchronizes content for non-blog nodes for the website as a whole. Since Drupal can have multiple blogs, SezWho has separate synchronization for each individual blogger, and that separate synchronization applies only to blog posts. In my case, I’m the only person using this Drupal site as a blog, so I didn’t set up a separate account for the site as a whole as well as for my individual blog here. So, it didn’t find any of my blog posts, just a few random other pages. I changed the synchronization program to synchronize blog posts for the main account, and now it shows all my posts as being synchronized. That is, at least, in the database. I had to tweak a few other places to force the blogid to zero to get other content to show up, and even with that it is spotty, either lagging or failing, and not managing to handle comments at all.
Later, I tried tweaking parameters another way, adding my Optonline email address to my SezWho profile and setting up a separate blog on the SezWho profile for my blog entries. Convoluted. Also, it hasn’t made any apparent difference.
Oh well.
General discussion
So, now I’m tied into three different comment systems. If you follow me on FriendFeed you can add comments there. I’ve tweaked Drupal to pull in those comments. There is a little bit of a lag. I like the way FriendFeed integrates with all the other life streams. I just don’t like the lag, or the difficulty of finding a place to add a comment initially.
You can also use Disqus. It seems to work pretty well, but for some reason, it is flagging some very old content as new. I’m not sure why that is happening. However, the comments can be added from the Drupal site and it seems to work pretty well. A nice plus is that if you use Seesmic, you can add video comments. The downside is that comments are stored on their server, and my access and control of the content is limited.
Then, there is SezWho. What is nice about SezWho is that they are supposed to integrate with the Drupal comment system, so comments stay part of Drupal. I can control them however I wish. The downside is that SezWho just doesn’t seem ready for beta testing.
So, for the time being, you’ll have different options for adding comments. None of them are perfect. All of them, hopefully, will be evolving to be better systems in the future.
More Alexa Bashing
Submitted by Aldon Hynes on Sat, 07/19/2008 - 21:45Turnip of Power has a blog post up about Alexa as a random number generator.
They write: Now Alexa has changed their algorithm, making it worse than useless. I’m surprised my site doesn’t record a negative score seeing how off base their estimates are.
Well, I thought I should check to see how my site did during my vacation. Sure enough, both Google Analytics and Quantcast showed my traffic drop to about a quarter what it was before I left for vacation.
At the same time, Alexa has shown a significant increase in traffic to my site.
So, I think that Turnip of Power is wrong. Alexa isn't a random number generator. It is showing a strong negative correlation to actual traffic.
UPDATE: This is a test update.
Playing with Laconi.ca Federation
Submitted by Aldon Hynes on Sat, 07/12/2008 - 08:21Over the past week, I’ve been spending a lot of time playing with Laconi.ca, an open source microblogging platform.
One of the things most interesting about Laconi.ca is the ability of servers to share content with one another. The mothership laconi.ca server is identi.ca. I’ve set up my account there to subscribe to accounts on other servers. In addition, I’ve set up my own laconi.ca server and subscribe to identi.ca from that server.
Word of warning. The ability to subscribe to and from different servers is still fairly unreliable. Many of my attempts to do remote subscriptions failed. In fact, the only way I managed to subscribe to my server was to turn on debug mode in hopes of figuring out why subscriptions were failing. It figures that subscriptions worked when I had debug on.
Anyway, here is the quick way of subscribing to a remote server. When you find a person on a server that you want to follow, make sure you are not logged into that server. If you are logged in, it will subscribe your local id to the user you want to subscribe to. When you are logged out, click on the name of the person you wish to subscribe to, and click on the subscribe button. You will be asked to enter a profile URL. Enter your profile from the server you want to subscribe from. As an example, my profile on identi.ca is http://identi.ca/ahynes1 on Orient Lodge it is http://micro.orient-lodge.com/ahynes1 If you aren’t currently logged in on the remote server, it will ask you to login. Then, you will be asked to confirm the subscription request.
If this works properly, you should be subscribed to the remote user. As I noted, too often, it doesn’t work properly, but that is how you can test it.
To get a further sense of where things are, you can look at a person’s subscriptions and subscribers. If your browser displays link addresses, mouse over each avatar in the subscribers or subscriptions to see if any of them point to remote servers. Check out mine on identi.ca and you’ll see several remote subscriptions and subscribers.
Why is this important? There are a lot of nice things that remote subscriptions can do. One person is creating a sports oriented laconi.ca site. I could subscribe to his sports oriented messages there, from identi.ca On my own site, I could subscribe to a particular subset of people on the identi.ca server so, when I view my identi.ca feed, I see everyone I’ve subscribed to on identi.ca, but when I’m on my development site, I see only those messages related to development. I’m sure that many of you can come up with other interesting use cases for federate servers.
Well, that’s it for now, I’m about to hit the road for a week, and expect to have very limited access. I’ll be working more on this when I get back.
EntreCard Highwater mark
Submitted by Aldon Hynes on Sat, 07/12/2008 - 07:33Okay, I did it. I dropped 300 EntreCards each day for 30 days.
Quick Laconi.ca update
Submitted by Aldon Hynes on Fri, 07/11/2008 - 14:51dewaldp came up with a fix to the .htaccess files for Laconi.ca that looks like it fixes a problem that I, and others, have been having.
@evan The (\d+) and (\w+) in htaccess didn't work on my Apache server. Had to change both to ([^/.]+)
I’ve changed that in the .htaccess and htaccess.sample files in the tarball. If you want to give it a try, feel free to download the tarball and copy the new .htaccess file into your production directory.