Justin Wood (Callek) wrote:
On 5/29/2011 4:25 PM, W3BNR wrote:
Personally I don't think we should have to lie about our browser.
We (SeaMonkey Council) fully agree with you. That said, our users are
higher priority. KaiRo (longtime project member, and Council member) has
proposed, years ago, a theoretical solution to the issue (back when
Firefox was not even recognized by websites, fwiw), the problem is we
don't have the backend gecko support atm, and it would be A LOT of work
to try and implement on our own.
If the support is ever there, we'll gladly use it though.
May I naively suggest the following course:
In effect build agent switcher into SM. First let SM identify itself
correctly. This lets the bean counters get SM into their usage totals.
But if the host objects then let the user be able, on the fly, to switch
to one of a select list of fake ids, (which would also carry
a token to identify it as an SM alias/fake), and try the host again.
(Perhaps the first part of going through the list of fake ids, might
even be scripted and automatic).
I envision the following scenario:
- User tries to enter/link-to/ a site
- Site rejects with a message
- User presses a 'try faking it' button
- SM switches to script of sending fake UAs till success of utter
failure.
Elaborations are obvious: Record UAs tried at the given host and
the results. Report these as incidents to SM central for actions
to try to convince the host owners to correct their behaviour.
Record successes (host identifier & successful UA) to short-cut
trial and error when going again to that host. i.e. build in
memory
--
Rostyk
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
