Search results for

#Blog

#1 Click this link to see Blog page --> 08/12/2006

I have been working steadily on redesigning the redesign of the redesigned #Blog site. That’s one reason, with the exception of these meandering missives, why the site has been stagnate. I have decided not to go forward with the graphics intensive menu systems which take so much time to make and go with a JavaScript menu system. I will eventually get this thing working the way I want it to.

MjL

#2 Click this link to see Blog page --> 05/12/2009

I have discovered that something has gone haywire with my web site provider (again) this morning. I kept getting “flood” error messages and couldn’t comment. The flood protection is to keep some spammer from automating a spam flood to my web site —— it is a nice protection. Evidently the time server is screwed up somewhere and is causing comments to the blog to get bounced out. I have removed the flood protection to work around this but I am not happy because it leaves me open to spammers. You just can’t get good help anymore! Please send an email if you have run into any similar problems commenting on the #Blog. Sorry about that.

MjL

#3 Click this link to see Blog page --> 07/10/2009

My #Blog has been messed up for the second day in a row. Somebody at the web host site is adding php script to the bottom of some of the index files —— It appears they are trying to track usage or something.

These added scripts are bombing out my pages and I am getting tired of fixing it. Of course nobody at their end knows from nothing, so either they have a rogue programmer or I am dealing with some kind of hacker.

Isn’t that just swell!? Anyway —— if you get a blank page when you try the site just send me an email and I will fix it. Hopefully I will eventually find out who is messing with it and get them to stop.

MjL

#4 Click this link to see Blog page --> 11/03/2009

I notice I have a problem with parts of the #Blog again this morning and some things aren’t working right. I hope I can get them fixed without too many calls to tech support. One is too many.

MjL

#5 Click this link to see Blog page --> 11/03/2009

#Blog
Okay —— Just got off the phone with tech support and they have confirmed that some bonehead technician made “some minor changes in the background” that are reeking havoc upon sites, like mine, which use code to count files in a directory and page through those files such as I do with news photos and political cartoons.

I have edited those for today and have been told this “minor change” will be rectified. Somebody is always messing with something!

MjL

#6 Click this link to see Blog page --> 11/04/2009

My troubles with my #Blog were unfortunately intentionally put upon me by some idiot “engineer” at the web server who decided to turn off some functions of the file server which allow file identification and counting.

My first call early in the morning was answered immediately by some foreigner who assured me they “were working on the problem” and it would be fixed in a few hours.

I called again after noon and sat on hold for over a half-hour to find out the change was permanent and I would have to “correct” my code to work around their “security fix”. It took me about a half-hour to figure out their “security fix” was a bogus amateur stunt by some idiot and I had to make some changes on about 800 of my index files to get back into the file server directory access.

I don’t know what kind of security they think they are fixing by jiggering with default server access flags but they are fools if they think they have prevented any file access to somebody with half a brain and the determination to get in —— like me.

So things should be working properly again and if you find something that doesn’t look or work right please let me know.

MjL

#7 Click this link to see Blog page --> 12/07/2009

The web server was busted until about 15 minutes ago so I couldn’t get any work done on the #Blog this morning until now. I called tech support at 4 a.m. and got a nice sounding lady in some foreign country who had a pleasant voice speaking in a version of English I could not understand. Eventually I got the idea they knew they had a problem and were “working on it”. I don’t know what country was working on it or if they are done, but so far it seems to be back up and running.

MjL

#8 Click this link to see Blog page --> 08/06/2010

I find it hard to believe I have been banging on this keyboard to keep this #Blog running for four years now! It has mostly been good for me, something to do and a way to vent my frustrations. I’ll admit there have been times my blood pressure has probably gone up but in the long run I feel better doing the blog than other mischief I might get into.

MjL

#9 Click this link to see Blog page --> 08/16/2010

Tammy sent me a text message a moment ago that said the #Blog wouldn’t let her make a comment but it seems to be working OK for me. I suspect the spam filter keyed on a particular word and might work if rephrased but I don’t know. If anyone has a similar problem please send me an email and I will try to fix the problem if I can.

Tammy, please try a one word comment like “test” just to see if it will work?

MjL

#10 Click this link to see Blog page --> 08/16/2010

#Blog
I figured it out thanks to Tammy sending me her comment via email which I got to load as you can see above. Her original sentence had no space between the row of periods and the word run in the first paragraph, third sentence. My filter won’t allow anything with <dot>ru because there are a ton of viruses and spam from Russia. Problem solved. Just always put a space after a period or dot so the filter doesn’t confuse it with an illegal Internet address. Aren’t computer programs fun!

And I agree totalheartedly (just to mess with my spellchecker!) that kids should have more summer vacation time and not less. The idea of year-round school is terrible to my way looking at it.

MjL

#11 Click this link to see Blog page --> 09/17/2010

I have been having fits with my #Blog server again. I keep getting error messages from the server and I know I am not doing anything any differently than I was a week ago.

I suppose they hired a new batch of college interns or something or somebody had a “better idea” that has screwed things up. As usual, I can’t get anybody to actually look at the problem —— they always blame the victim don’t they!

MjL

#12 Click this link to see Blog page --> 09/18/2010

Another bunch of people I would like to spend some personal time with are the idiots at the tech support desk on my #Blog server. They keep telling me everything is fine because they don’t see a problem. Me telling them there is definitely a problem doesn’t seem to register with them.

MjL

#13 Click this link to see Blog page --> 09/21/2010

#Blog #Yahoo
I started my morning with a Satisfaction Survey in my Inbox from Yahoo Web Hosting Support. They wanted to know how satisfied I am now that they have fixed my problem. I gave them a survey alright; I told the jerks THEIR problem was not fixed at all and I was tired of them trying to convince me that it was my problem. Further I was insulted when they questioned if the problem existed at all. I just wish they would spend half as much time fixing the problem as they do begging for compliments with their stupid surveys. My final word was as follows:

FIX YOUR DAMN WEB SERVERS AND QUIT GIVING ME THE RUN-AROUND!

MjL

#14 Click this link to see Blog page --> 10/30/2010

I’ve been here at the Pekin #BobEvans since 6 a.m. Our telephone service went out yesterday at noon. No telephone, No Internets. A&B have been lost. The idiot phone system at #Frontier (used to be Verizon) took me forever to get a person to argue with about whether the problem is in my house (my problem) or outside my house. Finally I am told by this cretin that it will be fixed by 1 p.m. today AFTER they ascertain the problem is not mine.

So I am trying to put the #Blog together here at Bob’s. We shall see what I can get done before they throw me out!

MjL

#15 Click this link to see Blog page --> 10/31/2010

It is so much nicer to work on my #Blog from home. I have to admit it was different to sit in a restaurant and have coffee delivered to me while I worked on it yesterday, but I prefer my own computer and keyboard in my own chair.

We got a call from the repairman and he said some farmer near Tremont cut the lines while putting in a drain culvert. I hope they send the farmer a bill for the repairs.

MjL

#16 Click this link to see Blog page --> 11/13/2010

After all these weeks I am still getting that goofy Yahoo #999 error on the #Blog. I keep calling but I’m down to once a week. I don’t think they will ever fix it but I have to run up their phone bill a little!

MjL

#17 Click this link to see Blog page --> 11/13/2010

I called #Yahoo Web Hosting Technical Support about the #Blog and got some guy with a pleasant accent from either Bangladesh, India or some similar sounding place.

I immediately gave him my latest “Case Number”, my date of birth, my zip code, and that I played the trombone in grade school.

I have all those fun trivia answers because that is what they always ask to “verify” I am me.

I then told him I wasn’t interested in talking to him or listening to excuses for an hour, that I was simply calling for the 16th time since Sept 17th and this was my 8th “Case Number”.

He took my cell phone number and my email address, which I have given to them in the 15 previous calls, and assured me they would get back to me. I’ll call again in a week I guess.

MjL

#18 Click this link to see Blog page --> 11/19/2010

I got a phone call last evening from Nathan. He spent some time trying to convince me the Yahoo #999 Error is an “IP error”.

What I heard is that he could care less about this #Blog problem caused by Yahoo and he wasn’t going to offer any reasonable explanation or make any effort to rectify the situation.

Somebody at Yahoo designed this crap software to prevent multiple connections and so if you get the error it is because your IP made multiple connections. No further discussion.

His reasoning is you wouldn’t get the error for any other reason because it was specifically written for that reason.

The same logic would say that if you shoveled horse manure into Nathan’s car he would spend the day looking for a horse in his glove box because only a horse could have done it?

Nathan’s best advice was if you get a 999 Error —— wait an hour for it to go away. Good grief.

Anyway, when I call again later today I want to make sure Nathan is not a part of the problem and get someone who might actually know what they are doing to look into this.

MjL

#19 Click this link to see Blog page --> 11/19/2010

#Blog I just thought of another analogy to explain #999 Nathan’s faulty logic circuits.

Smoke alarms are designed to warn you in case your house catches fire. So if Nathan’s smoke alarm goes off he is calling the fire dept. even when he can see the house is not on fire.

Because the smoke alarm wouldn’t go off unless the house was on fire and he just can’t find the fire.

Because he is looking for a house fire he neither looks for or sees the burnt toast in the toaster.

MjL

#20 Click this link to see Blog page --> 11/20/2010

I called the #Yahoo Tech people again. The young lady I reached this time says the so-called “engineers” are adamant that the #Blog problem is being caused by PHP errors because there are a few in the log file.

I think they are full of beans and are grasping at straws but they insist I have to go 48 hours without a PHP programing error.

It is clear they have decided this is the issue and until the log remains empty they aren’t going to look for the real problem.

I have been checking my files for errors and have fixed a few. I suppose I could be wrong but I think they are clueless and have hit upon this as a means to put me off.

So I will play along I guess because I really don’t know what the problem is and on the off chance they might be right I will correct these files and give it some time.

MjL

#21 Click this link to see Blog page --> 03/02/2011

The Yahoo 999 errors continue on this #Blog. I got an email from their tech support telling me it would be another three to five business days for them to resolve it.

Nothing like a form letter in reply to a request to fix a problem they should already know how to fix since they found the very same problem only four months ago. Another example of how technology is going backwards.

MjL

#22 Click this link to see Blog page --> 07/27/2011

The #Blog will be a little screwed up this morning until I can figure out what the server technicians have done this time. They can’t seem to decide what time zone or format they want to operate the server on and it appears they have changed it yet again. So my calendar says it is yesterday the comment log on the left isn’t working at all. Repairs will be in order. Please bear with the technical difficulties.

MjL

#23 Click this link to see Blog page --> 07/27/2011

I think I have it all sorted out now but it took most of the day. I made two calls to tech. support but, of course, they swear it was nothing they did. I went ahead and changed my #Blog code so the dates and times show right and had to change the way I show the listing on the left side of the last 15 comments. Again, this all somehow automagically went kaput and they know nothing about it. I really hate it when they refuse to listen and try to “school” me about what I am probably doing wrong when I haven’t changed anything at my end in over two years! Dumb bunnies!

MjL

#24 Click this link to see Blog page --> 07/28/2011

Once I discovered what the problem was with the #Blog I was tempted to send an email to the tech support people to explain it, but I decided it would be a waste of time.

Even if they understood it they probably wouldn’t share it with anyone or do anything about it.

MjL

#25 Click this link to see Blog page --> 08/06/2011

Today marks the five year anniversary of this #Blog. My how time flies, etc. So I wonder if I can make it another five years? I really appreciate you guys putting up with my many changes to the format, the silly jokes and sillier pictures. I continue to have a lot of fun here.

MjL

#26 Click this link to see Blog page --> 08/09/2011

There are some serious logjams going on with my #Blog site server. I would guess they turned maintenance over to the summer interns or something. When I called about it I got something like well like you know like I dunno like what maybe it could be like is sumthin at your end like your code or like —— you know —— you could call back later —— like —— OK?

So it might be a while longer before I can get everything working again this morning —— like —— you know?

MjL

#27 Click this link to see Blog page --> 08/30/2011

Once again the wayward technicians at my web server have fiddled with the time zone settings. Evidently we are back to using Pacific time which is seven hours different from Universal time based in Greenwich, England. This really screws up my #Blog because all my entries are time stamped from our central Illinois time zone but have to be converted in order to show up at the right time. Screwed up again. I DO wish these people would make up their minds as this is the fourth time they have done this to me!

MjL

#28 Click this link to see Blog page --> 09/21/2011

The #Blog server was down yesterday morning from about 6 a.m. until late morning. I don’t really know when it started back up because I was out and about. I just know I was some ticked off it suddenly quit working —— again.

MjL

#29 Click this link to see Blog page --> 09/23/2011

Okay —— you know how I gripe, moan, groan and complain about my lousy #Frontier Internet speed or my screwed up #Blog server? Well I must say it is fantastic today! It is lightning fast and everything seems to be working. At the risk of jinxing everything I feel it is only fair to say good things about this. “GOOD THINGS!”

MjL

#30 Click this link to see Blog page --> 03/11/2012

I fell victim to the twice-a-year event of Time Change. I typed the preceding two entries and they appeared to disappear into the Internets never to be found. But then my feeble sleep deprived mind reminded (?) me that our time changed (not really) but the server time remains constant to GMT (Greenwich Mean Time) ((That’s what time it is in England?)).

So I had to once again pull up all the files on the server that refer to time when accessing #Blog entries and change them from -6 hours to -5 hours. We have miraculously grown an hour closer to England (and Arizona).

Anyway (I think) I have fixed the Blog to work properly until the next time change or the next time some technician changes the time base on the servers back and forth. (Like they did last year, and the year before)

What I think happens is that somebody calls up Tech Support and complains their web site is off by an hour and the unknowing technicians change the time base. And then some other person from England (or Arizona or parts of Indiana) calls and complains THEIR time changed on their web site and they change it back - or whatever.

Just more evidence we should pick a time and stop messing with it. Leave it to humans to think they can change time anyway.

MjL

#31 Click this link to see Blog page --> 08/21/2012

It looks like #Yahoo finally got done with their “site maintenance” so my #Blog is back up and running. I don’t know why they would have to shut everything down to do this but they did and now I hope they are completely done!

MjL

#32 Click this link to see Blog page --> 11/02/2012

There were problems with the #Blog server all day yesterday. I don’t know if they were caused by the mess on the east coast or just the usual bungling incompetence of the people at Yahoo! who are supposed to keep things running. It has gone down a couple times already this morning too.

MjL

#33 Click this link to see Blog page --> 11/20/2012

I usually use Firefox as my web browser but occasionally I use Internet Explorer just to see if my blog is working correctly.

It is especially a challenge to get videos and other multimedia to work properly on both. And generally if it works on Firefox and IE it will work on Chrome. Now that Tracey has the iPad I can also see how it works on Apple’s Safari browser.

I immediately discovered the Safari browser kept reloading the page improperly. I found that it was the “Go to Top” routine that used to be in the lower right corner.

I don’t know if anybody misses that (or even knew it was there) but as soon as I removed that the iPad worked flawlessly on everything but video. It is very fussy about what video it will run, but works fine with YouTube.

So one of the reasons why I haven’t been writing so too much on the #Blog lately is that I was getting deeper and deeper into programming modes as I sometimes do when working on compatibility issues.

I made one important discovery in the process. I suddenly noticed videos that used to work properly weren’t working. It took me a while to realize that if I had both Firefox and IE running at the same time, neither would run video properly. So I had been chasing my tail. (That seems to happen too often) I also rediscovered the odd quirk that IE has when trying to cut and paste text —— there is some routine which tries to decide how to place the cursor for you and makes it nearly impossible to exactly cut and paste web code which is filled with brackets, etc.

So I am back to Firefox again and you IE users will just have to let me know what doesn’t work because I am so tired of messing with it.

MjL

#34 Click this link to see Blog page --> 05/13/2013

Just had a rather embarrassing moment —— I kept getting a 404 error when I tried to access this #Blog. So I called tech support where the guy told me the system was working fine and it was a browser error. I was dubious at first but after shutting Firefox down and restarting —— all was well. I apologized for blaming the web provider. He said it was OK and we said goodbye, except he didn’t hang up for a while and neither did I. Since I was wearing my blue tooth earpiece I was just going to let him hang up but after about ten seconds of small noises from his end of the connection I heard him say rather sadly, “Oh Brother, what a night!”, then “Uh-Oh!” and then the line went dead. I almost felt like calling back and apologizing again. So whoever you are, wherever you are tech support guy, believe me, I have had nights at work like that too! Thanks again.

MjL

#35 Click this link to see Blog page --> 08/06/2013

It is hard to believe I have been banging on a keyboard to this #Blog for seven years! Keeps me off the streets I guess.

MjL

#36 Click this link to see Blog page --> 09/27/2013

I try to back up my #Blog database every day but recently the backup utility at #Yahoo (my web site host) stopped working. I sent an email explaining this. I got an email back from Giridhar telling me “We have repaired the database from the backend and now the database status is “Active”.” There was nothing wrong with my database, it was “Active” when I sent the request and was not in need of repair. I’m trying to get them to repair the utility on their web site —— but of course they have to believe it is my fault that their utility doesn’t work. I will try again to get this through to them.
Gotta love tech support.

MjL

#37 Click this link to see Blog page --> 02/22/2014

Well the #Blog finally returned to working order; miraculously it would seem because nobody at Yahoo takes credit for fixing it or would even acknowledge that it was broke all day. Spontaneous dysfunction and then self healing.

MjL

#38 Click this link to see Blog page --> 04/06/2014

I got a letter in the mail from some outfit called “Domain Registry of America”. The letter says my domain name for my blog site, www.mjlegel.com, will expire in August and I should send them some money to renew it.

I have never had to pay anyone this fee before so I checked with Yahoo, the company that originally registered my site, and they said to disregard the notice unless I wanted to switch my entire #Blog to this company.

I suspect there are people who dutifully mail off checks to this outfit and don’t need to do that. It ought to be illegal to run these scams but the government makes the laws and it has been a while since our government made any laws to protect us. Mostly it passes laws to protect the businesses that abuse us.

MjL

#39 Click this link to see Blog page --> 06/17/2014

I had sent an email to the #Yahoo Tech Support crew to tell them to fix the database backup utility (again). They didn’t fix the utility but did “update” my #Blog web site so now it has some problems I have to fix (again).

I sent a somewhat snotty email back again telling them they didn’t fix THEIR problem but did manage to hose up my site for me. Almost every time they screw up things on their servers it takes a week or more of them trying to blame it on my site, my code, or whatever until eventually they find the problem with their server and fix it. Of course they never admit the problem was at their end —— it just miraculously starts working again.

Anyway —— if you run across something on the site (again) that doesn’t work properly please let me know.

MjL

#40 Click this link to see Blog page --> 06/17/2014

Speak of the devil! I just got an email from Lohit —— the database tech answering my questions about the busted backup utility at #Yahoo. Lohit writes:

The database file is currently 180MB which is of huge size. So, it would take time to have the database backed up or repaired. If you want to have your database backed up, I would recommend you try a manual backup using “phpMyAdmin”.

The database is actually only about 56MB in size, the rest are index files that are not part of the database or backed up. So Lohit is once again clueless. I wrote back the following —— “I am not asking for your advice —— I am asking that you repair the MySQL backup utility. I have used it every day for several years now and it fails to function at least once a year until somebody can be convinced to fix it again.” I am not going to hold my breath. #Blog

MjL

#41 Click this link to see Blog page --> 07/16/2014

My email battle continues with the lame-brain, single-minded technicians and minions at #Yahoo.

The backup utility on their web site will not back up the database for the #Blog. I send them emails with detailed information.

They reply I must give them permission to “test and publish” my database in order for them to determine what is wrong with my site.

I reply there is nothing wrong with my site and so they refuse to fix their problem. The last two times I gave them permission they screwed my database up completely and still found no solution to the problem —— so I am not going to let them experiment that way again.

The simple fact is they have no idea what they are doing and they arbitrarily change things to see if it will work instead of fixing the backup utility.

I have decided to send a different email every day with a new “incident number” in the hope I can nag them into doing something other than blame me for their problem.

MjL

#42 Click this link to see Blog page --> 11/09/2014

The morning cartoons and news photos on the ol’ #Blog are just going to have to wait —— I can’t get connected to the file server at Yahoo.

I called tech support and spoke with a heavily accented person who informed me they have a “temporary technical issue” —— try again in a “few hours”. Well, at least I know it isn’t my fault.

Oddly enough I was directed by the droning recorded message at the beginning of the call to go to a web site to get an “Incident Number”. I have to wonder why they didn’t just put a message there explaining their “temporary technical issue” and save us all some time? Stay tuned ——

MjL

#43 Click this link to see Blog page --> 11/09/2014

The file server finally started working so now there are news photos and toons on the #Blog.

MjL

#44 Click this link to see Blog page --> 11/12/2014

I spent entirely too much time on the #Blog yesterday playing with a new image viewer. I revamped two of the entries on the page for yesterday (Tracey’s rose and the Obummer blurb) using this new code toy and the “Assorted Stuff” above has new thumbnail links to click. Something different anyway.

MjL

#45 Click this link to see Blog page --> 11/18/2014

I have stuff I would like to do with the #Blog but the FTP server is down. Again. I called #Yahoo Tech support —— wait times are over an hour according to the machine voice. I sent an email. They brag they will answer an email within 24 hours. The email will say, “Please explain YOUR problem in greater detail.”

MjL

#46 Click this link to see Blog page --> 11/18/2014

#Blog #Yahoo
The FTP site is finally back up and running. I’ll get an email tomorrow telling me everything is fine. And it will be from Bangladesh and they will have never have known there was a problem in the first place. Global technology at its best!?

MjL

#47 Click this link to see Blog page --> 08/06/2015

Today marks nine years I have been writing, complaining, etc. on this #Blog. About all I have to show for it is the ability to do some HTML code and I can type a little faster. And it helps me blow off some steam now and then. I consider it my graffiti to the world without getting paint all over myself.

MjL

#48 Click this link to see Blog page --> 11/11/2015

I started working on the 2016 #Blog calendar so it will be ready by next year. I am slow.

MjL

#49 Click this link to see Blog page --> 04/11/2016

I had noticed that lately it takes considerably longer to upload data like photos, etc. to my #Blog site. I have engaged in a series of emails with the people at the #Yahoo ftp site and the last email from them explained that the more I save on their “unlimited data plan” the slower my ftp speeds will be. So I can store as much data as I want if I can get it uploaded but they throttle upload speeds to discourage use.

This morning my upload speed was throttled so slow it took almost fifteen minutes to upload the news photos and cartoons. Yesterday morning it only took three minutes. So they will not raise the threshold and they are punishing me further for complaining by throttling it even more.

I am now actively looking at moving my entire domain to another web hosting site. It sounds like a real pain in the butt, but it is worth looking into at the least.

MjL

#50 Click this link to see Blog page --> 04/14/2016

I have been making a few calls and sending emails for the past few days trying to resolve my issue with slow FTP upload speeds to the #Blog site. I have concluded that although it wouldn’t cost much money to move to another server it would be a large hassle.

The advice I received from #Yahoo varied. I was told perhaps it was something my ISP was causing so I spent a half-hour on the phone with Frontier. They concluded it wasn’t their problem. (Of course.) One of the Yahoo techs suggested I delete some of the “unnecessary files” on my site. Both Frontier and Yahoo declared they would escalate “my” problem.

This morning my upload speeds are miraculously wonderful. I have no idea who fixed what or if it fixed itself. It is always something.

MjL

#51 Click this link to see Blog page --> 04/14/2016

I just received a call from Taylor at #Yahoo Customer Service. I had talked to her two days ago and she said she would contact a specialist and get back to me. So I now know it was due to her efforts that my #Blog FTP uploads are working so good again. It shows that getting things done sometimes just amounts to getting the luck of the draw. Taylor is evidently a conscientious worker who spent the time to get this fixed and I would happily reward her if I just knew how to do that!

MjL

#52 Click this link to see Blog page --> 08/06/2016

How about this —— Ten years ago today I started this #Blog! Seems amazing even to me that I am still doing it. Oddly enough I still enjoy it and especially looking back over the years to see what was going on.

MjL

#53 Click this link to see Blog page --> 02/04/2017

I tried to update the #Blog database and received a “connection refused” error message. It is always something.

MjL

#54 Click this link to see Blog page --> 02/04/2017

#Blog
Well I managed to get the “This Day in History” post to upload but it took a couple tries and the web server seems sporadic at best. I think my server must have been sold again? Ever since YaHoo went belly up the web services have been sold around several times and each time the new owners manage to screw things up.

MjL

#55 Click this link to see Blog page --> 03/29/2017

It appears the drunken fourth graders who maintain my #Blog server have been hard at work again. Over the past few days I have encountered numerous “Connection Refused” messages. I would call and complain but I’m afraid they would try to fix it and then it would be permanently broken rather than just occasionally.

MjL

#56 Click this link to see Blog page --> 03/29/2017

Another glitch I have discovered on the #Blog is that NONE of my *flv* or *swf* files seem to be working. I don’t know if that is due to some upgrade of policy, update of flash player plugin or — what?

MjL

#57 Click this link to see Blog page --> 04/15/2017

I found an email from #Yahoo in my inbox this morning. It says my #Blog domain name will be suspended in four days if I don’t update my contact information. It took a while to finally track down which page that information is on.

I have updated that page several times over the past years and they still can’t seem to get it right. They still have my email address at verizon.com which got bought out by Frontier many years ago. The really odd thing is they sent the suspend notice to the right email address?

Once again I verified the proper information and now we wait to see what happens. If the Blog disappears in four days we will know they have failed. Again.

MjL

#58 Click this link to see Blog page --> 04/21/2017

This could turn into a lengthy message concerning the abject example of worthless customer service by the parent company of my #Blog server.

The vast majority of my Blog content is in a database of daily entrees. In case anything should happen at the site or on my computer I backup the database regularly. This is done on a “utility” provided by the server and it is horribly out of date. I have complained about it regularly for almost a decade. To no avail.

One of questions asked by the customer service people is will I agree to allow them to “test my account” or “make changes to my site if needed”. I always answer this in a loud NO. NEVER!

I do this because whenever I have allowed them to tamper with my account they have screwed it up. And because the problem has absolutely nothing to do with my account but with the bad programming of the backup utility.

This utility searches through all the content on the web directory and lists all the directories and sub-directories. These are listed in a form page allowing a choice to determine where to save the backup. My site has many, many such choices and the listing takes almost 5 minutes for the utility to compile and often results in the web page timing out. And I have to start it all over again.

I have asked numerous times to have this page code rewritten to simply save the backup in either the root directory or a named directory such as “Backup”. Anything other than going through this antiquated and time consuming listing of hundreds of directories.

This latest attempt has continued over the past week with replies from several “representatives” all insisting I MUST give them permission to test and alter my account appropriately to fix MY problem.

Rather than give up on this stupid process, which I suspect is the reason they persist in the nonsense, I will continue to reply with the same request. After all these years maybe I will eventually succeed?

MjL

#59 Click this link to see Blog page --> 08/06/2017

Today is the eleven year anniversary of the start date for this #Blog. Once in a while I think about not doing this anymore but it has become such a habit now I don’t think I can. Besides, it is a good way for me to vent now and then. And it does occasionally provide a reminder of things that I would otherwise forget. Also things I wish I had forgotten, but sometimes that is a good reminder just the same.

MjL

#60 Click this link to see Blog page --> 02/01/2018

Every morning, for this #Blog, I spend a few minutes looking through various sites of news photos. More and more I find myself refusing to post pictures of the leering Twitler applauding himself. I want my Blog to represent a fair sample of reality. Yet I can’t bear to look at this clown on my own web pages.

I used to feel exactly this same way about Duh-bya and now he has been normalized by many in much the same way as Raygun was; which makes me think Twitler will one day seem normal too. Shudder.

MjL

#61 Click this link to see Blog page --> 03/02/2018

I’m engaged in another email spat with my web provider. I’ve had this problem before. The web server intermittently doesn’t allow a logon when I try to edit my php database and at other times the #Blog doesn’t load beyond the calendar.

That’s how I know it is the php database that is having trouble because it is different than the web page that loads the calendar.

This has happened before and a couple times I was informed it was due to a damaged server hard drive or co-ordinated links to server files on the server network. All completely separate from my web site and completely out of my control.

All I can do is inform them of the problem. And since it happens about once or twice a year I have become pretty good at diagnosing the problem. (The real problem is their lack of maintenance. They don’t replace equipment until it actually fails.)

I can’t talk to them on the phone because I always lose my temper with the people who refuse to listen. So I send an email. They always reply that I have to allow them to diagnose MY files and make changes to MY database. I always refuse and try to explain that the problem is technical on their end.

This time I also lost my cool via email and was a bit nasty. I get so tired of obviously ignorant people lecturing me about something I’ve been doing for longer than they have been out of grade school.

MjL

#62 Click this link to see Blog page --> 03/07/2018

The problems with the #Blog site still haven’t been completely resolved although they have become less persistent. After a couple emails back and forth I finally just gave up trying to educate the first line tech support. They are trained to assume any problems are caused by the customer and won’t escalate anything until they have royally screwed up all the customer’s data and web pages. Once they have then determined the problem is indeed with their equipment they MIGHT see if they can get it fixed.

Since I know there is nothing wrong with my data I refuse to give them permission to “upgrade”, “repair”, etc. because they are clueless. They won’t tell anyone else about their problem because I won’t “cooperate” and let them fool with my data. Stalemate.

I let them do their thing once a long time ago and it took me almost a week to get it all back where I wanted it again. They decided a web page must look like the web pages their computer cookie cutter spits out and mine is therefore not “within parameters”.

Shortly after they screwed everything up I got an email from the equipment engineer explaining I had been right, they had a server hard drive problem.

MjL

#63 Click this link to see Blog page --> 04/04/2018

Well it looks like the #Blog is finally back again. I have been calling since 8 a.m. yesterday when the site lost access. It would seem in fixing the one problem another was created.

Over the course of the past twenty hours I have made at least eight calls trying to get this fixed. It was clearly an access problem because the response was about not having “permission” to access.

The problem was greatly exacerbated by several factors. The technicians are in a foreign country and we had trouble communicating because of language, culture, time zones, etc. Every time I realized they had no idea what the problem was I asked to speak to a supervisor or to have it escalated to another level. This was immediately met with great resistance by the technician so I can only assume that it is a bad thing personally for them not to be able to fix the problem.

I was told I had “too many extra files and had to delete them”. Another call I was told I had to upgrade my php software. Etc. Etc.

They clearly had no understanding the problem was not with content but with access to that content and I couldn’t get that through to them. Eventually I explained I couldn’t delete files or upgrade software without access and FINALLY at 3 a.m. this morning I got a technician who actually listened and followed through. The problem was resolved in about 10 minutes after that.

Outsourced customer support really sucks when the people aren’t properly trained or given access to the right information. It is really magnified when we can’t understand each other.

MjL

#64 Click this link to see Blog page --> 04/08/2018

Somebody at #Yahoo is still messing with my #Blog web files. I built a log directory with three different collection routines. Each day they log script errors, who accesses the Blog and when, etc. I check them every morning and keep seven days worth of data. The only way to get rid of them is to manually delete them so I know somebody else has been accessing and deleting them besides me. They probably don’t realize the batch files are written to update each day. They are probably still trying to figure out what they are.

MjL

#65 Click this link to see Blog page --> 04/08/2018

#Yahoo #Blog
One of the stumbling blocks whenever they screw up their system is the list of questions they ask to see what I am doing wrong. (Because they have to prove it IS my fault so they don’t have to do anything)

The first one is always about my ISP being too slow, etc. I patiently explain that is NOT the problem because I have three (Frontier, US Cellular, Verizon) and if the problem persists with all three connections that should eliminate the problem being the ISP.

The next one is the question, “What software do you use to publish your site.” And I answer, “Notepad”. They refuse to believe I write all my code from scratch (with a lot of cutting and pasting) and don’t use any cookie cutter programs like WordPress, etc. We usually spend a lot of time on this one. Especially if they look at my files and don’t see any of the standard templates and typical program bloat from third party compilers.

And then we get to the FTP program I use. Again, I have three. And if all three won’t work then I can safely presume the problem is theirs.

Eventually I wear them down and make a nuisance of myself long enough to get them to look at the problem instead of at me. But it isn’t easy because they think I’m some kind of lunatic at first.

MjL

#66 Click this link to see Blog page --> 06/01/2018

There will be no Twitter Roundup today because I have been shut off by #Frontier DSL. Service was supposed to be switched over to the trailer later today but they must have disconnected service here already. I am using my phone for an Internet connection and have limited bandwidth.


Things went from bad to worse. Shortly after activating the hot spot on my phone it locked up and the Internet connection died. So no Internet and no phone.

The #Blog will be greatly delayed in updates until I get this sorted out. I am using Tracey’s #iPad to connect for now.

It is always something.

MjL

#67 Click this link to see Blog page --> 06/23/2018

It appears the PHP server is down on the #Blog site. I’m actually curious to see if this comment even makes it through. I have no idea when they might actually fix this.

MjL

#68 Click this link to see Blog page --> 06/23/2018

The #Blog server is still erratic. I haven’t tried to contact tech support because I honestly don’t know if it would make a difference.

MjL

#69 Click this link to see Blog page --> 06/23/2018

Big mistake. I contacted Tech Support and the fool upgraded my #Blog PHP software. It is not backwards compatible. Twelve years of code that won’t work now. This may take a while to fix. On top of that, the server is still broke. He fixed a problem I didn’t have.

MjL

#70 Click this link to see Blog page --> 06/23/2018

I just got off another half-hour “chat” and this guy is clueless too. I should hear something back in 24 to 48 hours. #Blog

MjL

#71 Click this link to see Blog page --> 06/25/2018

The #Blog seems to be working again this morning. That’s a start. I expect there will be some glitches along the way because of the unwanted php software upgrade. So if you see something that doesn’t work correctly please let me know.

MjL

#72 Click this link to see Blog page --> 06/25/2018

#Blog
As you may imagine I was quite irritated with my interaction with the technician Siddharth on Saturday. It was so frustrating and infuriating to have this guy continue to change my settings on the server side while he bumbled his attempts to fix what wasn’t wrong.

At every step of the way I would tell him not to do that and he did it anyway. It was like my own personal train wreck. I could see it coming and had absolutely no control of the process. This is why I hate to call tech support. They never seem to know what they are doing.

Things seem to be back in working order but I am still wary of what else may turn up along the way.

MjL

#73 Click this link to see Blog page --> 06/25/2018

#Blog
That didn’t take long. It just quit working briefly again. So I’m right back to the intermittent problem I called about Saturday. Two days just to get back where I started? I’m afraid to call them back again. Maybe I should wait to see if it fixes itself?

It keeps bombing back to this comment submission so I don’t know if it is logging the comment or not. I did call tech support again and again I was connected with somebody whose first language is not English. Rinse. Repeat. I was told I had to respond to the email I received that said it was fixed. Run Around.

MjL

#74 Click this link to see Blog page --> 06/25/2018

#Blog
Annndd —— we are back again. No reply from the “expedited engineering team” so who knows if they fixed it or —— it fixed itself. I can completely understand why Yahoo is going out of business.

MjL

#75 Click this link to see Blog page --> 06/26/2018

It appears the #Blog is back up and running again. I didn’t have any problems after they fixed it, again, yesterday morning.

I have had a number of programming errors reported due to the unwanted php upgrade so I will have to go back through my program code and alter or remove those routines that are no longer valid. The latest php software is not backward compatible. Another of those monopoly moves in software where they make “upgrades” that require you to deal with their laziness and make changes to suit their whim.

MjL

#76 Click this link to see Blog page --> 08/06/2018

Twelve years ago today I started this #Blog. Time flies.

MjL

#77 Click this link to see Blog page --> 10/04/2018

I started working on building my files for the #Blog next year. Not particularly difficult but time consuming. Once I have it all put together and ready to upload for the year it makes daily maintenance so much easier than doing it day by day. Hopefully I won’t hose anything else up in the process. It happens. I try to back everything up before making changes, but Murphy’s Law always applies.

MjL

#78 Click this link to see Blog page --> 11/04/2018

Completed my twice yearly time change on the #Blog. I finally wised up and left myself a READ_ME.TXT file to explain the procedure for the next time. I always seem to bumble about a little bit before I figure out which configuration files need to be changed.

MjL

#79 Click this link to see Blog page --> 04/06/2019

I got a notification from my #Blog server that I had to “upgrade” my email server there. Typical of Yahoo, I’ve had to do this at least three times in the past year. I don’t know what the drunken technicians are doing there but I am getting damn tired of doing their job for them. Instead of migrating everything whenever they do another #ArtsyFartsy upgrade, they just give you a deadline to do their work for them or they lock access to your email. It is getting old.

I wasted another half-hour of trying to decipher their redundant menus and bullsnit to get my account working again. Damnit!

MjL

#80 Click this link to see Blog page --> 04/24/2019

Experiencing significant delays on the #Blog server. The drunken fourth graders at Yahoo must be fixing things again.

MjL

#81 Click this link to see Blog page --> 08/06/2019

Anniversary of the #Blog.
Thirteen years and counting.
What a long, strange trip it has been?

Post-dated MjL

#82 Click this link to see Blog page --> 02/10/2020

The #Blog database seems to be screwing up this morning so if you make a comment and don’t see it —— please let me know.

MjL

#83 Click this link to see Blog page --> 02/10/2020

The #Blog seems to be working for the past hour or so —— fingers crossed.

MjL

#84 Click this link to see Blog page --> 04/14/2020

It looks like the #Blog server is screwing up again. I have had several comments disappear this morning. Aggravation!!

MjL

#85 Click this link to see Blog page --> 04/15/2020

I spent almost an hour on a “chat” with a technician from the #Blog site yesterday. I don’t think he had one clue about their server problem. I explained I thought it was likely a bad hard drive on one of the parallel servers but it was completely over his head.

Late in the afternoon the errors became less frequent and I can only hope they had more complaints or a complaint from a more important client so they spent some time looking into it.

Or maybe the glitch is still there and I haven’t seen it yet this morning.

MjL

#86 Click this link to see Blog page --> 05/27/2020



#TechSupport #Yahoo #Blog
I can’t tell you how much dread I feel at this announcement. EVERY time these idiots improve, upgrade, etc. it turns into a major pain in the ass for me. I have never dealt with a more inept bunch of people and each time I wonder why I don’t move the Blog to a different web host. The last time they did this they turned off the backward-compatibility and I had to rewrite a lot of code. Hard telling what they will screw up this time.

This might also explain the sluggishness and down time of late.

I suspect they have a bunch of teenagers in India doing the transfer of data to this new system.

So if the Blog disappears (again) on or after June 9 you will know why.

Update: 05/27/23
Almost three years later and another selloff to a new outfit (#Turbify). This time they really hosed everything up and my site was FUBAR for weeks. Still not completely repaired.

MjL

#87 Click this link to see Blog page --> 06/18/2020

I just wasted a half-hour on a tech support chat with #Yahoo trying to get them to fix the #Blog MYSQL backup page. I don’t know why I bother, the people that answer the chat are so clueless they don’t know the difference between html, php or how the database works.

It has been locked up for over a week and I doubt it will work again properly for another month. Very aggravating.

MjL

#88 Click this link to see Blog page --> 07/09/2020

I lost all access to my #Blog yesterday afternoon.
I got the error message:

“Sorry! You don’t have permission to view this page.”

I couldn’t see the Blog, log on to edit the database or to the FTP site. I couldn’t even log on to the help pages on the server.

So I initiated a “chat” with a technician. Deepak by name.

Here are just few questions on the chat log as Deepak frantically tried to find out what I did to cause this problem.
(It is always assumed first that the customer is the problem.)

Could you please tell me which tool you have used to build your website?

Could you please tell what changes you made recently?

Have you updated any special file or any update?

After 45 minutes of me explaining it was an access issue and not a program error on my part I finally gave up and asked that he send me an email if the problem was fixed. About a half-hour later it all started working again. No explanation. Par for the course.

MjL

#89 Click this link to see Assorted Stuff page --> 09/12/2019 #1

I just posted this on #Facebook and received a 24 hour ban. I
can’t post anything until tomorrow. The crazy thing is I got
the photo FROM Facebook last year to put here on the #Blog.

MjL

#90 Click this link to see Blog page --> 10/23/2020

The #Blog server was up and down most of yesterday afternoon and evening.

So I am just a bit slow in getting things up and running today.

MjL

#91 Click this link to see Blog page --> 02/22/2021

Finally got the #Blog back up and running. I had permission errors all day since about 9 a.m. I called several times but couldn’t understand the Indian, Bangladesh or whatever accent or the connections were so bad one or the other of us couldn’t hear.

I just now finished a chat session and it was fixed in 5 minutes.

I will never know what happened.

MjL

#92 Click this link to see Assorted Stuff page --> 03/13/2021 #1

#Blog

MjL

#93 Click this link to see Blog page --> 08/06/2021

Fifteen (15) years ago today I started this silly #Blog!
It has been fun looking back over the years.

MjL

#94 Click this link to see Blog page --> 08/14/2021

The #Blog database is acting very erratic this morning.
Some entries have taken more than one try and sometimes they blank out for a while before returning. Hopefully the drunken fourth graders who run this system will get it figured out without killing my Blog.

MjL

#95 Click this link to see Blog page --> 08/29/2021

#PowerOutage
The power just went out so I am sure the #Blog will be late.
Posted from my phone.

MjL

#96 Click this link to see Blog page --> 09/13/2021

#Blog site seems a bit clogged up again this morning. Long delays and sometimes doesn’t work at all. Must be #Monday.

MjL

#97 Click this link to see Blog page --> 09/26/2021

I’m having a hard time choosing information to #Blog that isn’t so rehashed and twisted by the media. I get so tired of the single issue 24/7 treatment while so many other things are ignored. I find myself hovering over news links, photos and social media posts and deciding to just move on rather than spend the energy to clip and share them.

MjL

#98 Click this link to see Blog page --> 01/07/2022

My FTP and the access to the #Blog server has stopped working. I was on the phone with two different “technicians”, neither of which spoke English very well, and they were helpless to understand the problem much less fix it.

If I can’t this resolved I can’t upload content to the site.

Hope I can get it working without too many calls and hours on the phone to foreign countries.

MjL

#99 Click this link to see Blog page --> 01/20/2022

The #Blog server FTP has been working properly for 24 hours so I feel less likely to jinx myself by mentioning it. It only took 12 days of constant phone calls and emails. I suspect I was not the only person having this problem so I probably shouldn’t take all the credit.

I’m just glad they finally got around to fixing it.

MjL

#100 Click this link to see Blog page --> 08/23/2022

Problems with the #Blog server this morning. Comments are disappearing and then reappearing. If you don’t see something you posted it may show up later?
Or not?

MjL

#101 Click this link to see Blog page --> 08/23/2022

I usually get an email when a comment is logged on the #Blog server. My first indication something was wrong was in not receiving those emails. Then I noticed a couple comments I had made had disappeared and then reappeared. Then I started getting dire CRASH and REPAIR messages.

I just got a ton of emails with my (and Michael T.) attempts to comment. Some made it, some didn’t. Hopefully it is back up and working but I wouldn’t bet money on it.

I don’t contact customer support because they will deny THEY have a problem and will create an even worse cluster flop trying to “repair” my data. Eventually some other user will fall on their sword and sacrifice their data to make it better for the rest of us.

MjL

#102 Click this link to see Blog page --> 08/24/2022

It appears the only casualty of yesterday’s #Blog database crash was my Wordle entry and I put that back in again.

It also looks like they got the database fixed (knock on wood).
I am so glad I didn’t call #TechSupport and I’m hoping whomever did call didn’t get their database destroyed.

I say that because the poorly trained non-English speaking techs ALWAYS presume the problem is caused by the customer. They then try to repair the customers (unbroken) data with a broken system and will only realize the problem is not the customer’s AFTER they have really messed up his data. Been there, been trashed. Fortunately I have learned to back up my data regularly and not rely on them.

MjL

#103 Click this link to see Blog page --> 09/29/2022

On top of everything else, my #Blog server isn’t accepting files again. So, even when I get stuff done I can’t upload it. When it rains it pours.

MjL

#104 Click this link to see Blog page --> 11/06/2022

I’m still waiting to see if the #Blog server changes the time code so the timestamps might suddenly be off by an hour if or when they do. #DST

MjL

#105 Click this link to see Blog page --> 04/09/2023

Part of my motivation for the #Hashtags I have been trying is my daily journey back through the #Blog each day. I originally started doing this years ago to check for and correct link rot.

Over the years I’ve noticed a lot of memes and themes. The most glaring —— semantics and word choices used in news photo captions.

I toyed with the idea of having a category regarding this and soon realized it was so pervasive as to become a full-time job and I already edit those on a regular basis anyway.

People become protestors, demonstrators, rioters, activists, victims, perpetrators, defendants and so on. Usually according to the editorial slant of the caption writer which is almost always in favor of the authorities.

Police are almost always rioting but are portrayed as riot police. They cause the situation they are supposed to be controlling. The people they assault are never victims of police violence but are called suspects, squatters, defendants, perpetrators, rioters, etc.

Internationally banned chemical weapons become tear gas or pepper spray. Lethal high pressure water cannon become water sprays. Lethal projectiles become rubber bullets, flash bangs and so on. Everything a cop uses is potentially lethal. They are all weapons. Guns, clubs, mace, pepper spray, tasers, handcuffs are all weapons and are used routinely to harm and assault people with impunity.

American media are consistently the worst but other countries are recently taking up the mantle of authority and austerity. Phrasing situations to insinuate something the facts don’t warrant.

MjL

#106 Click this link to see Blog page --> 07/05/2023

#Turbify I received an ominous email from the blog server tech support and immediately started a chat discussion with them very early this morning. Looks like the #Blog is in danger of disappearing again.

Chat Transcript

MjL

#107 Click this link to see Blog page --> 08/06/2023

It is hard to believe I have been messing with
this #Blog (almost) every day for SEVENTEEN years!

MjL

#108 Click this link to see Blog page --> 08/17/2023

#Fresenius #Excel #Blog
Tracey’s employers have rearranged her region (again) and she needs some help rebuilding spreadsheets for the students, clinics, educators, learning centers, etc. I will be spending some time building and populating some data for her. The Blog may suffer.

MjL

#109 Click this link to see Blog page --> 09/09/2023

I’m getting emails from #Turbify threatening to suspend my account again for PHP script errors. Most of the errors have been caused by the last fiasco where they “upgraded” my account to the latest versions of software and they are not backward compatible. The Blog is older than some of these technicians.

I will be trying to resolve these issues but if the the #Blog disappears (again) at least you will know why.

MjL

#110 Click this link to see Blog page --> 09/10/2023

#Blog #Turbify
I will be spending a lot of time trying to tie up all these logged “errors” and the vast majority aren’t really errors. The code works, just not in the way it is expected to by the filter. They are wasting more energy looking for problems than the problems they think they are finding. An unreferenced index or empty variable causes no problem if never addressed by any other part of the code. Hopefully I can convince them to focus on more pressing issues if they exist. What bothers me the most is that most of these problems were caused weeks ago when THEY changed the system architecture and code versions.

MjL

#111 Click this link to see Blog page --> 09/14/2023

Well that attempt to sleep didn’t work either. I am so immersed in all this #Blog coding I can’t turn my brain off.

MjL

#112 Click this link to see Blog page --> 11/05/2023

I nearly reprogrammed The #Blog because the time stamp was wrong, but after some thought figured out the flaw in the #DST local time vs GMT fiasco the so-called “experts” have fostered.

Our local clocks dropped back an hour at 2 a.m. our local time but the Blog servers are in California. So at (the new) 3 a.m. local time HERE it was still only 1 a.m. DST in California until it changed there an hour later. For an hour the time stamps were still off by an hour. I’m glad I waited or I would have been chasing time changes again an hour later.

The reason this disturbs me is that not long ago this was all up to me to program for local time but the geniuses who write server code decided normal humans were too stupid to figure these things out for themselves and locked that ability out for local programming. Clearly not taking into account the time difference between servers and local users in different time zones. We are going back to everyone thinking the world revolves around their local time. For them the sun circles the Earth I guess.

THIS is why the concept of #ArtificialIntelligence terrifies me. It will be programmed by “experts” who don’t even understand how time zones work.

I’m just glad the servers are not in Hong Kong.

MjL

#113 Click this link to see Blog page --> 11/13/2023

Tracey returned home yesterday from a visit with family at the farm in #Watson. I was unsupervised from Friday until yesterday. All I did was doodle with the #Blog and Internet with some TV watching of old reruns.

MjL

#114 Click this link to see Blog page --> 11/13/2023

This hashtag adventure is turning into a bit of a mess, but it is my #Blog and I am enjoying doing it. It is surprising how different stories begin to link together in odd ways. I’m still fumbling to find a way to standardize the hashtags but I doubt I will find it.

MjL

#115 Click this link to see Blog page --> 12/09/2023

I’ve had some problems lately with the Submit button on the #Blog. Sometimes the page doesn’t refresh and I end up making multiple submissions. It happened in the past with Chrome and it started with Edge this morning. It doesn’t repeat though and I can’t seem to find the combination of events that make it happen.

MjL

#116 Click this link to see Blog page --> 02/28/2024

Glad to see the #Blog is back! It was down yesterday afternoon until just a few minutes ago. It will take me a bit to get things back up and updated. I will never know what caused the outage.

MjL

#117 Click this link to see Blog page --> 04/19/2024

I occasionally get emails regarding the #Blog and I would like to reiterate that comments are always welcome and encouraged. I respect not everyone wants to publicly share their thoughts so I don’t copy and paste the emails, but I would like to have discussion too.

MjL

#118 Click this link to see Blog page --> 04/20/2024

It was a year ago today for the Great #Blog Disaster when #Turbify updated / upgraded a complete FUBAR of the site. I am still tripping over portions of the Blog that don’t work right.

MjL

#119 Click this link to see Blog page --> 08/06/2024

I’ve been fooling around with this #Blog for eighteen years!
Doesn’t seem so long if you say it fast.

On this anniversary the bill from #Turbify almost doubled. I called up the billing dept. yesterday and was told it was because of all the “improvements” that were made. That would be when they destroyed the Blog for almost a month and I’m still finding things to fix because of it.

Talk about adding insult to injury. I managed to change plans to something less expensive but still too costly. The price of my online addiction.

MjL

#120 Click this link to see Blog page --> 08/13/2024

I’m doing some reconstruction on the #Blog ——
so if you see something not working properly —— Please let me know!

MjL

#121 Click this link to see Blog page --> 08/27/2024

Our #TelStarCable Internet is down again this morning. Fortunately I had most of the #Blog uploaded already for today. I’m using the cell phone hotspot now.

MjL

#122 Click this link to see Twitter Roundup page --> 10/06/2024 #7

The reason I never use “cookie-cutter” software to code my #Blog.
Too many glitchy routines that waste resources.

MjL

#123 Click this link to see Blog page --> 10/30/2024

I have finished editing and uploading the #Blog calendars for next year!

MjL