News for hackers. Stuff that matters.
Re:Bypass Paywalls repository is gone by Karellen on Friday April 12, 2024 @05:42PM (#40017995)
Does the thing being bypassed prevent you from saving the page, or from making in any other way a copy of any content you've already fetched?

If not, how could it be classed as copy-protection?

Edit: One other thing: if spoofing UA headers was a problem, all the browsers in the world would fall foul of it - because non-Mozilla browsers all say that they're Mozilla, and Opera said it was IE, and Chrome said it was Safari, and now a bunch of browsers say they're Chrome - at the same time as saying they're Mozilla. Except it's more complicated than that.

Re:Bypass Paywalls repository is gone by idle_zealot on Friday April 12, 2024 @05:52PM (#40018068)
I guess it's less copy-protection and more access-control.
Re:Bypass Paywalls repository is gone by Hello71 on Friday April 12, 2024 @08:48PM (#40019279)
this is basically the "computer scientist" view of the world in https://ansuz.sooke.bc.ca/entry/23, especially the Monolith bit. spoofing UA could be legal in general or when done for interoperability but illegal when done with intent to bypass access control.
Re:Bypass Paywalls repository is gone by beeboobaa3 on Saturday April 13, 2024 @12:16AM (#40020448)
Right, the UA spoofing browsers perform is historically done to bypass sites not wanting to serve them content.
Re:Bypass Paywalls repository is gone by LoganDark on Saturday April 13, 2024 @02:07AM (#40020893)
Well the UA spoofing I perform is done to bypass sites not wanting to serve me content.
Re:Bypass Paywalls repository is gone by clemiclemen on Monday April 15, 2024 @09:56AM (#40040604)
Those looking into the history or the user agent, and why it happens to advertise itself as Firefox, Safari and Chrome ate the same time, can look into this article: https://webaim.org/blog/user-agent-string-history/comment-pa...