Sure enough, Dan Zarrella over at danzarrella.com had. He wrote one for Tweetbacks, and then expanded on it with TweetSuite. So I gave them a shot.

I started with Tweetbacks on the FreeformFrog.com Blog and everything seemed to be working fine – until one day when the Tweetbacks stopped. It just stopped finding them – even though I knew they were getting tweeted – because I was using Ping.fm to syndicate my blog posts to the appropriate social networks.

I gave it a couple weeks, and then decided I was going to fix it. I was tired of not having my TweetBacks working – especially during my efforts pushing a Social Networking campaign at job.

So, I added @danzarrella, and asked…

@danzarrella do you have plans to integrate ping.fm posting in TweetSuite? If not, mind if I take a crack at it?
from @neotsn at 4:32 PM Mar 18th from web

A few minutes later, I got a response…

@neotsn go to town
from @danzarrella at 4:34 PM Mar 18th from TweetDeck in reply to neotsn

Excellent…now I had his blessing to hack his codes. And so I have…

The download is coming soon

I have to get my Ping.fm API Key approved before anyone but me can install the plugin.

And now I present to you a general overview of what I wanted to accomplish, and how I did it. (Please note, this is a GENERAL overview with some examples – it’s not meant to be a how-to, so don’t try to just copy/paste the samples – there is much more to do than can be explained here). Let’s get started…

Objectives…

1. Make it post through Ping.fm – I syndicate all my stuff through twitterfeed.com and it pushes everything out through Ping.fm for me. Upon further investigation, I noticed that TweetSuite used its own publishing code to push out the updates – after it created its own shortened urls and attached them. So of course it would never find my updates – it didn’t know what urls to search for, because it didn’t create them.
2. Make it find my tweets that were pushed through Ping.fm – After realizing that it stopped searching for blog titles and started searching for the shortened urls as the unique identifier on the web, I realized that I needed it to create my urls and push them out with my Ping.fm update text. That was the only way to let TweetSuite know that there were tweets out there about my blog, and obtw here’s the link.
3. Clean up some of the things that were a little messy – Once I got poking around in the code, I noticed that it some parts of it were written a little redundantly, and in order for me to maintain understanding of what was going on, I needed to clean it up a little.

Let’s Code…

Well, for starters, to accomplish #1, I had to write a function that would validate the user’s app key with Ping.fm:
{code type=php}
/* [[Neo]] */
//BEGIN Ping.fm functions
function pingfm_verify() {
// request app key verification
$ch = curl_init();
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_URL, ‘http://api.ping.fm/v1/user.validate’);
curl_setopt($ch, CURLOPT_POSTFIELDS, Array(
‘api_key’ => get_option(‘tweetsuite_ping_api_key’),
‘user_app_key’ => get_option(‘tweetsuite_ping_app_key’)
));
$output = curl_exec($ch);
// update database with response
if (preg_match(‘/OK/’, $output)) {
echo ‘ <strong>Your key has been verified.</strong> Your can now post to your
<a href=”http://www.ping.fm” target=”_blank”>Ping.fm</a> account.’;
update_option(‘tweetsuite_ping_keyVerified’, 1);
} else {
echo (‘<strong>Your key could not be verified.</strong>.’);
update_option(‘tweetsuite_ping_keyVerified’, 0);
return false;
}
}

// END Ping.fm Functions
{/code}
Just your basic curl function to contact http://api.ping.fm/v1/user.validate and pass the api_key and user_app_key to the api, per the API Documentation on user.validate. Depending on the response, store it to the database, and display the appropriate message.

Next, I had to implement the fields to make that happen. We’ll start with the database…
{code type=php}
/* [[Neo]] */
//ADDED:
add_option(‘tweetsuite_ping_api_key’,’333333333333333333333333333333333′);
add_option(‘tweetsuite_ping_app_key’,”);
add_option(‘tweetsuite_use_ping’,0);
add_option(‘tweetsuite_ping_keyVerified’,0);
//END ADD
{/code}
This sticks those fields into the wordpress database table “wp_options” where all the config values go. My developer’s api key, a blank user application key, a field for the checkbox “Do you want to use Ping.fm?” and one for whether or not the user_app_key successfully verified.

Then I create the user interface for those fields (as well as rearrange the rest of the fields since these have to flow right to make sense…
{code type=php}
/* [[Neo]] */
//ADDED:
update_option(‘tweetsuite_ping_app_key’, $_POST['tweetsuite_ping_app_key']);
//END ADD

//tweetsuite_use_ping
($_POST['tweetsuite_use_ping']) ? update_option(‘tweetsuite_use_ping’, 1) : update_option(‘tweetsuite_use_ping’, 0);
{/code}

That part allows the database to be updated with the data from the fields below…
{code type=html}
<!– /* [[Neo]] */ –>
<!– BEGIN ADD –>
<tr valign=”top”>
<th scope=”row”>Ping.fm :: Use Ping.fm to publish new posts (via your default method)?:</th>
<td><INPUT TYPE=CHECKBOX NAME=”tweetsuite_use_ping” <?php if(get_option(‘tweetsuite_use_ping’)) { echo “checked”; } ?>>
<br /><b>["Send a Tweet when you publish" is required for this to work]</b>
</td>
</tr>
<tr valign=”top”>
<th scope=”row”>Ping.fm :: Your Ping.fm <a href=”http://ping.fm/key/” target=”_blank”>Application Key</a>:</th>
<td><INPUT TYPE=text NAME=”tweetsuite_ping_app_key” value=’<?php echo get_option(‘tweetsuite_ping_app_key’); ?>’ /><br /><?php if(get_option(‘tweetsuite_ping_app_key’)) { echo pingfm_verify(); } ?>
</td>
</tr>
<!– END ADD –>
{/code}
This is below the checkbox for “Send a Tweet when you publish a post?”…if that is checked, then if you check “Use Ping.fm to publish new posts (via your default method)?” and fill out the next field for “Your Ping.fm Application Key” then it will send your post details on Publish through Ping.fm instead of Twitter itself, appending the tinyurl associated with the post to your Ping.fm message. All this is done by editing the function that sends the tweets…
{code type=php}
function tweetsuite_send($msg) {
/* [[Neo]] */
//REMOVED:
//$prefix = urlencode(get_option(‘tweetsuite_prefix’).’ ‘);
//REPLACED:
$prefix = (get_option(tweetsuite_use_ping) and get_option(tweetsuite_ping_keyVerified)) ? get_option(‘tweetsuite_prefix’).’ ‘ : urlencode(get_option(‘tweetsuite_prefix’).’ ‘);
$msg = $prefix.$msg;

/* [[Neo]] */
//ADDED
if(get_option(tweetsuite_use_ping) and get_option(tweetsuite_ping_keyVerified)) {
$ch = curl_init();
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_URL, ‘http://api.ping.fm/v1/user.post’);
curl_setopt($ch, CURLOPT_POSTFIELDS, Array(
‘api_key’ => get_option(‘tweetsuite_ping_api_key’),
‘user_app_key’ => get_option(‘tweetsuite_ping_app_key’),
‘post_method’ => “default”,
‘body’ => $msg)
);
$output = curl_exec($ch);
} else {
//END ADD
$username = get_option(‘tweetsuite_twitter_username’);
$password = get_option(‘tweetsuite_twitter_password’);
if(($username) and ($password)) {
$url = ‘http://twitter.com/statuses/update.xml’;
$curl_handle = curl_init();
curl_setopt($curl_handle, CURLOPT_URL, “$url”);
curl_setopt($curl_handle, CURLOPT_CONNECTTIMEOUT, 2);
curl_setopt($curl_handle, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($curl_handle, CURLOPT_POST, 1);
curl_setopt($curl_handle, CURLOPT_POSTFIELDS, “status=$msg”);
curl_setopt($curl_handle, CURLOPT_USERPWD, “$username:$password”);
$buffer = curl_exec($curl_handle);
curl_close($curl_handle);
}
/* [[Neo]] */
//ADDED
}
//END ADD
}
{/code}
This starts off by swapping out the original urlencode() function for a conditional statement deciding if this is a ping.fm post or a twitter post. If it’s a ping.fm post, then we don’t want to urlencode() the prefix, because it sticks + signs where there should be spaces in the prefix to the title. However, if we don’t want to use ping.fm, then don’t mess with the original code.

Following that, it splits which method we used to post, based on the same criteria – make sure the checkbox is true for “tweetsuite_use_ping” and that the user’s app key is verified in “tweetsuite_ping_keyVerified”. If that’s the case, then post it through ping.fm – if any of that is not met, then go ahead and try to post it through twitter. If there is no username and password supplied on the options page, then we just won’t post anything.

Now…about the whole $msg – that part got skipped in the logic of everything. This was the tricky part, for me. Originally, I stumbled across an API Documentation page for the ping.fm method “url.shorten” and that was the very thing I needed – something to grab a ping.fm url, without passing it through ping.fm yet. However, I found out, after much frustration, that this method was mysteriously “depreciated” (which should be read as “edited off the page, and 404′d when you try to use it). But, I found another solution in the knowledgebase at Ping.fm…
{code type=php}
function ts_send_tweet($postID) {
global $wpdb;
if(!is_int($postID))
$postID = $postID->ID;

$table_name = $wpdb->prefix . “shorturls”;
$line = $wpdb->get_row(“select * from $table_name where postID=$postID”);
if($line->postID==$postID) {
/* [[Neo]] */
// ADDED: “*”.
$shorturl = “*”.$line->tinyurl;
$post = get_post($postID);
if(get_option(‘tweetsuite_send_posts’))
tweetsuite_send(trim($post->post_title).’ ‘.$shorturl);
}
}
{/code}
The article said you can prepend a * to the front of a url and it would not shorten it (in addition to the fact that they said they wouldn’t re-shorten any URLs 24 characters or smaller). So, I went with the * solution, because we’re already providing short URLs, but don’t want to risk the functionality in future updates to allow for custom url shortening services.

And that accomplishes both #1 and #2. We have the TweetSuite posting its updates through the Ping.fm API, and pushing a shortened url out with the post. TweetSuite then becomes aware of this url at publish, and stores it in its database. Then the cron job that runs every 5 minutes searches on any version of the URL that was stored and pulls back all the entries from the search.twitter.com Atom feed – parses them, and updates the database with them.

The rest of the stuff I did in the plugin was merely cleaning up…for example, reading the shortened urls from the Atom feed. The original code was:
{code type=php}
if(stristr($tweet, ‘http://bit.ly’)) {
if(strstr($tweet, $bitly)) {
$add = true;
} else {
$add = false;
}
}
{/code}
Because the urls are using alphanumeric sequences to track what link is what – and the url’s are case-sensitive, it was returning links that were not related to the post. For example, I got someone’s tweet about Rush Limbaugh because the bit.ly url (“http://bit.ly/fyhz”)was the same letters, but in a different case then my original “http://bit.ly/FyhZ”. So I changed the order of the search, did it for all the services currently supported, and cleaned up the code a little:
{code type=php}…
if(strstr($tweet, ‘http://bit.ly’)) { $add = (stristr($tweet, $bitly)) ? true : false; } else {
…
{/code}
The function strstr() is not case-sensitive, and that’s ok for a search on the domain name – we want anything that looks close to “bit.ly” to return positive. However, once it does, it’s imperitive that we use the case-sensitive stristr() function to return a positive result only if the full url matches what we have in the database case-for-case.

Wrapping up…

I made a couple more additions to the code beyond that, some of them required for functionality, some of them for cosmetics. I’ve submitted my plugin version to Ping.fm to approve it, and take my Developer’s Key out of “Pending” status. Once that’s done, I’ll send it off to Dan Zarrella to take a look and see how he wants to move forward. Then I’ll be able to post the plugin for download (definitely here, but also on the WordPress Plugin directory.

Continuing on…

I have read through the comments on Dan’s blog from the people, and have taken note of the things that they are asking for. After reading the code, he had already been working on some of the features. There are 5 main ones that people are asking for, and I’ve already done one of them in this release:

1. TweetThis link opens in a new window.
2. AutoUpgrade via WordPress Plugin Directory
3. Allow customized URL Shortening Services
4. TweetThis links for pre-installation posts
5. TweetThis links on the home page.

I’ll be looking more into the other options and see what I can do.

One More Thing…

This post was syndicated through the TweetSuite + Ping.fm plugin .

Technorati Tags: beta, dan zarrella, database, internet, MySQL, PHP, Ping.fm, site, syndication, tweetbacks, TweetSuite, twitter, WordPress

Well, I have an answer – and this example will use the Digsby Instant Messenger client. (I’ll get technical after the story below.) Here’s a little background…

I’ve been using Trillian for my instant messaging software of choice since it was version 0.74a back in 2001. And I have never had any problems with it. It’s been a great tool to keep the 20-odd screennames I had back in the day all organized with their appropriate buddy lists joined or separated as necessary. Fortunately, I was invited to use their new Trillian Astra beta program for the past couple years. Using the Astra alpha/beta releases has been nice, as all the features from the Pro accounts were available for testing – that was, until Build 98, when they turned on the Basic/Pro distinction. Much to the chagrin of the beta testers, there was a major uprising because of this, with a lot of focus by the users being put on Chat Logs and server-side synchronization. To the praise of Cerulean Studios, they reinstated the Pro functionality until they gave fair warning in Build 99.

One user mentioned Digsby as an alternative to Trillian. I’ve used other clients like meebo.com as a cross-platform web-based chat, and Pidgin when I used Linux on my laptop (and even tried the Windows version recently). However, Digsby is the only one that provides the closest functionality to Trillian with the many social networks that it connects you to – with the somewhat-noticeable lack of MySpace IM. (But who really uses that anyway?)

Ultimately, I gave Digsby a shot on my laptop, running Windows 7 Beta 1, and it seemed to serve its purposes very nicely. I don’t use the laptop for anything beyond quick internet checking with Google Chrome, collecting my emails in Thunderbird, an alarm clock using Songbird, and sending IMs.

Later, when Trillian released Build 99, I wasn’t thrilled about the limited Basic functionality I was relegated to – but also am not prepared to spend the nominal $25 to upgrade to Pro just yet. (Maybe I will this summer.) So, I installed Digsby at work, and on my desktop computers, and was back in business.

I noticed that once I installed Digsby on the other computers, it migrated my accounts, buddy lists configuration (i.e. meta contacts), and most of my preferences over. It wasn’t until I discovered there were also customizable themes and when I had to look through chat logs on 3 computers, that I noticed a need for further synchronization.

So I set out thinking of a way to do this…and that’s where we start.

I’ve been using Live Mesh since it was Microsoft Groove in Microsoft Office 12 Beta 1. And I thoroughly enjoyed the functionality of being able to keep a single copy of my website code (since I run multiple sites on the-spot.network), and be able to work on them at work, at home, or with my laptop outside of Jamba Juice in Sundance Square, Fort Worth, TX.

You can do this with both Groove or Mesh, but for the purposes of this article (since I don’t have Microsoft Office installed on the laptop), we’ll do it with Mesh (plus Mesh is free, Groove is part of Office 2007).

Warning: Please read before you proceed.

I had to do this SEVERAL times before it actually worked. By “SEVERAL” I mean that I had to reinstall Digsby a LOT because I didn’t do it correctly, or the permissions weren’t setup properly before I tried syncing. If I were you, I’d try something simple first, like creating a folder in Program Files, and sticking a txt file in it, and see if you can get it to sync. Once you’ve followed the instructions and learned how, give it a shot with the program you have in mind.

Ok, you can continue.

Step 1: Sign up for Mesh.com

Step 1: Sign into or up for Mesh.com

Assuming you’ve already got a Windows Live Account, sign into the  Live Mesh website, with your Windows Live ID. Once you sign in, you’ll be taken to your Live Mesh Devices page.

Step 2: Add your computers to Mesh

Step 2: Add your computer to Mesh

From the Devices page, click Add Device. Use the drop-down menu to select your computer’s operating system, and then click Install. This downloads the Live Mesh software to your computer. Once you’ve installed the software, you’re ready to begin synchronizing folders between: your computer and your Live Desktop, your computer and other devices in your mesh, or your computer and a friend’s computer.

Step 2a: Your Live Mesh device window

Do Step 2 on all the computers you wish to sync.

Step 3: What do you want to sync?

Mesh gives you about 5GB of cloud storage space. Because everything you sync between computers is also stored in at the Live Mesh website on your “Live Desktop”, the cumulative sum of all the files you want to keep synchronized cannot exceed 5GB.

For my example, I want to sync my Digsby themes so that I can use my them on whatever computer I am using. So, I navigate to the Program Files folder, and find the Digsbyresskins folder.

Step 4: Setting the right permissions

First things first though – if you’re using Windows Vista and have the User Access Control activated, then you’re not going to be able to write anything to this folder without giving Administrative Privilages. This will prevent Mesh from syncing the files and folders to anything your Program Files directory. So let’s fix it…

1. Right click on skins, choose Properties
2. Click the Security Tab, and hit the Edit button
3. Hit Continue on the UAC window, click the Add button
4. Type your username and domain if needed, and hit OK
   
5. (***If, in Step 8, you don’t see any files showing up, you might need to start over and add the “all user accounts” to have full permissions by selecting “<localhost>users”, and giving it Full Control. Otherwise, go ahead and set that permission now, if you don’t anticipate any security issues in doing so.***)
6. Check the Full Control checkbox, and hit OK, and hit OK again to close all the windows.

Do this same thing on the other computers you’d like to sync with, adding the appropriate username for your account on that particular computer. Now you should be able to write files to that folder without needing approval.

Step 5: Add your folder to your Live Mesh

Step 5: Add the folder to your Live Mesh

Now you’re ready to add your folder to your Live Mesh:

1. First, remove everything in the folder you want to use. In my case, I cut all the theme folders in skins.
2. Right click on skins, choose Add folder to Live Mesh.
3. You’ll get a window that pops up, asking what you’d like to name the folder. I just used “Digsby-skins”. Hit OK.
4. Paste the themes back into skins and let them sync.

Step 6: The progress meters

Step 6: Let the folder Sync to Live Desktop

My entire Digsby installation is about 60MB, with the themes making up about 3MB of that. Depending on what you’re actually syncing, this size will vary greatly – and so will the time it takes for everything to upload. If you open the folder you’ve chosen to sync, you’ll see a sidebar pop out of the right hand side of the window that shows the progress of your device.

Note: You’ll only see the devices that you’ve told to sync with this folder. Mine shows my laptop because I’ve already done this, we’ll get to adding the other devices next.

Step 7: Icon to setup new Mesh folder

Step 7: Setting it up on the other computer.

For this to work, you should have the same program installed on the other computer. This is not meant for sharing a program from computer to computer – just accessories like themes, plugins, settings, etc.

To set up your other computer, start over with Step 1 – install Live Mesh, add the computer, configure the Security settings, cut the contents from the folder you’re going to sync.

Once you’ve added this computer to Live Mesh, you’ll see a desktop icon, in my case “Digsby-skins”.

1. Double click the icon to get the setup window
2. Click Browse and Navigate to the directory you want the sync’d files stored in and hit OK

You’ll want to give it some time to download the files that the source computer has put up on the Live Desktop. You can base that timeframe by the activity of the Progress Meters on the right of the directory window, as the image in Step 6 shows.

Step 8: Conflict Notification

Step 8: Add any files from the secondary computer to be sync’d

Once you have finished syncing the files from the source computer, you can cut/paste the files you moved on the secondary computer, back to their original location. This allows you to Overwrite any files that might be duplicated on both machines, instead of having to resolve any conflicts manually.

After you have copied the files on the secondary computer back to their original location, check to see that they are showing up on the primary computer. If they are, then everything is working like it should.

Step 9: Testing the synchronization

When everything is finally sync’d back between both computers, give it a test. You should now be able to load your program in both places, and if you happen to add a new plugin in one location, it should be available on the other computer soon thereafter.

That’s that…

That is how I have set up my Digsby installation to share Themes, and how I will instruct one of my coworkers to sync her Photoshop brushes between office and home. Let me know what you’re using it for in the comments below.

Technorati Tags: cloud computing, computer, digsby, how do i set up live mesh, How To, internet, live mesh, microsoft, network, plugins, sync, synchronization, theme, Windows

1. Open the ports

2. Download the Dedicated Server Package.

3. Install the Dedicated Server Package.

4. Create your server’s GameSpy Account.

5. Create the configuration script.

5b. Optional: Edit the DefaultGame.ini file to allow for map voting.

6. Create the batch file to load the server.

That’s all there is to it. At least, that’s all there was to mine.
Happy Fraggin’!

Update: I don’t run my server much anymore – but when I did, it worked, and I followed these instructions. I can’t provide individual support for everyone that tries to create a server, but doesn’t figure it out by these steps. I documented everything I did, step-by-step, and put them here – I didn’t do anything extra or different from what’s here. So if you have trouble getting your server up, you’re just going to have to play around with it like everyone else did before you to get their server up.

Blogged with Flock

Tags: ut3dedicated server, ut3, dedicated, internet, server, game, unreal tournament, unreal, tournament, video game, video, game, configuration

Technorati Tags: Admin, bot, configuration, configuration script, dedicated, Firewall, game, gamespy, internet, internet server, LAN, localhost, master server, ports, server, server port, server setup, tournament, UDP, unreal, unreal tournament, user, ut3, ut3dedicated server, video, video game, Windows

Originally, I set up the server to be a web server with php and sql capabilities. Then I realized I needed to FTP files to the web server, so I installed FileZilla Server. Once that was done, I started working on the webpage for tsnlocal.net. I got it up, and then wanted to play around with some other type of server, and decided on a Jabber server for instant messaging. I installed Wildfire.

Wildfire is extremely easy to setup and install – so once I finished that, I looked for a Jabber client. My first choice was a VoIP client called Jabbin, but I couldn’t get it to connect to the server – probably because I don’t have a VoIP Protocol on the server to support it. So I went with what we use at work, Exodus. It’s a fairly functional Jabber client – with chat rooms, IM rosters, subscriptions, and file transfer…and a bunch of other stuff, including plugins.

Once the Jabber service was set up, and I figured out how to connect to it, I realized that telling people to use my dyndns domain name was not going to work. So I had to figure out how to get my Godaddy.com domain name to link directly to my IP address. But, come to find out, I have to have a Top Level Domain for an IP address, or my dyndns must be a nameserver registered with the NS Registry, in order to use it as a nameserver. I spent 2 days setting up BIND on Windows XP (because there was very little help on the internet for how to do it). Then I jacked around with the Total DNS control settings on godaddy, and got the webserver to work like it should – almost.

So now you can join the jabber server with yourname@jabber.tsnlocal.net. Now that I had that working, I noticed that there were email settings like pop.tsnlocal.net and smtp.tsnlocal.net that could be set up, so I decided to look into running my own email server. I got in #bloodshotgamer on irc.gamesurge.net and asked some of the tecky people I talk to in there what they’d recommend. Duck-Lap recommended qmail for linux, but mentined MailEnable for Windows. I was hoping for an IMAP service so I could run the webpage side of it, but that was not included with this. I might upgrade the service to something new later on, but for now, this was easy to install, and has easy administration, which is what I’m looking for since most of these other services aren’t critical to the function of the server. BIND was about the only thing that was hell to configure…everything else was easily figured out once I had the info and a general grasp of what it does and how it does it.

So now, [[Oracle]] does these things:
- Web Server (Apache, PHP, MySQL)
- FTP Server
- DNS Server
- Email Server
- Jabber Server
- TeamSpeak Voicechat Server
- Hamachi server
- Google Desktop distributed indexing server for the hamachi shares (the essence of tsnlocal)
- and a keep-alive for the dyndns service linking my IP to the dynamic domain

That’s a lot for a little box…but I’m not done yet – I need to put ssh on it so I can telnet into it. I’m sure there are other things that I will find to do with it as time goes on too.

Technorati Tags: bind, chat rooms, DNS, dns control, domain name, dyndns, Email, email server, email settings, exodus, FileZilla, FTP, godaddy, hamachi, instant messaging, internet, Jabber, jabber client, jabber server, Jabbin, nameserver, PHP, pop, server, setup, smtp, sql, sql capabilities, VoIP, Web, web server, webpage, webserver, Wildfire, Windows, [[Oracle]]

After working on some graphics for tsnlocal.net, and creating background for the [[Oracle]] server and my computer, I’ve begun work on the next theme for tsnX: tsnX-dark. This one is a bit tricky because there is a combination of dark and light going on the same page that will require a different set of coding for the template to keep everything visible.

I’ve also been sparked to start working on some more stuff by a simple task they gave me at work – create a webpage, without using Frontpage and stuff, to display a server-is-down message in plain html. So I did it, all in Notepad++, and was actually pretty impressed that I could write a whole page using CSS and html from nothing, without using a WYSIWYG editor – I guess it’s still true that I know how to do it, it’s just easier for design purposes that I use an editor….even though I still do the hard coding by hand.

Anyway, I’ve begun work on tsnX-dark, and am still working on tsnlocal.net and the [[Oracle]] server, to give it its own DNS server capabilities. If I am able to do that, then if [wizard] and I end up in the same house with faster internet, I’ll be able to host all my website from my own computers, instead of having to host them commercially.

I’m also going to restart the daunting task of creating the MySpot page…there is already one out there, but it’s just a simple New Posts search page…I have to get some other code in there and a new design on it to finish it up. I’m also going to make the server and user status on the tsnlocal page into an Auto-refreshing portion of the page via AJAX. Then I’m revamping thepizzy.net homepage to reflect the tsnX design and update the information that has apparently not been touched since tsn went down earlier this year.

It just takes the proper motivation and desire to work on this stuff – because if you’re not totally into the job, then the product is going to suck if you finish it. So look for changes.

Technorati Tags: ajax, computer, CSS, DNS, dns server, Frontpage, html, internet, myspot, oracle server, search, server capabilities, ThePizzy, tsn, tsnlocal, tsnX, webpage, website, WYSIWYG, wysiwyg editor, [[Oracle]]