Re: reaching gmail in basic html?
Karen Lewellen <[email protected]>
| Newsgroups | gmane.comp.web.lynx.devel |
|---|---|
| Message-ID | <[email protected]> |
where is somewhere? I may need to post the article here for folks to understand. Google has started using a proprietary edition of JavaScript for tracking purposes that they are branding as security. On Wed, 6 Nov 2019, dan d. wrote: > > I read somewher elinks and the like use a subset of java only with inherent limited java functionality. > That is likely what google is seeing when querying a client request. > > On Tue, 5 Nov 2019, Karen Lewellen wrote: > >> Actually, this is not correct. >> I have gotten this duplicated by google accessibility staff. In fact >> Google stated in an article recently that since only crooks turn off >> JavaScript, they will not allow anyone to sign into their gmail account >> without JavaScript. >> When I requested answers for accessibility reasons, one staff member >> duplicated the issue using elinks, and told me that it was because Google >> did not consider elinks to use the "right" kind of JavaScript. >> Later, a different staff member who normally uses links reported that they >> too could no longer reach basic html using the browser. >> This is not a client issue, as I am going directly to google for my gmail >> reading. >> Karen >> >> >> On Tue, 5 Nov 2019, Mouse wrote: >> >>>> The Thunderbird story is interesting because prior to now I could use >>>> elinks and links, which both can incorporate JavaScript to reach my >>>> research gmail account. >>> >>>> They no longer allow it though because google claims it is not the >>>> right kind of JavaScript. Generally speaking I too would love >>>> learning how this is done. >>> >>> This has to depend on something in your client. Google cannot, after >>> all, observe anything about your client except its network behaviour; >>> something is provoking different network behaviour - or, possibly, your >>> client's blind trust in the JS Google is sending it is causing it to >>> refuse you locally without exhibiting _any_ network behaviour. >>> >>> My guess would be that your JS implementation includes some kind of >>> "this is what sort of implementation I am" string, which Google is >>> asking it to send back - or, more stupidly but in my estimation a >>> little more likely, is checking somewhere in the JS code it sends to >>> you. Learning details (without help from Google, which help I doubt >>> would be forthcoming) would probably require inspecting the JS it sends >>> and/or snooping the cleartext of the communication. Neither one sounds >>> trivial to me, though. >>> >>> /~\ The ASCII Mouse >>> \ / Ribbon Campaign >>> X Against HTML [email protected] >>> / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B >>> >>> _______________________________________________ >>> Lynx-dev mailing list >>> [email protected] >>> https://lists.nongnu.org/mailman/listinfo/lynx-dev >>> >> >> _______________________________________________ >> Lynx-dev mailing list >> [email protected] >> https://lists.nongnu.org/mailman/listinfo/lynx-dev >> > > -- > XB > > _______________________________________________ Lynx-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lynx-dev