The latest version of links does support SNI.

I use several clients that do not support SNI and one workaround is to connect through a program that does support it, e.g. haproxy, socat, etc.

Privacy/censorship conscious users may dislike SNI, SSL/TLS implementors are now trying to "fix" it, and in fact most SSL/TLS-enabled websites do not require SNI to be sent (popular browsers send it anyway). If requested, I can post stats on whether SNI is required for any list of websites. I have already done this a couple of times with the list all sites currently posted on HN: only a minority require SNI.

According the changelog, SNI support was added in links 2.10:

   === RELEASE 2.10 ===
   
   […]
   
   Sat Jan 17 06:44:01 CET 2015 mikulas:
   
   	Enable SSL SNI, some servers need it
   
   […]

"Sorry, the latter piece of the patch does indeed appear to call the NSS SSL_SetURL which should trigger the SNI."

So, according to your own link, yes it should support SNI.

AFAIK it's not integrated yet. But anyway, I'm still wrong as lynx does support SNI: https://lynx.invisible-island.net/lynx2.8.8/features.html#im...