On Mon, 27 Jul 2026, Mike via Lynx-dev wrote: > And yes, I think that POST, if not other methods, could be used at > least in 2 forms, the removal and the modification-addition ones. I'm > not sure yet if it would be best.
There’s a famous story of an org using GET for data-modifying things. Turns out search engines trigger GETs as they crawl a site, which did include the delete forms, for that case, so they ended up with an empty database. If you have a <form/> you should use POST if it modifies *anything*. lynx operates… as expected, even if it can be a bit annoying (I run into this on AO3, when I post a comment, then go forward a chapter, then go back to the chapter where I had posted the comment, which issues a GET request because the cache period has expired, and lynx then has to reload the page with the form on it (which is a GET page) clearing the form data). bye, //mirabilos -- https://toot.mirbsd.org/@mirabilos/statuses/01KNQD9RNZM1Z2A61AZHG857MP long list of references on why “AI”/LLMs are bad for everyone
