By alex, on November 20th, 2011 I’ve been neglecting this site in favor of another site of mine, which has taken up quite a lot of resources – I’ve setup an online silver jewel shop, and it’s taken quite a bit of my time up till now getting things configured and up and running.
That plus a death in the family has led to this site being neglected the last few months.
Just to let those people know who still drop by : I’ve not given up on creating websites like twitalytics, creating tools for the internet, but unfortunately, these websites are currently not a viable business for me – I’m alone in setting this up, and that means a lot of time going in it before I have something basic working like twitalytics, which honestly I have to admit still needs lots of refinement.
I’ve therefore decided to reprioritise : first get a business up and running, and then try my hand again at creating interactive websites that are usefull.
By alex, on March 2nd, 2011 I had a bit of a major problem with Twita (the new name of twitalytics.dataconnect.be, as somebody else has started using twitalytics). Basically I was consuming too much sql and cpu resources on the shared server I was running my cron job on.
The cron job is back up and running, with a reworked sql in it that seems to be loads lighter than what I originally wrote. Apparently using count() to just check if some field and value exist in your table does major lookups to your table, even with indexes set and everything. 
The admin guys have checked their logs and I have checked mine, and it seems we can ‘let the beast go!’ again.
* Let the beast go is a famous phrase from our firstwhile premier Jean-Luc Dehaene while visiting the US and riding on a mechanical steer in a tourist attraction.
By alex, on December 26th, 2010 Darn it – last week I changed my crontab list so that I would be notified if an error occurred while running cron jobs, and I now get a MySQL warning ” Data truncated for colum location”.
I had reserved 40 characters for the location field of a user, but it seems that with the special characters allowed in that field, sometimes it’s going over that and the field is truncated. A database search through the already stored location fields shows a few entries where the max of 40 chars is reached, so I’ll be changing the length to 50.
Frustratingly, I can’t really seem to find a good overview of the length of all the fields that are returned by the twitter JSON response. The twitter search documentation is a good start, but it seems far from complete…
By alex, on December 18th, 2010 
Number of tweets per day for the hashtag twitter keyword #leweb for the date range between Nov 27, 2010 and Dec 19, 2010. I might have missed some at the top as I only check hourly, but it shows a clear indication of number of tweets sent before and around the event.
By alex, on December 13th, 2010 My hourly twitter search updates are threaded, and sometimes hang. For now I check this manually, until I have some time and inclination to look into this and solve the riddle of this.
I don’t check every day – so I’ve added a daily cron job now that sends me a status email of the program working (or not)…
|
A sample text widget
Etiam pulvinar consectetur dolor sed malesuada. Ut convallis
euismod dolor nec pretium. Nunc ut tristique massa.
Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan.
Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem,
suscipit in posuere in, interdum non magna.
|
|
