Re: Anyone else having trouble using Firefox Accounts login from SeaMonkey?

2018-01-27 Thread WaltS48 

On 1/27/18 3:05 PM, Ricardo Palomares Martí­nez wrote:

Hi,

I've noticed in the last few days that I can't login into Mozilla
Add-ons or Pontoon from SeaMonkey due to Firefox Accounts login system
not working. From, for instance, Pontoon, I choose Sign in and get
redirected here ("***" shows deleted data, not actual values):

https://accounts.firefox.com/oauth/?redirect_uri=https%3A%2F%2Fpontoon.mozilla.org%2Faccounts%2Ffxa%2Flogin%2Fcallback%2F_id=***_type=code==profile%3Aemail%20profile%3Adisplay_name%20profile%3Auid%20profile%3Auid%20profile%3Aemail%20profile%3Adisplay_name

It shows an almost blank page with the Mozilla logo in the upper right
corner and a progress spin in the center.

Webtools console shows this error message:


"  920c7d2a.main.es_ES.js:35:8783
Response not received for: fxaccounts:fxa_status
920c7d2a.main.es_ES.js:18:4662
d.prototype.error
https://accounts-static.cdn.mozilla.net/scripts/920c7d2a.main.es_ES.js:18:4662
d.prototype.add/b.timeout<
https://accounts-static.cdn.mozilla.net/scripts/920c7d2a.main.es_ES.js:22:5118


Are other people successfully using Firefox Accounts from SeaMonkey
lately?

TIA



Possibly those that don't have "Mozilla/55.0 (Windows NT 10.0; Win128; 
x128; rv:57.0) Gecko/20200101 Firefox/77.0" as their User Agent String.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Anyone else having trouble using Firefox Accounts login from SeaMonkey?

2018-01-27 Thread Ricardo Palomares Martí­nez 
Hi,

I've noticed in the last few days that I can't login into Mozilla
Add-ons or Pontoon from SeaMonkey due to Firefox Accounts login system
not working. From, for instance, Pontoon, I choose Sign in and get
redirected here ("***" shows deleted data, not actual values):

https://accounts.firefox.com/oauth/?redirect_uri=https%3A%2F%2Fpontoon.mozilla.org%2Faccounts%2Ffxa%2Flogin%2Fcallback%2F_id=***_type=code==profile%3Aemail%20profile%3Adisplay_name%20profile%3Auid%20profile%3Auid%20profile%3Aemail%20profile%3Adisplay_name

It shows an almost blank page with the Mozilla logo in the upper right
corner and a progress spin in the center.

Webtools console shows this error message:


"  920c7d2a.main.es_ES.js:35:8783
Response not received for: fxaccounts:fxa_status
920c7d2a.main.es_ES.js:18:4662
d.prototype.error
https://accounts-static.cdn.mozilla.net/scripts/920c7d2a.main.es_ES.js:18:4662
d.prototype.add/b.timeout<
https://accounts-static.cdn.mozilla.net/scripts/920c7d2a.main.es_ES.js:22:5118


Are other people successfully using Firefox Accounts from SeaMonkey
lately?

TIA

-- 
Proyecto NAVE (Mozilla es-ES Localization Team)
Mozilla Hispano Community
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey cannot access a web site Chrome can.

2018-01-27 Thread Ed Mullen 
On 1/26/2018 at 12:59 PM, Rob Steinmetz created this epitome of digital 
genius:
I have a remote site. The people at that site cannot access a internal 
website we use at another location. I have had the users clear their 
cache and try to access the site. Chrome on the same machines can access 
the site. They can ping the ip address.


I'm looking for a way to figure out what is causing SeaMonkey to not 
load the website.


Are the users getting any error message?  Any message at all? What 
happens when they try to go to the URL?



--
Ed Mullen
http://edmullen.net/
If an orange is orange, why isn't a lime called a green or a lemon 
called a yellow?

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Version Numbers 52.0 or 52.6.0 in user agent

2018-01-27 Thread David E. Ross 
On 1/27/2018 1:04 AM, Daniel wrote:
> WaltS48 wrote:
>> On 1/25/18 11:18 PM, Daniel wrote:
>>> David E. Ross wrote:
 On 1/25/2018 8:32 AM, WaltS48 wrote:
> On 1/25/18 10:56 AM, David E. Ross wrote:
>> On 1/25/2018 3:44 AM, Daniel wrote:
>>> David E. Ross wrote:
 On 1/24/2018 7:51 PM, Daniel wrote:
> Frank-Rainer Grahl wrote:
>> 2.49.1 is based on ESR 52.4
>> 2.49.2 should (hopefully) arrive in the next 2-3 weeks and will 
>> be based
>> on 52.6
>>
>> Firefox does not show minor version numbers in its UA string.
>>
>> 52.5.3 ESR:
>> Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101
>> Firefox/52.0
>>
>> 2.49.2 x 64 local build:
>> Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101
>> Firefox/52.0 SeaMonkey/2.49.2
>>
>> As you can see almost identical but as usual google and others 
>> will do
>> incorrect user agent sniffing.
>>
>> FRG
> That's interesting!! Being a long term SM user, it has always 
> intrigued
> me why the Gecko number has not been updated in yonks 
> (20100101)... but
> now I see that probably stems from FF, which also doesn't seem 
> to update
> its Gecko release date!!
>
> Presumably the Gecko engine *HAS* actually been updated!! ;-P
>
 Not updating the version date for Gecko in the user agent string 
 is part
 of Mozilla's plan to obscure user characteristics.  Web servers 
 sniffing
 user data supposedly find it harder to track individual users. 
 See bug
 #1329996 at .

 I prefer relying on the Secret Agent extension from
 .

>>> Then one would have to wonder what use it is to have the Gecko 
>>> version
>>> with-in the User-Agent string at all!! ;-(
>>>
>> Some Web servers insist on sniffing the user agent string and expect
>> some kind of date for Gecko.  Mozilla-based browsers fail to work on
>> such Web sites unless there is a date field.
>>
> An example please.

 I do not have an example.  I recall reading in a bug report (now
 apparently closed) that omitting the Gecko date was causing problems
 with Web servers that sniff the UA.

>>> I seem to recall that some/many sites fail to function for SeaMonkey 
>>> unless the SeaMonkey UA had FF in it ... in some cases *Only FF* in 
>>> the SM UA
>>>
>>> So why the mention, now, of some sniffing for Gecko?? Is that Gecko 
>>> *only* or Gecko *as well* now??
>>>
>>
>> Some light reading for you Daniel, and anyone else that might be 
>> interested.
>>
>> https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent
>>
>> Enjoy!
>>
> Interesting!! The example Chrome/Chromium and Opera and Safari UA 
> strings mention "like Gecko" but do not give a version date!!
> 
> And, Walt, the link you provided had a further link to ...
> 
> https://developer.mozilla.org/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent
> 
> which mentions 
> 
> "It's worth re-iterating: it's very rarely a good idea to use user agent 
> sniffing. You can almost always find a better, more broadly compatible 
> way to solve your problem!"
> 
> Which has long been re-iterated in these groups!! And, again, in the 
> para "Are you trying to check for the existence of a specific feature?", 
> it states "You should never do user agent sniffing" with the word 
> "never" in Bold!!
> 

Sniffing began when Web developers got the not-so-smart idea they could
take advantage of non-standard features of different browsers to provide
"enhanced" Web pages.  Unfortunately, most of those non-standard
features were actually bugs.  Even more unfortunately, the developers
had to fix their Web pages as thos bugs were fixed.  Many of those
developers are still making new Web pages and still trying to use
non-standard features.

-- 
David E. Ross


President Trump:  Please stop using Twitter.  We need
to hear your voice and see you talking.  We need to know
when your message is really your own and not your attorney's.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Moving to a new machine

2018-01-27 Thread Frank-Rainer Grahl 
If the new PC is blank or the old installation does not be preserved I am 
usually using zip -r -S with the whole mozilla dir in roaming. If SeaMonkey 
has already been installed just delete the complete roaming\mozilla dir on the 
new pc before unpacking. Same with roaming\Thunderbird.


FRG

Ray_Net wrote:

rickman wrote on 27-01-18 01:23:
I had to give up on my on my old laptop (Lenovo piece of ...) and got a new 
one.  I want to move all my newsgroup files to the new machine. Oddly enough 
when I search on doing this I find info on moving Thunderbird.  They say to 
use Mozbackup.  Will that work with Seamonkey?


Otherwise they talk about copying the profile folder contents. Should that 
work ok with Seamonkey?



YES

I should copy what's inside this directory:
C:\Users\tit_p\AppData\Roaming\Mozilla\SeaMonkey\Profiles\ey8r9gln.default\

Or you copy
C:\Users\tit_p\AppData\Roaming\Mozilla\SeaMonkey\

note "tit-p" is my user-account-name.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Version Numbers 52.0 or 52.6.0 in user agent

2018-01-27 Thread Daniel 

WaltS48 wrote:

On 1/25/18 11:18 PM, Daniel wrote:

David E. Ross wrote:

On 1/25/2018 8:32 AM, WaltS48 wrote:

On 1/25/18 10:56 AM, David E. Ross wrote:

On 1/25/2018 3:44 AM, Daniel wrote:

David E. Ross wrote:

On 1/24/2018 7:51 PM, Daniel wrote:

Frank-Rainer Grahl wrote:

2.49.1 is based on ESR 52.4
2.49.2 should (hopefully) arrive in the next 2-3 weeks and will 
be based

on 52.6

Firefox does not show minor version numbers in its UA string.

52.5.3 ESR:
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101
Firefox/52.0

2.49.2 x 64 local build:
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101
Firefox/52.0 SeaMonkey/2.49.2

As you can see almost identical but as usual google and others 
will do

incorrect user agent sniffing.

FRG
That's interesting!! Being a long term SM user, it has always 
intrigued
me why the Gecko number has not been updated in yonks 
(20100101)... but
now I see that probably stems from FF, which also doesn't seem 
to update

its Gecko release date!!

Presumably the Gecko engine *HAS* actually been updated!! ;-P

Not updating the version date for Gecko in the user agent string 
is part
of Mozilla's plan to obscure user characteristics.  Web servers 
sniffing
user data supposedly find it harder to track individual users. 
See bug

#1329996 at .

I prefer relying on the Secret Agent extension from
.

Then one would have to wonder what use it is to have the Gecko 
version

with-in the User-Agent string at all!! ;-(


Some Web servers insist on sniffing the user agent string and expect
some kind of date for Gecko.  Mozilla-based browsers fail to work on
such Web sites unless there is a date field.


An example please.


I do not have an example.  I recall reading in a bug report (now
apparently closed) that omitting the Gecko date was causing problems
with Web servers that sniff the UA.

I seem to recall that some/many sites fail to function for SeaMonkey 
unless the SeaMonkey UA had FF in it ... in some cases *Only FF* in 
the SM UA


So why the mention, now, of some sniffing for Gecko?? Is that Gecko 
*only* or Gecko *as well* now??




Some light reading for you Daniel, and anyone else that might be 
interested.


https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent

Enjoy!

Interesting!! The example Chrome/Chromium and Opera and Safari UA 
strings mention "like Gecko" but do not give a version date!!


And, Walt, the link you provided had a further link to ...

https://developer.mozilla.org/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent

which mentions 

"It's worth re-iterating: it's very rarely a good idea to use user agent 
sniffing. You can almost always find a better, more broadly compatible 
way to solve your problem!"


Which has long been re-iterated in these groups!! And, again, in the 
para "Are you trying to check for the existence of a specific feature?", 
it states "You should never do user agent sniffing" with the word 
"never" in Bold!!


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171016030418


User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171015235623

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey