It is unfortunate that modern web development has led to websites so complex that they either break entirely or look terrible in text-based browsers like Lynx. Take Mastodon, for example: $ lynx https://mastodon.social/ […] To use the Mastodon web application, please enable JavaScript. Alternatively, try one of the native apps for Mastodon for your platform. The C2 Wiki does not load either: $ lynx https://wiki.c2.co…
Unlike computer interfaces, the web was never text-first. It was graphical from the start. The first browser was in a GUI, not a terminal.
Sites have been hobbled/broken on Lynx since the very beginning. It's neat and can be convenient to have a browser that works in your terminal for simple stuff, but the web was never designed for that. It's natural and to be expected that many sites will break. The burden is really on Lynx to do what it can to support sites as they are, rather than sites to try to build compatibility with Lynx.
It's kind of like, there are programs to "view" a PDF in the terminal, or at least its text content. But PDF authors shouldn't be expected to optimize the order text is presented for those programs. That's not what PDF was ever meant for, even if you can get it work sometimes.