Well, Twitter finally went and did it. They killed their search widgets. All the search widgets stopped working on my web pages today. 🙁 They’ve been planning this for awhile: Deprecating widget settings – Announcements – Twitter Developers . The following pages are now missing their widgets: my Weather, NASCAR, and Entertainment Page, as well as the EverQuest II search at Mysstie.
So, for now, all I can do is provide links directly to Twitter, like #okwx OR #okfire OR #okquake – Twitter Search. Blah… Sigh.
The only noticeable thing I did to my main website since adding links to my Winamp Skins on the Winamp Info page, was adding a new Twitter widget to my Entertainment page in the TV Show section. It looks for all the tweets I’ve sent with the #TV hashtag. I figured that’s the best way to indicate what shows I am watching since GetGlue/TvTag shut down. Yeah, I know I’m the only one that gives a flying fruit cake about it.
Updated the blog to WordPress v4.3.1 which was a security and bug fix. Did the usual backing up of the database and file structure before applying the update. Then added my various code tweaks back in.
Updated both of my galleries (mine, Mysstie’s) to Zenphoto v1.4.10. Followed their upgrade instructions and backed up the themes and zp-core directories as well as the database before copying over the new files. I then used Windiff and code comparisons in PSPad to integrate any new changes in the default Garland theme into my custom Garland theme.
Patched the Pelicar Forum to SMF 2.0.11. Like everything else, backed up the database and files first.
I added a EverQuest II Legends of Norrath Loot Card Links page. I just wanted a quick way to view the various loot card pages specific to EverQuest II. Actually, I guess I added that at the end of August. Oh well, LOL.
That’s all I can think of for now.
As some of you might know, EverQuest II allows you to Tweet and post updates to Facebook via its EQII Share interface. The problem is, if your tweet message is too long, it will fail with some cryptic error in your chat window. While the EQII Share dialog window shows a character count, it does not take everything into account. Here are some additional things to consider:
- Every tweet contains the automatically added #EQ2 hashtag. Along with the additional space character to make ” #EQ2″ that’s 5 characters added to the tweet.
- If you have your character’s name set as a prefix in the EQII Share options, this needs to be counted as well. For example, if I use the name Krysstie as a prefix (8 characters) then a total of 10 characters will be added to the tweet as “Krysstie: “. You must count the added colon and space that comes after the name.
- If you include a screenshot with your tweet, this is another 21 characters taken away from your message. 20 for the URL itself and 1 character for an additional space. The URLs will be something like: http://t.co/OTgeCCFg which happens to be a screenshot one of my characters took.
So, in the case of Krysstie, my message in the dialog can not be more than 104 characters if I include a screenshot. 10(name) + 104(message) + 5(#EQ2 hashtag) + 21(screenshot URL) = 140 characters. If I don’t included a screenshot, then my message can be 125 characters.
I’ve sent feedback from within the game to improve the dialog to take these things into consideration when calculating the character count; however, with the Chains of Eternity expansion just about to be released, I’m pretty sure it will be way down on their list of priorities. Anyway, hope someone finds this tidbit of information useful.
Here’s October 2012’s list of changes changes to my websites.
- Friday, October 26, 2012
While I was trying to get a new version of Apache (2.2.23) and PHP (5.3.18) installed and working on my system to better match what Surpass Hosting upgraded my server to on the 23rd, I noticed that I had a slightly newer version of the Inception Blu-ray page than had been uploaded. It now has the back-cover image and properly sized player to match the trailer’s actual dimensions. The things that happened concerning the server upgrade and me trying to get these newer Apache and PHP versions installed and working would probably warrant a separate post.
Suppose I should change the published date on this post to match the latest date on it. Uhh.. maybe not.. it changes the permalink for the post as well, breaking the old link. Better change the published date back to the original LOL. Hrmm.. food for thought with these posts. I know what to do next time. Make sure I change the permalink to contain just the month of the post and not the day. Actually, I can’t do that either, at least not easily. I’d have to manually change the permalink in the database. Ehh.. I’ll think on the matter.
- Wednesday, October 17, 2012
Decided I would try out Twitter’s new Embedded Timeline widgets. I’ve added this newer version to both my main website and blog. I also decided to test out a #NASCAR search widget on my NASCAR page. At the moment I’d call them a work in progress. For example, I’ve defined the link color to be blue or #0000FF for the widget on my main website and they do show as blue in Firefox; however, they don’t in IE9. The #NASCAR search widget is also missing a lot of tweets that a normal #NASCAR search shows. I’ll give them the benefit of the doubt for now in case there is some behind the scenes work still going on that I’m not aware of or some setting that I need to tweak. If it doesn’t start to work better in a few days then I’ll probably get rid of it.
If you’re like me, you could probably careless about the social media chat widget thing that is to the right of the NASCAR RaceBuddy and/or Media Center video streams. I do my chatting in a separate Twitter tab within the browser or a separate Twitter application such as TweetDeck. Not only is the chat in these widgets less than desirable at times, but it also seems to cause the video streams to constantly lag and start/stop when the chat widget updates and scrolls items down/up. This is the primary reason I decided to see if I could stop the chat widget from loading in the browser. You can always move or resize the browser window to hide it if that’s all you want to do.
Success! No more chat widget on those pages and the video was much smoother afterwards. Note: this will affect any webpage that uses the same script to display a similar chat widget.
I haven’t tried it yet but I suspect adding an entry to the Windows’ HOSTS file for cdn.gigya.com to point to 127.0.0.1 would have the same effect and would prevent all browsers from showing the chat widget (or anything else associated with that sub-domain).