The Quest for DSL

December 16, 2005
So after much trial and tribulation, my DSL service FINALLY went on.  They had told us December 9th, but it wasn't live when I tried it then.  Mary Lou called them a couple of days ago and they told her sometime before December 27th…a date they referenced in an email from the DSL group even though the web and phone check system still said the 9th.  Anyhow, I worked all night on Wednesday which allowed me to work from home on Thursday afternoon.  Before dialing up a connection I popped the phone line into the DSL and was happily greeted with a blinking "DSL" light.  I did what I call my "DSL Happy Dance" (it's not a pretty thing folks), ran the installation routine that sets up the account and I was good to go.  Goodbye crappy dialup service from LocalNet and their bad DNS issue and constant disconnects!

—

I've suffered through a return to dial-up Internet access for the past several years.  I've now gotten the ball rolling on switching back to a high speed connection -or have I…

Several years ago I had a high speed Internet via my cable operator.  But due to one of my many unemployment incidents I got rid of it to save some money.  Then a couple of years after that I cut my cable service to just the local broadcast channels for the same reason.  As a sidebar, I have to say we really don't miss it that much and at $7.00 a month it's hard to not be happy with the decision.

Anyhow, my life has finally rebounded to the point that I'm gainfully employed and I started on convincing my wife of how nice it would be to have a high speed connection again.  She reluctantly agreed.  But because we've cut our cable service to the minimum we can no longer get a cable ISP connection without upgrading to the standard service again.  I don't have the need or desire to return to a $80-$100 a month cable bill so the answer was easy: DSL.

Verizon offers DSL in my area and I know others around my neighborhood have it.  Thus it was a viable option.  I'm not currently a Verizon customer so in order to get DSL I had to also our switch phone service over.  With the cost of my current phone service and dial-up access it's only going to be about $20 a month more.  So the call was made, the switch was on…

For about 2-1/2 weeks that is!  The cut-over date came and went and nothing happened.  Calling Verizon revealed that our order had been cancelled.  Why?  Blah, blah, blah.  In short they blamed my current provider for not releasing the line.  This proved to not be true.  (I guess I should also note that they lost our initial order right after it was entered because the rep didn't save it.  He had to call back and reenter it again.) Thus the order was reentered (again) and I awaited my new cut-over date.  The catch here was that they wouldn't send out the DSL package until we were ported over and they could verify DSL availability.  So the second cut-over date came and went without anything happening (again).

Once again the order was cancelled!  As it turns out they had been enter the wrong code on the order!  I guess at this point I should also note the phone service is in my wife's name and she's the one that's been doing the leg work.  Me?  I've been doing the whining and complaining at home! ;)  So being the shrewd businessperson that she is, she spoke to a supervisor and squeezed them for a free month's service and a waived "installation charge".  This is on top of the initial discounts and what not she had gotten out of them the first time.  So now we are (hopefully) entered into the system and should be switched within the next 10 days.  Color me skeptical…

It just amazes me how hard companies will work to NOT take your money.  Hello?  If I had another option I would pursue it, but I don't.  Thus I still hold out hope that this will come to pass and I shall be surfing the Internets with appropriate response times!

The Entity IV: In The Black

The Entity IV: In The Black

I'm looking down on a little boy
Don't get too close now, you'll fall inside
Go away now, don't play around
You didn't listen, got drawn inside
Now I hear you, you're just a mind
Like a story, you've heard before
Didn't want to believe it, it's so absurd

You didn't want to listen
You wouldn't take my words
You didn't see me, so you…
Took the chance

Now you're nothing, just a mind
Gave you warning, a second chance
It'a simple story, you can't go back
Ain't nobody, nor a second chance
Isn't anything that can take you back

Just a thought now, in the air
Learn your way now, it's simple fact
Just a mind boy, an entity
Free to go now, just enact your plan
Truly fact now, you're in the black


4/26/1982

PolarBlog V1.6.2 (Fungus Gnat) Released

PolarBlog V1.6.2 (Fungus Gnat) has been released.  This release fixes a serious comment deletion bug and another minor comment posting bug.

Enhancements

  • None
Bug Fixes
  • Deleting a comment deletes all top level comments! This  was being cause by a bug in MySqlDb::stripArray() where nested arrays were not being handled properly.
  • The auto-linebreak option on comments does not work.  This has been corrected.
Configuration Changes
  • None
See the PolarBlog Changes file for more information.  Please see the PolarBlog Upgrading documentation for information on upgrading your installation.

This release is named "Fungus Gnat" because this was an annoying pest of a bug!

PolarBlog Comment Delete Bug

I've just found that a bug fix I made in V1.5.2 (Groundhog)…

"Deleting a single comment destroying all root level comments!  A serious array data mishandling issue in the DB class has been corrected.  Nested arrays are now handled properly."

Has NOT been fixed and appears to still exist!  I know this because I've once again trashed my comments table! :(  So until I can extract it from the backup (probably tomorrow), my comments on most entries will be missing.

Consider this your warning not to delete comments until I get this fixed.  An easy work-around is to edit the offending comment and disable the display option.  Generally this is what I do even with spam comments, but was fixing another comment problem and stumbled upon this while deleting a duplicate comment I created.

I don't have an ETA for fixing this, but I will likely issue a new release to address just this problem once I do fix it.  Sorry.  I hope this hasn't/doesn't hit you too!

ig: The Google Drug

Several weeks back I was led to Google's new "Individualized Google".  Actually I don't even know if that's what it's called, but that's the best I can come up with from the "ig".  (Feel free to correct me if you know otherwise.)  Anyhow, I played with it a bit and found the drag and drop aspect of it to be really cool, but beyond that I didn't really have a need.

Then a couple weeks after that I had some more time to revisit it and play with it some more.  And the verdict?  After about a month of use, I'm addicted to the new Google drug!  I haven't yet made the switch there as my homepage, but I'd say it's not that far off.  Currently I use my Links page and also used to use my RSS Feeds page often.  But I've created a lot of FireFox bookmarks that let me quickly navigate/search for things on the sites I visit the most, type addresses in directly or simply Google my way through life.  This has made a portion of my Links page obsolete.  And the contents of my RSS Feeds has largely been integrated into the new "ig" page as you can specify RSS feeds as part of the customization.  This works well, but I have had some problems with RDF feeds not working.  But most of the things I follow regularly do work.  Goodbye RSS Feeds page?  It also has a very nice weather widget and that has largely obsoleted my Weather page also!  But as winter approaches, that will likely get used again because my default zip also pulls in the current radar image for me.

And to further pound another nail into my personal website, yesterday I learned about Google Reader!  I only played with this for a few minutes, but it quite possibly will become my news reader of choice in the future…particularly if they give me a widget on my new homepage.

Hit me again Google, I need another fix!  ;)