Archive for In the Cyber World

It’s been a few long months owing to me having to take care of emergency familial issues, but remember that post I made back in March about Web Hosting Gone Wrong?

Shortly after I wrote that post, I spoke with Andrew from Media Temple about this matter and where he obviously was not allowed to go into situation specifics aside from what was publicly posted by Kyle, we were able to talk more in-depth about Media Temple’s policies and about specifics regarding theoretical situations which could result in the scenario that Kyle experienced. I aired my concerns – elaborated where necessary – and Andrew addressed them all quite thoroughly and we spoke at length about the various topics I had addressed in my previous blog posts.

At this point (actually, much earlier, but I have been unable to really sit down to write until now – sorry, Andrew!), I have to say that where I still have mild concerns about the potential ‘ease’ of going over resource allotment, I am satisfied with the results of the conversation and no longer have that sour taste in my mouth or the same misgivings I once had.

In case it wasn’t evident in previous posts or in case anyone needs a reminder, I will reiterate that my concerns were NOT regarding MT charging for overages (in other words, I wasn’t saying that MT shouldn’t charge for overages, period).

My greatest concern was how unexpectedly the overage-causing situation had happened (it was a total and complete accident and there was no prior indication that such a problem would happen), what the ramifications were (triggering the overage as the situation caused resource over-usage), what the implications might be (how easy would it be to go over resource allotment?), and then how MT INITIALLY handled the situation.

As a courtesy to Andrew and Media Temple, I will address the issues one more time and then close this particular ‘chapter’ of blog posts regarding Web Hosting Gone Wrong.

Read the rest of this page »

Cheap(er) domain registration prices and cheap(er) basic web hosting packages have never and will never motivate me to choose GoDaddy for any of my domain registration or web hosting needs.

NEVER.

However.

Due to the old RegisterFly fiasco (not my fault!) that happened back in the timespan of 2005-2007, I had a handful of domains that I had been maintaining at RegisterFly get pushed on to GoDaddy while one domain ended up with eNom. Several got moved elsewhere (DreamHost, here I come!) while I let others whose purposes had expired… expire.

Also.

Due to working with various people over the years – paid, voluntary, because we’re friends, and otherwise – I have been forced to interact with GoDaddy as the go-between fix-it and fix-up person.

But those incidents and instances aside, I myself would never – if possible – choose GoDaddy.

Why?

Good grief, but where do I start?

I know! How about in alphabetical order?

Read the rest of this page »

So that post I made a while ago about the $1000 a month shared webhosting?

EDIT: A follow-up post has been made to this. Please READ THIS for the final update and the resolution.

To refresh your memory (or simply read if you never caught it in the first place), click HERE.

Apparently, according to Kyle Matthews whom this incident happened to, there has been a resolution offered by Media Temple – namely, $6XX amount of overage fees are being/will be/were waived.

Click HERE to read his update!

According to Kyle’s post, Media Temple sent him an email shortly after his blog post appeared asking him to call them back in regards to the “unfortunate circumstance of the issue”.

Funny, that (in my opinion anyways), when the original customer support emails had stated that nothing could be done when Kyle had first asked.

But.

Media Temple DID get back in touch and did acknowledge at least part of the gaffe on their part – good for them! That’s called customer service gone right. At least… part way.

But.

Like Kyle’s blog post states, it still leaves a sour taste in my mouth, too, and mostly because of what I had explained in my earlier post.

A company trumpeting the robustness of their service and backing it up with percentages and statistics and saying that only 0.3% and 0.03% of users (basically, VERY VERY FEW for the first and out of a random 10,000 for the second!) ever experience overage problems ONLY to be keeled over by the 2 million 404 Apache errors from one website which generated a crapload of overage charges just…

It just doesn’t sit well with me at all in any way, shape, or form ESPECIALLY knowing that once upon a not very long time ago at all, the same site had done just fine on DreamHost’s shared web hosting service.

DreamHost talks about what they offer in their services, sure, and you can go poke at their fine print if you want to, and you can read up on their thoughts regarding ‘unlimited’ this, that, and the other, and they even regularly post status updates on their servers and all but nowhere have I seen the sort of reputation/credibility-building (more like hyping, really!) that Media Temple posted on their FAQs page.

And DH managed to host the site just fine.

Blegh.

So yeah.

Resolution posted!

… But the sour aftertaste is still there and I still can’t help but wonder just what kinds of sites those 10,000 were that MT randomly picked out which generated a grand total of 0.03% of sites going over their resources.

I guess trust (or something like it) once broken is hard to fix and I guess after all the hype, I’m not sure what’s ‘realistic’ to expect from MT or not after seeing something like this happen.

… We’ll see.

~ EMG

So I’ve been getting a crapton of completely illegitimate ‘PORNO!’ and ‘VIAGRA!’ type of comments which get stuck in Akismet’s spam queue.

Because each of these comments is literally a full screen’s height long and mostly contains text which I cannot read (language, huge blocks of text and links, AND tiny font sizes), shuffling through more than a pageful to make sure legit comments make it through to me is honestly a serious pain on my EYES and can trigger migraines on a bad day.

In an effort to cut back on this sort of spam in my spam queue and in an attempt to not alienate any of my potential commentors, I have installed a plugin called Conditional CAPTCHA.

What this plugin does is this: If the Akismet spam identifier identifies a comment as a potential spam (yes, the plugin works alongside Akismet!), it will present to the person who is submitting the comment a fill-in-the-blank/text-based CAPTCHA.

The commentor will be asked to identify and type in two digits (eg: first digit and third digit) from a string of text-based digits and if they type in the right ones, the comment will pass and if they type in the wrong ones or don’t type at all, the comment gets auto-deleted.

It is not an ideal solution, but as I struggle with a status migraine, it is something I am going to implement until I can find a better alternative.

If anyone has any ideas or comments, please share them!

And to reiterate: The CAPTCHA ONLY shows up when Akismet has already identified the comment as potentially spammy.

~ EMG

… is it…?

Over here it sure isn’t!

So after a few long months of having very empty Rabbit Hole and Giving Props widgets staring at me in the face asking me, “Why haven’t you worked on your links yet?”, I finally sat myself down to wrangle around with them and only them.

Three hours later (actually five, but the first two hours were kinda scattered around)…

Behold – my Giving Props list! *points to the sidebar Giving Props widget block*

What do you think?

The list isn’t fully finished yet as there are a few people and things that I need to add on, but you get the general idea, right?

Maaan, but the list ended up being a lot longer than I thought it would be and it also ended up taking up more of my time and concentration than I thought it might!

Initially, the list was going to be a simple list of text-only links like the list of links in a typical Blogroll widget block (to maintain cohesion with the rest of my site which is very minimalistic in terms of graphics), but after thinking about ‘giving back to the community’…

I decided that maybe I could turn my simple Giving Props link block into a personal project to ‘give back’ to the people, services, and places who/that have helped me along my journey as a WordPress junkie, front-end web developer and designer, and blogger.

And that’s where all those icons/buttons come in.

To show my appreciation for these people, services, and places, I ended up creating sixteen – 16 so far! – unique slimline buttons for each and every one of these people, services, and places and boy oh boy, but did I have one heck of a blast doing so or what!

There are still more to come – there are still a few people yet whom I want to put in the list, but haven’t decided on the graphic for – but I think I’m doing good so far.

After I get the others done, I will officially send them off to their ‘owners’ and hopefully, I will hear back from some of the people and get some feedback on what they like or what they don’t like.

*crosses fingers*

… I hope nobody takes offense to what I’ve done.

~ EMG

So I’m using AddThis to Print that one blog post right there between that one post and that other post and… WHOOPS!

You know what happened?

I ended up Printing the entire blog – ACK!

Thankfully, I was only printing to PDF and the blog in question was my own and I have my blog settings set so that one page can only display a certain number of posts at any given time.

But… still.

The whole blog!

Man oh man.

I sent a support ticket to the AddThis team; hopefully I’ll get some sort of answer or workaround for this issue.

I can’t imagine that I might be the only person to have this issue unless… I’m the only person who tacks on the AddThis feature to every blog post on a page of posts?

We’ll see.

I’ll post again with more news when I find out what’s going on, but I figured I should let everyone know what’s going on in case someone else wants to try and Print a single post.

~ EMG