The GW-Apps is geared toward discussions of Window-Eyes and GW Micro apps. Any subscriber of the GW-Apps list has the ability to post on-topic messages.
From:
"Macarty, Jay {PBSG}" <Jay.Macarty@pepsico.com>Subject:
RE: SocialEyes OutageDate:
Mon, Sep 9, 2013 12:27:34 pmI simply had the idea to summarize all the various discussion points from the weekend. Much of what was there came from various users at one time or another.
-----Original Message-----
From: Chris Skarstad [mailto:rascal0826@verizon.net]
Sent: Monday, September 09, 2013 11:09 AM
To: gw-apps@gwmicro.com
Subject: Re: SocialEyes Outage
Hi. I think Jay came up with some really excellent ideas in his post going over the problem and the whole summary. I do think some kind of error message after a time would be good, and also some kind of error reporting mechanism should be added in too, after all not everyone is computer-savvy enough to realize that it's a real problem with just social-eyes itself. I remember reading a couple emails from people who thought it was something wrong with their pc, and other folks even uninstalled and re-installed it, thinking it was on their end, which it wasn't. In this case, it was on GW's end, and it's important that the users know that from the get-go so they won't spend all kinds of time worrying wether they did something wrong, or thinking their computer is at fault.
I'm glad Social-eyes works again. Yay!
On 9/9/2013 11:43 AM, John wrote:
> Just as I and a few others thought.
> And server issues on your end, I take it.
>
>
> -----Original Message-----
> From: Aaron Smith [mailto:aaron@gwmicro.com]
> Sent: Monday, September 09, 2013 11:41 AM
> To: gw-apps@gwmicro.com
> Subject: Re: SocialEyes Outage
>
>
> It was server issue. We'll do what we can to minimize these types of
> issues in the future.
>
> Thanks,
>
> Aaron
>
> On 9/9/2013 11:00 AM, Jared Rimer wrote:
>> What caused the issue, and hopefully things could be put in place so
>> we are told what was up? I surely couldn't make sense of the error
>> S.E. was giving me, and thats the first place I looked Saturday
>> morning. I logged in Friday evening, but my last status was at 6:40
>> PM on 9/6 maybe because I logged out for dinner and never bothered to
>> log in till Saturday morning.
>>
>> On 9/9/2013 6:04 AM, Aaron Smith wrote:
>>> Greetings,
>>>
>>> We apologize for the inability to connect to Facebook via SocialEyes
>>> over the weekend. The issue has been resolved, and you should be
>>> able to log in successfully now. If you already have SocialEyes
>>> running, you'll need to close it, and then re-launch it.
>>>
>>> Thanks,
>>>
>>> Aaron
>>>
-----Original Message-----
From: Chris Skarstad [mailto:rascal0826@verizon.net]
Sent: Monday, September 09, 2013 11:09 AM
To: gw-apps@gwmicro.com
Subject: Re: SocialEyes Outage
Hi. I think Jay came up with some really excellent ideas in his post going over the problem and the whole summary. I do think some kind of error message after a time would be good, and also some kind of error reporting mechanism should be added in too, after all not everyone is computer-savvy enough to realize that it's a real problem with just social-eyes itself. I remember reading a couple emails from people who thought it was something wrong with their pc, and other folks even uninstalled and re-installed it, thinking it was on their end, which it wasn't. In this case, it was on GW's end, and it's important that the users know that from the get-go so they won't spend all kinds of time worrying wether they did something wrong, or thinking their computer is at fault.
I'm glad Social-eyes works again. Yay!
On 9/9/2013 11:43 AM, John wrote:
> Just as I and a few others thought.
> And server issues on your end, I take it.
>
>
> -----Original Message-----
> From: Aaron Smith [mailto:aaron@gwmicro.com]
> Sent: Monday, September 09, 2013 11:41 AM
> To: gw-apps@gwmicro.com
> Subject: Re: SocialEyes Outage
>
>
> It was server issue. We'll do what we can to minimize these types of
> issues in the future.
>
> Thanks,
>
> Aaron
>
> On 9/9/2013 11:00 AM, Jared Rimer wrote:
>> What caused the issue, and hopefully things could be put in place so
>> we are told what was up? I surely couldn't make sense of the error
>> S.E. was giving me, and thats the first place I looked Saturday
>> morning. I logged in Friday evening, but my last status was at 6:40
>> PM on 9/6 maybe because I logged out for dinner and never bothered to
>> log in till Saturday morning.
>>
>> On 9/9/2013 6:04 AM, Aaron Smith wrote:
>>> Greetings,
>>>
>>> We apologize for the inability to connect to Facebook via SocialEyes
>>> over the weekend. The issue has been resolved, and you should be
>>> able to log in successfully now. If you already have SocialEyes
>>> running, you'll need to close it, and then re-launch it.
>>>
>>> Thanks,
>>>
>>> Aaron
>>>
