> If there's a security hole related to gopher or bibp, let's fix it, > let's not up and drop support for those protocols because of it. People > do use these protocols even in 2014.
"let's" is a contraction for "let us". Basically the community must audit lynx, if they want it to remain in base. Those of us who have glanced judged it to be of poor quality. > If it's code bloat, I'd like to know just how much code we're talking > about. This is open source. You know you can find the source yourself and read it? Or .. perhaps you can't, and just wish to preach to us?
