Re: Copyright violation? How?

Steffen Nurpmeso <[email protected]>
Newsgroups gmane.comp.web.lynx.devel
Message-ID <20191116203845.nl5e1%[email protected]>
Stefan Caunter wrote in <[email protected]>:
 |> On Nov 15, 2019, at 20:00, Ian Collier <[email protected]> wrote:
 |> On Fri, Nov 15, 2019 at 09:55:43PM +0000, Thorsten Glaser wrote:
 |>> Mouse dixit:
 |>>> #define UA_COPYRIGHT_WARNING \
 |>>> "WARNING: Misrepresentation of the User-Agent may be a copyright \
 |>>> violation!"
 |> 
 |>> Eh, I've never seen that one... not between 2.8.6 and 2.9 anyway.
 |>> If it existed it must be positively ancient.
 |> 
 |> Yes, you are right.  It appears to me that this text was present in 2.8.2
 |> but was eliminated in 2.8.3dev.13, released October 1999.
 ...
 |Indeed I have never seen that message, but in the 90s, servers did \
 |not screw with clients based on UA headers (much), so it was uncommon \
 |to set it. I remember reading the Washington Post and hotmail with \
 |no issues back then. 

From my memory i think you are totally mistaken.  At least
regarding anything Javascript alike, which was *anything* by then.
And it had to be done because of different ways of accessing the
document object model with Netscape and Microsoft.  Also Opera
used Subwindows in a main Window, which you better adhered to at
least a bit.  And if i recall correctly many sites blocked early
even if it was completely unnecessary, which is why that UA thing
popped up at first -- right?

Sorry you are the one who hears it, but very generally speaking
that current top-post hype makes me sad.

A nice Sunday i wish.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

_______________________________________________
Lynx-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lynx-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.