Clan x86

General Forums => General Discussion => Topic started by: rabbit on July 15, 2009, 10:01:41 pm

Title: Horribly Slow?
Post by: rabbit on July 15, 2009, 10:01:41 pm

Is it just me, or is the site horribly slow right now?

Title: Re: Horribly Slow?
Post by: Blaze on July 15, 2009, 10:12:51 pm

It's not running incredibly fast, but it isn't slow for me.

Title: Re: Horribly Slow?
Post by: iago on July 15, 2009, 10:44:12 pm

It seems to go back and forth. I need to get in touch with my ISP and see if they can figure out what's causing the noise. I'm getting ready for a trip in a couple weeks, and dealing with an ISP is a bit of a time commitment, so I don't really want to dive into it right now.

<edit> screw it, I just put in a support ticket with my ISP. If they don't get back to me within a week or two, or fix this by the time I get back from my vacation (exactly 1 month from today), I'm going to look into changing providers. Their service this far has been absolutely unacceptable.

Title: Re: Horribly Slow?
Post by: warz on July 16, 2009, 01:51:39 am

Yea. I've actually had a few days where the site wouldn't load for me.

Title: Re: Horribly Slow?
Post by: iago on July 16, 2009, 06:24:06 pm

Over the next couple days, can you tell me if it gets any better?

I replaced a network cable, and it suddenly got faster. But I also power cycled both my modem/router when doing so, so it may have been a fluke and it may get bad again.

Title: Re: Horribly Slow?
Post by: deadly7 on July 16, 2009, 10:37:43 pm

The irony of this is everytime so far I've tried responding in this thread the forum has died.

edit: OMG THIS WORKED!

Title: Re: Horribly Slow?
Post by: iago on July 16, 2009, 11:33:57 pm

Haha, I guess that answers that question. :)

According to my ISP, they're seeing:

Quote

Jul 12 07:29:53 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 12 08:51:28 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 12 11:07:07 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 12 11:26:10 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 12 13:41:50 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 12 14:24:24 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 12 14:25:25 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 12 16:58:35 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 12 18:14:13 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 12 18:15:43 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 12 18:22:16 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 12 19:00:50 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 02:07:13 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 02:35:16 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 04:54:52 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 04:58:01 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 05:00:02 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 05:04:37 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 05:06:08 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 05:08:40 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 05:09:41 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 05:11:43 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 05:13:47 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 05:16:20 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 05:22:53 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 05:25:59 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 05:29:31 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 05:34:36 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 06:35:10 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 06:37:42 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 06:39:46 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 06:43:19 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 06:45:50 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 06:51:22 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 07:06:54 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 07:10:56 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 07:36:01 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 07:38:32 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 07:39:34 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 07:42:35 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 07:50:07 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 07:51:38 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 07:53:10 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 07:55:41 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 08:00:13 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 08:07:15 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 08:08:46 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 08:10:49 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 08:42:52 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 09:03:54 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 09:39:58 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 09:44:31 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 09:48:36 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 09:51:38 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 09:54:10 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 09:55:41 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 09:59:12 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:04:44 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:10:47 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:13:19 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:14:20 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:16:53 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:19:56 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:21:27 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:22:59 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:24:30 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:27:31 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:30:39 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:34:10 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:35:42 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:37:43 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:40:45 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:45:48 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:47:47 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:49:52 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 10:51:23 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 11:04:26 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 11:05:27 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 11:06:28 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 11:12:01 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 11:14:04 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 11:16:07 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 11:18:09 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 11:27:10 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 11:29:42 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 11:30:43 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 11:32:45 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 14:07:24 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 15:06:00 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 15:15:33 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 15:33:36 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 16:26:42 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 16:56:15 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 17:07:48 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 13 17:21:50 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 01:32:46 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 02:38:53 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 02:45:57 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 05:03:36 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 05:06:10 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 05:10:42 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 05:12:13 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 05:15:20 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 05:17:21 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 05:20:26 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 05:23:00 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 05:25:02 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 05:27:37 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 05:30:40 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 05:44:42 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 06:27:15 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 13:44:42 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 13:58:14 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 13:59:47 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 14 14:03:48 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 01:55:28 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 10:22:55 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 10:31:57 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 12:54:35 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 12:56:07 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 13:32:40 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 20:49:34 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 20:59:36 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 21:00:37 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 21:02:09 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 21:08:40 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 21:12:15 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 21:15:16 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 21:16:46 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 21:17:47 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 15 21:22:52 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 16 05:11:49 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 16 07:37:58 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 16 07:40:01 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 16 11:51:21 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 16 12:30:24 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 16 15:38:35 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 16 16:29:07 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
Jul 16 16:33:14 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready

Not sure why, yet.

Title: Re: Horribly Slow?
Post by: Lead on July 17, 2009, 07:01:02 am

Very slow here, also.

Title: Re: Horribly Slow?
Post by: Chavo on July 17, 2009, 09:15:43 am

Quote from: iago on July 16, 2009, 11:33:57 pm

Haha, I guess that answers that question. :)

According to my ISP, they're seeing:

Quote

Jul 12 07:29:53 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
-snip-

Not sure why, yet.

It really bothers me that ISPs in general don't have tools to find quality degredation like this automatically (ok, they do have some larger scale ones) or at least don't use them.  The wait-until-the-user-complains model is depressing.

Title: Re: Horribly Slow?
Post by: iago on July 17, 2009, 10:43:03 am

Quote from: Chavo on July 17, 2009, 09:15:43 am

Quote from: iago on July 16, 2009, 11:33:57 pm

Haha, I guess that answers that question. :)

According to my ISP, they're seeing:

Quote

Jul 12 07:29:53 l2tp kernel: ADDRCONF(NETDEV_CHANGE): aps81.2.52: link becomes ready
-snip-

Not sure why, yet.

It really bothers me that ISPs in general don't have tools to find quality degredation like this automatically (ok, they do have some larger scale ones) or at least don't use them.  The wait-until-the-user-complains model is depressing.

Well, in fairness my current ISP is a two-man shop. I don't expect them to be proactive about stuff, but the advantage is that, if I need something, I can call up the guy and ask him. :)

Title: Re: Horribly Slow?
Post by: AntiVirus on July 17, 2009, 12:25:32 pm

Quote from: iago on July 15, 2009, 10:44:12 pm

Their service this far has been absolutely unacceptable.

This is unfortunate.  Weren't you rather excited to find a small business to be your ISP after moving?

Quote from: Lead on July 17, 2009, 07:01:02 am

Very slow here, also.

Same.  There has also been a few times where I am unable to access this forum or the other one you are hosting for me, iago.

Title: Re: Horribly Slow?
Post by: Warrior on July 17, 2009, 12:52:54 pm

very speedy for me here

Title: Re: Horribly Slow?
Post by: iago on July 17, 2009, 05:47:39 pm

Quote from: AntiVirus on July 17, 2009, 12:25:32 pm

Quote from: iago on July 15, 2009, 10:44:12 pm

Their service this far has been absolutely unacceptable.

This is unfortunate.  Weren't you rather excited to find a small business to be your ISP after moving?

Yeah -- if I DO change ISPs, it's going to be to another small shop, tohough.. I'm a sucker for the little guys. :)

Title: Re: Horribly Slow?
Post by: deadly7 on July 17, 2009, 07:56:01 pm

Quote from: iago on July 17, 2009, 05:47:39 pm

I'm a sucker for the little guys. :)

A phrase iago's been hearing all of his life.

Title: Re: Horribly Slow?
Post by: MyndFyre on July 17, 2009, 08:02:13 pm

Quote from: deadly7 on July 17, 2009, 07:56:01 pm

Quote from: iago on July 17, 2009, 05:47:39 pm

I'm a sucker for the little guys. :)

A phrase iago's been hearing all of his life.

Using, too. :P

Title: Re: Horribly Slow?
Post by: deadly7 on July 17, 2009, 08:22:40 pm

Quote from: MyndFyre on July 17, 2009, 08:02:13 pm

Using, too. :P

No wonder Ergot decided to join x86...

Title: Re: Horribly Slow?
Post by: Ergot on July 17, 2009, 09:13:29 pm

How could I refuse?

Title: Re: Horribly Slow?
Post by: iago on July 17, 2009, 09:18:18 pm

It's on my t-shirt...

(http://www.javaop.com/~ron/images/pictures/littleguys.jpg)

Title: Re: Horribly Slow?
Post by: Blaze on July 17, 2009, 09:38:54 pm

No, iago!  That drinks not vegan!

Title: Re: Horribly Slow?
Post by: deadly7 on July 17, 2009, 11:34:13 pm

Quote from: Blaze on July 17, 2009, 09:38:54 pm

No, iago!  That drinks not vegan!

THE COFFEE BEANS. THEY WERE TREATED POORLY! OH, WOE IS ME.

Title: Re: Horribly Slow?
Post by: Blaze on July 17, 2009, 11:44:22 pm

Quote from: deadly7 on July 17, 2009, 11:34:13 pm

Quote from: Blaze on July 17, 2009, 09:38:54 pm

No, iago!  That drinks not vegan!

THE COFFEE BEANS. THEY WERE TREATED POORLY! OH, WOE IS ME.

That drink is a Frappachino(tm).  It has incredibly modified dairy, as well as other ingredients that aren't vegan.  :)

Title: Re: Horribly Slow?
Post by: Armin on July 18, 2009, 01:50:13 am

Quote from: deadly7 on July 17, 2009, 11:34:13 pm

Quote from: Blaze on July 17, 2009, 09:38:54 pm

No, iago!  That drinks not vegan!

THE COFFEE BEANS. THEY WERE TREATED POORLY! OH, WOE IS ME.

lawl @ using insult to justify your own meat eating.

Title: Re: Horribly Slow?
Post by: Hitmen on July 18, 2009, 02:07:29 am

Quote from: Blaze on July 17, 2009, 11:44:22 pm

incredibly modified dairy

why don't we have a barf smiley

Title: Re: Horribly Slow?
Post by: deadly7 on July 18, 2009, 02:31:11 am

Quote from: Blaze on July 17, 2009, 11:44:22 pm

That drink is a Frappachino(tm).  It has incredibly modified dairy, as well as other ingredients that aren't vegan.  :)

Yeah but if I joked about that, it wouldn't exactly be funny now would it?

Quote from: Armin on July 18, 2009, 01:50:13 am

lawl @ using insult to justify your own meat eating.

Fail troll is fail, but I would like to use this opportunity to point out that certain sects of Hinduism (mine included) are staunch vegetarians.

Title: Re: Horribly Slow?
Post by: Blaze on July 18, 2009, 03:19:47 am

Quote from: Hitmen on July 18, 2009, 02:07:29 am

Quote from: Blaze on July 17, 2009, 11:44:22 pm

incredibly modified dairy

why don't we have a barf smiley

(http://img119.imageshack.us/img119/2135/emotbarf.gif)

Title: Re: Horribly Slow?
Post by: iago on July 18, 2009, 11:14:56 am

Quote from: Blaze on July 17, 2009, 11:44:22 pm

Quote from: deadly7 on July 17, 2009, 11:34:13 pm

Quote from: Blaze on July 17, 2009, 09:38:54 pm

No, iago!  That drinks not vegan!

THE COFFEE BEANS. THEY WERE TREATED POORLY! OH, WOE IS ME.

That drink is a Frappachino(tm).  It has incredibly modified dairy, as well as other ingredients that aren't vegan.  :)

Haha, whatever. That guy (K-Fed) is a lot thinner and darker skinned than me, too. :)

Title: Re: Horribly Slow?
Post by: iago on July 18, 2009, 06:53:56 pm

So, I jiggled all the cables, and it's been about 2 hours since I've had a dropped connection. *crosses fingers again*

Title: Re: Horribly Slow?
Post by: MyndFyre on July 18, 2009, 09:55:26 pm

Quote from: iago on July 18, 2009, 06:53:56 pm

So, I jiggled all the cables, and it's been about 2 hours since I've had a dropped connection. *crosses fingers again*

Heh heh, I'll BET you "jiggled" those cables.  Bow chicka bow wow!

Title: Re: Horribly Slow?
Post by: iago on July 21, 2009, 03:07:27 pm

So, I went ahead and closed the ticket with my ISP. It seems to be chugging along nicely now.

Let me know if you still notice issues.