Re: [Lynx-dev] a solution for this problem?
On 2023-01-21 19:34, Thorsten Glaser wrote: >> Only way I could share it is as an attachment, >> its something like three pages of characters. > > I guess that's just too long then. Links (GET requests specifically) > aren't required to work if they're above 1024 characters long. According to RFC 7230 (which sets out the requirements for URIs/URLs), section 3.1.1, It is RECOMMENDED that all HTTP senders and recipients support, at a minimum, request-line lengths of 8000 octets. https://www.rfc-editor.org/rfc/rfc7230#section-3.1.1 There were some long-standing limitations in certain browsers (glares at IE) where URLs over 2000 characters would cause problems, but most servers and user-agents should handle that just fine. And according to RFC 2119, RECOMMENDED/SHOULD definitions: SHOULD: This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. https://www.rfc-editor.org/rfc/rfc2119 So if lynx or links is balking at limits above 1024 bytes, perhaps that ought to be raised to at least a baseline of 8000 bytes? -tim
Re: [Lynx-dev] a solution for this problem?
Karen Lewellen dixit: > Only way I could share it is as an attachment, its something like three pages > of characters. I guess that’s just too long then. Links (GET requests specifically) aren’t required to work if they’re above 1024 characters long. bye, //mirabilos -- Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit gerechnet, darum bin ich blutverschmiert… wer konnte ahnen, daß SIE so reagier’n… gestern Nacht ist mein IRC-Netzwerk explodiert~~~ (as of 2021-06-15 The MirOS Project temporarily reconvenes on OFTC)
Re: [Lynx-dev] a solution for this problem?
Links the chain had the same problem, badly formed address. Making it not just a lynx the cat issue. Only way I could share it is as an attachment, its something like three pages of characters. On Fri, 20 Jan 2023, Luke at Shellworld Support wrote: On Fri, 20 Jan 2023, Karen Lewellen wrote: Oh, just the standard https:// comes before. Then I, at least, find that very strange. I have never run into that error for other than a javascript: URL, a data URL as someone else mentioned, or some other kind of function-based URL that lynx can't handle, but that you can sometimes edit into a more usable shape. I have not run into it rejecting an https URL with that error. It would still be nice to see the entire URL, including the data after the question mark, but I realize you probably can't copy and paste, and it's not worth the trouble of typing across at this point. Luke
Re: [Lynx-dev] a solution for this problem?
On Fri, 20 Jan 2023, Karen Lewellen wrote: > Oh, just the standard https:// > comes before. Then I, at least, find that very strange. I have never run into that error for other than a javascript: URL, a data URL as someone else mentioned, or some other kind of function-based URL that lynx can't handle, but that you can sometimes edit into a more usable shape. I have not run into it rejecting an https URL with that error. It would still be nice to see the entire URL, including the data after the question mark, but I realize you probably can't copy and paste, and it's not worth the trouble of typing across at this point. Luke
Re: [Lynx-dev] a solution for this problem?
Oh, just the standard https:// comes before. On Fri, 20 Jan 2023, Luke at Shellworld Support wrote: On Thu, 19 Jan 2023, Karen Lewellen wrote: what comes after the colon is However, I requested what comes before the colon. Luke
Re: [Lynx-dev] a solution for this problem?
On Thu, 19 Jan 2023, Karen Lewellen wrote: > what comes after the colon is However, I requested what comes before the colon. Luke
Re: [Lynx-dev] a solution for this problem?
On second thought I dug up an old post in the thread to check. what comes after the colon is ecromclick.verizonwireless.com/omclick.document/? and a lot of odd characters. Google as I said states badly formed address. Not to be confused with bad HTML no form has been defined. as for finding another email address, I recall asking before. My professional needs for research and high level document work means a an address with a web interface that works in lynx. The interface automatically tries to convert files to .html, which google does, lets me save files otherwise, and displays in .html, something apparently alpine now has issues with, there is a current thread about it on the alpine discussion list. Personally, with my fully owning dreamhost may not be the best example, Imap and Alpine absolutely terrify me, it freezes, shuts down when I am writing an email, does not display attachments, etc. I may feel differently about imap once I get to test it, via shellworld, using pine, for the lost gmail account I currently have on forward. However, my preference is outlined above, and if there is an idea I will investigate the door. Karen On Thu, 19 Jan 2023, Karen Lewellen wrote: It is unlikely I can test this now. The terms of service were time sensitive, so we found a different way to address the issue. Can you expand on what you felt I might find? Intend raising the problem with Verizon's accessibility team. Kare On Thu, 19 Jan 2023, Luke at Shellworld Support wrote: > In fact, the error, badly formed address, > Is one I have not encountered before. I have. It can mean a few things if I recall correctly. If, instead of enter, you press "E" on that link (that is, a capital E), then the home key or Ctrl+A, it will put you at the start of whatever link it is trying to take you to, in an edit field. What do you see as the part of the link before the colon? Luke
Re: [Lynx-dev] a solution for this problem?
Oh I did that. One test came to my office, which uses links built for JavaScript. it is not a gmail address. Still failed. On Fri, 20 Jan 2023, Thorsten Glaser wrote: Karen Lewellen dixit: Intend raising the problem with Verizon's accessibility team. It’s only half likely they’re even at fault/able to fix this. In your situation I can only *strongly* urge you to find an eMail solution different to Googlemail (considering, also, what others hinted at, regarding nōn-JavaScript usability in near future). Good luck, //mirabilos PS: Personally, I find pine very usable, for a text program. Getting either it or alpine set up at Shellworld is very likely trivial, and then you can use normal SMTP and IMAP for eMail. I’m not sure how usable it is with Braille lines (might need more than 60 columns) or text-to-speech though. Memorising the keystrokes needed to use it is quick. -- “Having a smoking section in a restaurant is like having a peeing section in a swimming pool.” -- Edward Burr
Re: [Lynx-dev] a solution for this problem?
It is unlikely I can test this now. The terms of service were time sensitive, so we found a different way to address the issue. Can you expand on what you felt I might find? Intend raising the problem with Verizon's accessibility team. Kare On Thu, 19 Jan 2023, Luke at Shellworld Support wrote: In fact, the error, badly formed address, Is one I have not encountered before. I have. It can mean a few things if I recall correctly. If, instead of enter, you press "E" on that link (that is, a capital E), then the home key or Ctrl+A, it will put you at the start of whatever link it is trying to take you to, in an edit field. What do you see as the part of the link before the colon? Luke
Re: [Lynx-dev] a solution for this problem?
> In fact, the error, badly formed address, > Is one I have not encountered before. I have. It can mean a few things if I recall correctly. If, instead of enter, you press "E" on that link (that is, a capital E), then the home key or Ctrl+A, it will put you at the start of whatever link it is trying to take you to, in an edit field. What do you see as the part of the link before the colon? Luke
Re: [Lynx-dev] a solution for this problem?
Karen Lewellen dixit: > In fact, the error, badly formed address, Could be a data: URL, but, of course, without you sharing the link in question, we cannot know. bye, //mirabilos -- > Hi, does anyone sell openbsd stickers by themselves and not packaged > with other products? No, the only way I've seen them sold is for $40 with a free OpenBSD CD. -- Haroon Khalid and Steve Shockley in gmane.os.openbsd.misc
Re: [Lynx-dev] a solution for this problem?
There's the = sign command in lynx that shows information about a page and the URL closest to the bottom of that output may be the needed link. Jude "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) . On Sat, 14 Jan 2023, Bela Lubkin wrote: > Karen Lewellen wrote: > > > However, when I hit enter on this link, I get a badly formed address > > error...which I admit is new. > > Can you find out what that badly formed address link is? I'm not sure > which of these might work: > > - `lynx -source the_problem_page > problem-page.html`, then examine that > - use backslash 'view source' while in Lynx on the problem page > - '=' command inside Lynx, on the problem page, while on the problem link > - running the whole thing under `lynx -trace` and digging it out of the > wreckage > > It could be as simple as them using some sort of wrong HTML or URL > encoding which other browsers 'know' and silently fix -- or as > unreachable as the URL has to be decoded from some sort of crypto by > a JavaScript routine... > > >Bela< > >
Re: [Lynx-dev] a solution for this problem?
Karen Lewellen wrote: > However, when I hit enter on this link, I get a badly formed address > error...which I admit is new. Can you find out what that badly formed address link is? I'm not sure which of these might work: - `lynx -source the_problem_page > problem-page.html`, then examine that - use backslash 'view source' while in Lynx on the problem page - '=' command inside Lynx, on the problem page, while on the problem link - running the whole thing under `lynx -trace` and digging it out of the wreckage It could be as simple as them using some sort of wrong HTML or URL encoding which other browsers 'know' and silently fix -- or as unreachable as the URL has to be decoded from some sort of crypto by a JavaScript routine... >Bela<
Re: [Lynx-dev] a solution for this problem?
Hi chime, Actually, that is not the error here. In fact, the error, badly formed address, Is one I have not encountered before. Kare On Sat, 14 Jan 2023, Chime Hart wrote: Hi Mouse: Another aspect of Karen's comments was about that cryptic "no form action defined" or something about bad html. Chime
Re: [Lynx-dev] a solution for this problem?
I have been on the Google accessibility list for years, and remember when JavaScript change was announced. The google staffer actually said that only hackers do not use JavaScript. In a blog etc. The only place where I have access to my gmail account in basic html is on shellworld. google thinks it is my home computer, and believe me, its a creative hard won battle, for which I gladly pay for shellworld services alone..but I have other reasons to stay of course. If you have the cookies from when gmail let you log in with lynx, it might be possible, otherwise I am unsure...sorry! Kare On Sat, 14 Jan 2023, Mouse wrote: Verizon is using my Gail account, which still works in basic HTML for me. You later mention "Gmail", leading me to assume the "Gail" above is supposed to be "Gmail". If so...what do you have to do to make that work? One of my workplaces uses Google for their mail and, they said that "starting March 24, 2022" we "won't be able to sign into [our] accounts on browsers that don't support JavaScript". The actual date was somewhat after that; I haven't been able to find any record of exactly when, but it happened. And I just now tried again and got | Couldn't sign you in | |The browser you're using doesn't support JavaScript, or has JavaScript |turned off. | |To keep your Google Account secure, try signing in on a browser that |has JavaScript turned on. Learn more Of course, it don't bother explaining how requiring the exposed attack surface of a JavaScript engine can possibly make anything more secure than...not. I would *love* to switch back to using lynx, but I haven't found any way to get anything more useful than the misleading refusal above. However, when I hit enter on this link, I get a badly formed address error...which I admit is new. It's been a while, but I do have a fuzzy memory that, years ago, I found lynx erroring on links that "worked fine everywhere else" but were not actually well-formed according to the spec. Unfortunately, that memory is too fuzzy for me to say much more. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML mo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
Re: [Lynx-dev] a solution for this problem?
Hi Mouse: Another aspect of Karen's comments was about that cryptic "no form action defined" or something about bad html. Chime
Re: [Lynx-dev] a solution for this problem?
> Verizon is using my Gail account, which still works in basic HTML for > me. You later mention "Gmail", leading me to assume the "Gail" above is supposed to be "Gmail". If so...what do you have to do to make that work? One of my workplaces uses Google for their mail and, they said that "starting March 24, 2022" we "won't be able to sign into [our] accounts on browsers that don't support JavaScript". The actual date was somewhat after that; I haven't been able to find any record of exactly when, but it happened. And I just now tried again and got | Couldn't sign you in | |The browser you're using doesn't support JavaScript, or has JavaScript |turned off. | |To keep your Google Account secure, try signing in on a browser that |has JavaScript turned on. Learn more Of course, it don't bother explaining how requiring the exposed attack surface of a JavaScript engine can possibly make anything more secure than...not. I would *love* to switch back to using lynx, but I haven't found any way to get anything more useful than the misleading refusal above. > However, when I hit enter on this link, I get a badly formed address > error...which I admit is new. It's been a while, but I do have a fuzzy memory that, years ago, I found lynx erroring on links that "worked fine everywhere else" but were not actually well-formed according to the spec. Unfortunately, that memory is too fuzzy for me to say much more. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTMLmo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
