Re: Unsupported Browser Notice

2019-04-25 Thread Ray_Net

Ant wrote on 25-04-19 10:55:

On 4/24/2019 2:12 PM, Paul B. Gallagher wrote:

Brian Mailman wrote:


Windows 10
Seamonkey 2.48

Hi, I'm now receiving a notice of "Unsupported Browser" and that my 
Seamonkey is "outdated" when I try to go to davita.com .


The notice recommends Firefox, among others. I forget where the 
setting is, but I do have this copy of Seamonkey set to identify 
itself as Firefox!


Help?  Thanks in advance.


Simply disable "Advertise Firefox compatibility" and reload:

Edit | Preferences | Advanced | HTTP Networking

It's weird that they're demanding Firefox but rejecting a browser 
that says it's Firefox-compatible in favor of one that doesn't. But 
web designers aren't always the sharpest pencils in the box.


Nice find. This issue should be reported to the web site owners to 
sniff SM's UA correctly.


I think that they don't care about a dying product 
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Unsupported Browser Notice

2019-04-25 Thread NFN Smith

WaltS48 wrote:
If you read my previous reply and the one from Paul B. Gallagher, you 
see that we get the page to load and don't get an Unsupported Browser 
Notice when disabling "Advertise Firefox Compatibility".



Right.  I managed not to address that.  If turning off advertising 
compatibility works, do it.


Smith

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


Re: Unsupported Browser Notice

2019-04-25 Thread WaltS48

On 4/25/19 3:13 PM, NFN Smith wrote:

Brian Mailman wrote:

Windows 10
Seamonkey 2.48

Hi, I'm now receiving a notice of "Unsupported Browser" and that my 
Seamonkey is "outdated" when I try to go to davita.com .


The notice recommends Firefox, among others. I forget where the 
setting is, but I do have this copy of Seamonkey set to identify 
itself as Firefox!



This one is a growing issue, and has been since the release of Firefox, 
circa 57.0. A growing number of site operators are rejecting older 
versions as "dated" (and with known security issues), and I know that 
there were sites rejecting Firefox 52.x ESR implementations (even if 
still supported) before 60.x ESR was released.


I haven't seen it a lot, although I know of one financial institution 
that I deal with that complains about outdated browser, although it 
doesn't deny access.


There's a significant number of Web developers and admins that really 
don't know browsers well, what's supported or not.  A further problem is 
that most web sites get significant amounts of bot-generated traffic 
that use forged User Agent strings.  I've done some work on that with my 
own web site, and even though I go conservatively, I still reject a lot 
of traffic that shows old versions of browsers, or User Agent strings 
that have syntax errors that are obviously forged.


One of the dynamics is that with Google Chrome, they're aggressive 
enough about forcing updates on users that for a site operator, it's 
generally safe to assume that anything that's more than about 2 versions 
older than the most current version, it's safe to assume that it's 
forged, and is safe to reject.  This effect is amplified by both 
developers and admins that mostly live in Chrome (and don't know much 
about Mozilla's architecture, including Seamonkey as a derivative).


Although historically, Seamonkey users have sometimes had to struggle 
with sites that demand Firefox (especially before Seamonkey started 
advertising Firefox compatibility), it is becoming more common that 
sites reject Seamonkey, not necessarily because of Seamonkey, but that 
it's advertising compatibility with Firefox 52.


I do some with spoofing using PrefBar, and I have some number of spoofs 
of other browsers that I may make use of occasionally.  So far, I 
haven't really had to try to spoof Seamonkey 53 or 57 (and Firefox 60 
capacity), but I anticipate doing so before too long.


I did check davita.com, and none of the spoofing I use (whether a stock 
Firefox 60, or for that matter, stock Chrome or Opera strings) are 
getting me past that complaint.  At that stage, it's a pretty good guess 
that the site developer/admin is doing browser sniffing badly. However, 
it's also a guess that they see few enough Seamonkey users (other than 
you) that they're not going to bother to make any changes.


You may need to simply bite the bullet and use another browser for that 
site.


Smith


If you read my previous reply and the one from Paul B. Gallagher, you 
see that we get the page to load and don't get an Unsupported Browser 
Notice when disabling "Advertise Firefox Compatibility".




--
OS: Linux Mint 19.1 - Cinnamon Desktop
https://www.thunderbird.net/en-US/get-involved/

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


Re: Unsupported Browser Notice

2019-04-25 Thread NFN Smith

Brian Mailman wrote:

Windows 10
Seamonkey 2.48

Hi, I'm now receiving a notice of "Unsupported Browser" and that my 
Seamonkey is "outdated" when I try to go to davita.com .


The notice recommends Firefox, among others. I forget where the setting 
is, but I do have this copy of Seamonkey set to identify itself as Firefox!



This one is a growing issue, and has been since the release of Firefox, 
circa 57.0. A growing number of site operators are rejecting older 
versions as "dated" (and with known security issues), and I know that 
there were sites rejecting Firefox 52.x ESR implementations (even if 
still supported) before 60.x ESR was released.


I haven't seen it a lot, although I know of one financial institution 
that I deal with that complains about outdated browser, although it 
doesn't deny access.


There's a significant number of Web developers and admins that really 
don't know browsers well, what's supported or not.  A further problem is 
that most web sites get significant amounts of bot-generated traffic 
that use forged User Agent strings.  I've done some work on that with my 
own web site, and even though I go conservatively, I still reject a lot 
of traffic that shows old versions of browsers, or User Agent strings 
that have syntax errors that are obviously forged.


One of the dynamics is that with Google Chrome, they're aggressive 
enough about forcing updates on users that for a site operator, it's 
generally safe to assume that anything that's more than about 2 versions 
older than the most current version, it's safe to assume that it's 
forged, and is safe to reject.  This effect is amplified by both 
developers and admins that mostly live in Chrome (and don't know much 
about Mozilla's architecture, including Seamonkey as a derivative).


Although historically, Seamonkey users have sometimes had to struggle 
with sites that demand Firefox (especially before Seamonkey started 
advertising Firefox compatibility), it is becoming more common that 
sites reject Seamonkey, not necessarily because of Seamonkey, but that 
it's advertising compatibility with Firefox 52.


I do some with spoofing using PrefBar, and I have some number of spoofs 
of other browsers that I may make use of occasionally.  So far, I 
haven't really had to try to spoof Seamonkey 53 or 57 (and Firefox 60 
capacity), but I anticipate doing so before too long.


I did check davita.com, and none of the spoofing I use (whether a stock 
Firefox 60, or for that matter, stock Chrome or Opera strings) are 
getting me past that complaint.  At that stage, it's a pretty good guess 
that the site developer/admin is doing browser sniffing badly. However, 
it's also a guess that they see few enough Seamonkey users (other than 
you) that they're not going to bother to make any changes.


You may need to simply bite the bullet and use another browser for that 
site.


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


Re: Boolean Expressions in filters ..... Possible??

2019-04-25 Thread NFN Smith

Daniel wrote:
I'm trying to set up some filters to apply to some/all of my UseNet 
groups, and I think they would effectively be Boolean Expressions, so 
I'm wondering if they are possible??


Some examples might be .

1.    If Lines>99  Total Posts=1 then Mark as Read.
 (i.e. a very long post/rant that no one replied to)

2.    If TotalPosts  Unread then Mark as Read.
 (Maybe a responder is already the subject of a filter, so their
 posts would already be Mark as Read, so get rid of the thread.)

3.    If Newsgroups  ParticularNewsgroup then Mark as Read.
 (Some groups seem to attract REAL loonies, so if those groups
 are cross-posted to, I'm not interested in thread)



I've found the filters capacity of Mozilla's mail clients (both 
Thunderbird and Seamonkey) to be somewhat limited.


I will suggest that your request of "boolean" is misplaced.  Boolean 
addresses the logic of AND, OR and NOT -- essentially grouping 
conditions there. Personally, I find it frustrating that there's no 
capacity for mixing AND and OR with parens -- e.g., "x AND (y OR z) AND 
NOT a".  Filters with multiple conditions are pretty much limited to 
"match all" or "match any", and that's it.


However, your question isn't really related to Boolean operators, so 
much as what kinds of conditions you can include in your filters.


For items 1 and 2, I don't believe that's possible within the existing 
structure.  These are ones that take calculation (and likely, 
interaction with the news server itself).  There's a lot of different 
servers that support nntp, but I'm not aware of any of them that will 
allow a remote client to interact at this level.


For item 3, I think you can do a filter that will trigger if a 
particular group is listed in the Newsgroups: header.


In the filters dialog, there is a setting for "Custom", but for the most 
part, I think it's limited to checking specific header entries.


Although I've noted annoyance at the limitations of what can be done 
with filters, the reality is that I think changes will never show up in 
Seamonkey.  Anything that comes is going to have to originate in 
Thunderbird, and I've seen little indication over a lot of years that 
the TB developers have any interest in trying to make any significant 
changes there.


That said, I know that there's a Thunderbird extension called 
FiltaQuilla 
https://addons.thunderbird.net/en-US/seamonkey/addon/filtaquilla/.  I've 
never tried it, and have no idea if it will run in Seamonkey, or not. 
That might give you a little more capacity, but a quick check indicates 
it's more mail-focused than anything that will change much in handling 
of news messages.


Realistically, if you want more filters handling with news than you're 
already seeing with Seamonkey, you'll probably need to look for other 
news clients. And even then, some of what you're asking for is likely 
not to be offered in any news client.


Smith



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


Re: Unsupported Browser Notice

2019-04-25 Thread chokito
Works fine in 2.49.5 with user agent "Mozilla/5.0 (Windows NT 6.1; Win64; x64; 
rv:66.0) Gecko/20100101 Firefox/66.0"
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Unsupported Browser Notice

2019-04-25 Thread Ant via support-seamonkey

On 4/24/2019 2:12 PM, Paul B. Gallagher wrote:

Brian Mailman wrote:


Windows 10
Seamonkey 2.48

Hi, I'm now receiving a notice of "Unsupported Browser" and that my 
Seamonkey is "outdated" when I try to go to davita.com .


The notice recommends Firefox, among others. I forget where the 
setting is, but I do have this copy of Seamonkey set to identify 
itself as Firefox!


Help?  Thanks in advance.


Simply disable "Advertise Firefox compatibility" and reload:

Edit | Preferences | Advanced | HTTP Networking

It's weird that they're demanding Firefox but rejecting a browser that 
says it's Firefox-compatible in favor of one that doesn't. But web 
designers aren't always the sharpest pencils in the box.


Nice find. This issue should be reported to the web site owners to sniff 
SM's UA correctly.

--
"Ants live safely till they have gotten wings." --unknown
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\ http://aqfl.net & http://antfarm.ma.cx /
  / /\ /\ \ http://antfarm.home.dhs.org
 | |o   o| |   Axe ANT from its address if shown & e-mailing privately.
\ _ /   Please kindly use Ant nickname & URL/link if crediting.
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Unsupported Browser Notice

2019-04-25 Thread Ant via support-seamonkey
You might have to change your web browser's user agent. Its home page 
worked for me with "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) 
Gecko/20100101 Firefox/52.0" on my decade old, updated 64-bit W7 HPE SP1 
PC's SeaMonkey v2.49.4 web browser. Maybe try changing its user agent?



On 4/24/2019 12:50 PM, Brian Mailman wrote:

Windows 10
Seamonkey 2.48

Hi, I'm now receiving a notice of "Unsupported Browser" and that my 
Seamonkey is "outdated" when I try to go to davita.com .


The notice recommends Firefox, among others. I forget where the setting 
is, but I do have this copy of Seamonkey set to identify itself as Firefox!


Help?  Thanks in advance.-- 

"Thanks for giving me the courage to eat all those ants." --unknown
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\ http://aqfl.net & http://antfarm.ma.cx /
  / /\ /\ \ http://antfarm.home.dhs.org
 | |o   o| |   Axe ANT from its address if shown & e-mailing privately.
\ _ /   Please kindly use Ant nickname & URL/link if crediting.
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey