On 02/12/2016 07:59, Ant wrote:
> On 12/1/2016 7:07 PM, Ant wrote:
>> https://earthengine.google.com/timelapse/
>>
>> Or just in mine? 64-bit W7 HPE SP1's IE11 web browser worked though.
>> What about the rest of you?
>
> OK, I figured it out. Dang send referers!
I suggest sending fake
On 12/1/2016 7:07 PM, Ant wrote:
https://earthengine.google.com/timelapse/
Or just in mine? 64-bit W7 HPE SP1's IE11 web browser worked though.
What about the rest of you?
OK, I figured it out. Dang send referers! :( Thanks all. :)
--
"..., you ready for a little dumpster diving?" "Um...
On 12/1/2016 7:14 PM, Paul B. Gallagher wrote:
Ant wrote:
https://earthengine.google.com/timelapse/
Or just in mine? 64-bit W7 HPE SP1's IE11 web browser worked though.
What about the rest of you?
Thank you in advance. :)
Specify, "fails to work correctly." Precisely what doesn't work as
Ant wrote:
https://earthengine.google.com/timelapse/
Or just in mine? 64-bit W7 HPE SP1's IE11 web browser worked though. What about
the rest
of you?
Thank you in advance. :)
Cool! Never knew about that. Thanks!
It works for me:
User agent: Mozilla/7.0 (Windows NT 12: ; WOW128; rv:66.0)
Gérard wrote on 12/02/2016 04:19 AM:
Dear Ant
I got the following error message:
Ant wrote on 12/02/2016 04:07 AM:
https://earthengine.google.com/timelapse/
Or just in mine? 64-bit W7 HPE SP1's IE11 web browser worked though. What
about the rest of you?
Thank you in advance. :)
Sorry,
On 12/01/2016 10:07 PM, Ant wrote:
https://earthengine.google.com/timelapse/
Or just in mine? 64-bit W7 HPE SP1's IE11 web browser worked though.
What about the rest of you?
Thank you in advance. :)
As a seasoned veteran in these newsgroups it fails to work in your
production profile,
Dear Ant
I got the following error message:
Ant wrote on 12/02/2016 04:07 AM:
https://earthengine.google.com/timelapse/
Or just in mine? 64-bit W7 HPE SP1's IE11 web browser worked though. What
about the rest of you?
Thank you in advance. :)
Sorry, but it looks like your browser is not
Ant wrote:
https://earthengine.google.com/timelapse/
Or just in mine? 64-bit W7 HPE SP1's IE11 web browser worked though.
What about the rest of you?
Thank you in advance. :)
Specify, "fails to work correctly." Precisely what doesn't work as expected?
WFM, FWIW.
--
War doesn't determine
https://earthengine.google.com/timelapse/
Or just in mine? 64-bit W7 HPE SP1's IE11 web browser worked though.
What about the rest of you?
Thank you in advance. :)
--
"Ants die in sugar." --Malawi
Note: A fixed width font (Courier, Monospace, etc.) is required to see
this signature
On 12/01/2016 09:21 PM, Felix Miata wrote:
sean composed on 2016-12-01 18:44 (UTC-0700):
fwiw, 2.49a2 is working perfectly for me... I'm sure our overworked and
underpaid volunteers know there's no need to waste time with 2.40...
I've almost never used chatzilla & never dom Inspector... so
On 12/01/16 8:44 PM, sean wrote:
> Ant wrote:
>> On 12/1/2016 9:08 AM, WaltS48 wrote:
>>> On 12/1/2016 11:59 AM, Ant wrote:
https://blog.seamonkey-project.org/2016/12/01/face-the-music/ :(
>>>
>>> 2.40 needs patched.
>>
>> Yep, badly!
>
> fwiw, 2.49a2 is working perfectly for me... I'm
sean composed on 2016-12-01 18:44 (UTC-0700):
fwiw, 2.49a2 is working perfectly for me... I'm sure our overworked and
underpaid volunteers know there's no need to waste time with 2.40...
I've almost never used chatzilla & never dom Inspector... so no tears
will ever be shed by me when ewong
On 12/01/2016 08:44 PM, sean wrote:
Ant wrote:
On 12/1/2016 9:08 AM, WaltS48 wrote:
On 12/1/2016 11:59 AM, Ant wrote:
https://blog.seamonkey-project.org/2016/12/01/face-the-music/ :(
2.40 needs patched.
Yep, badly!
fwiw, 2.49a2 is working perfectly for me... I'm sure our overworked
Ant wrote:
On 12/1/2016 9:08 AM, WaltS48 wrote:
On 12/1/2016 11:59 AM, Ant wrote:
https://blog.seamonkey-project.org/2016/12/01/face-the-music/ :(
2.40 needs patched.
Yep, badly!
fwiw, 2.49a2 is working perfectly for me... I'm sure our overworked and
underpaid volunteers know there's
On 12/1/2016 10:46 AM, TCW wrote:
> On 12/1/2016 12:29 PM, NoOp wrote:
>> On 12/1/2016 10:23 AM, TCW wrote:
>>> On 12/1/2016 12:12 PM, NoOp wrote:
On 12/01/2016 08:40 AM, Lee wrote:
> On 12/1/16, TCW <"."> wrote:
>> On 11/30/2016 8:06 AM, WaltS48 wrote:
There's a zero-day
On 12/1/2016 12:29 PM, NoOp wrote:
On 12/1/2016 10:23 AM, TCW wrote:
On 12/1/2016 12:12 PM, NoOp wrote:
On 12/01/2016 08:40 AM, Lee wrote:
On 12/1/16, TCW <"."> wrote:
On 11/30/2016 8:06 AM, WaltS48 wrote:
There's a zero-day exploit in the wild that's being used to execute
malicious code on
On 12/1/2016 10:23 AM, TCW wrote:
> On 12/1/2016 12:12 PM, NoOp wrote:
>> On 12/01/2016 08:40 AM, Lee wrote:
>>> On 12/1/16, TCW <"."> wrote:
On 11/30/2016 8:06 AM, WaltS48 wrote:
>> There's a zero-day exploit in the wild that's being used to execute
>> malicious code on the computers
On 12/1/2016 12:02 PM, Chris Ilias wrote:
On 01/12/2016 12:52 PM, TCW wrote:
I was *told* to not post long URLs before by Chris I and someone else.
Short URLs is the preferred method is what I was told.
I never said that. I told you not to refer to contributor builds as
official releases.
On 12/1/2016 12:12 PM, NoOp wrote:
On 12/01/2016 08:40 AM, Lee wrote:
On 12/1/16, TCW <"."> wrote:
On 11/30/2016 8:06 AM, WaltS48 wrote:
There's a zero-day exploit in the wild that's being used to execute
malicious code on the computers of people using Tor and possibly other
users of the
On 12/01/2016 10:12 AM, NoOp wrote:
> On 12/01/2016 08:40 AM, Lee wrote:
>> On 12/1/16, TCW <"."> wrote:
>>> On 11/30/2016 8:06 AM, WaltS48 wrote:
> There's a zero-day exploit in the wild that's being used to execute
> malicious code on the computers of people using Tor and possibly other
On 12/01/2016 08:40 AM, Lee wrote:
> On 12/1/16, TCW <"."> wrote:
>> On 11/30/2016 8:06 AM, WaltS48 wrote:
There's a zero-day exploit in the wild that's being used to execute
malicious code on the computers of people using Tor and possibly other
users of the Firefox browser,
On 01/12/2016 12:52 PM, TCW wrote:
I was *told* to not post long URLs before by Chris I and someone else.
Short URLs is the preferred method is what I was told.
I never said that. I told you not to refer to contributor builds as
official releases.
On 12/1/2016 10:40 AM, Lee wrote:
On 12/1/16, TCW <"."> wrote:
On 11/30/2016 8:06 AM, WaltS48 wrote:
There's a zero-day exploit in the wild that's being used to execute
malicious code on the computers of people using Tor and possibly other
users of the Firefox browser, officials of the
On 12/1/2016 9:08 AM, WaltS48 wrote:
On 12/1/2016 11:59 AM, Ant wrote:
https://blog.seamonkey-project.org/2016/12/01/face-the-music/ :(
2.40 needs patched.
Yep, badly!
--
"Ever watch ants just crawling around? They walk in that single straight
line, a long, a long, long mile of ants.
On 12/1/2016 11:59 AM, Ant wrote:
https://blog.seamonkey-project.org/2016/12/01/face-the-music/ :(
2.40 needs patched.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
https://blog.seamonkey-project.org/2016/12/01/face-the-music/ :(
--
"They are like the ant... They start one way and turn around and go the
other way... They look all the time at the ground and never see the
sky." --Davi Kopenawa Yanomami, Amazonian Indian (Newsweek 117(17):5, 1991)
Note: A
On 12/1/16, TCW <"."> wrote:
> On 11/30/2016 8:06 AM, WaltS48 wrote:
>>> There's a zero-day exploit in the wild that's being used to execute
>>> malicious code on the computers of people using Tor and possibly other
>>> users of the Firefox browser, officials of the anonymity service
>>> confirmed
On 12/1/16, Frank-Rainer Grahl wrote:
> Likely 2.40 is affected. There will always be 0 day bugs and even a
> fully patched Firefox will contain some. That is why I use Noscript and
> an Adblocker. If a site wants that I turn off the Adblocker its a site I
> will no longer visit.
On 12/1/16, Ray_Net wrote:
> WaltS48 wrote on 30-11-16 15:06:
>>> There's a zero-day exploit in the wild that's being used to execute
>>> malicious code on the computers of people using Tor and possibly
>>> other users of the Firefox browser, officials of the
On 11/30/2016 8:06 AM, WaltS48 wrote:
There's a zero-day exploit in the wild that's being used to execute
malicious code on the computers of people using Tor and possibly other
users of the Firefox browser, officials of the anonymity service
confirmed Tuesday.
The versions span from 41 to
Likely 2.40 is affected. There will always be 0 day bugs and even a
fully patched Firefox will contain some. That is why I use Noscript and
an Adblocker. If a site wants that I turn off the Adblocker its a site I
will no longer visit. Even with Noscript there is a risk that a
whitelisted site
I am not sure where this version comes from. A previous post indicate
that its just Adrians version without credits given. Whatever. Do not
use it or file bugs against it.
You can get the unoffical versions from:
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/
Bugs
The location will change. In 2.47+ it is now:
chrome://communicator/content/console/console.xul
FRG
David E. Ross wrote:
On 11/30/2016 1:02 PM, Jonathan N. Little wrote:
I have Web Developer bar installed and the console button no longer works.
URL chrome://global/content/console.xul does,
WaltS48 wrote on 30-11-16 15:06:
There's a zero-day exploit in the wild that's being used to execute
malicious code on the computers of people using Tor and possibly
other users of the Firefox browser, officials of the anonymity
service confirmed Tuesday.
The versions span from 41 to 50,
34 matches
Mail list logo