Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

“Users will only be able to view patents via HTTP. HTTPS will no longer work”

uspto.gov

Post reply on HN
Print view View original

101–110 of 172 posts

Re: “Users will only be able to view patents via HTTP. HTTPS will no longer work”

#101

Post by pbhjpbhj »

mwfunk wrote: post #69
Eridrus wrote: post #65

Does anyone here actually read patent filings? I've been involved in writing a few and the result was useless drivel. Combined with the fact that there are penalties for willful infringement, I'm not sure what the benefit to reading patents in your field would be.

The patent system has evolved in a way that has practically inverted its original intents. You're exactly right, practitioners in a given field (ex: engineers in the tech industry) often avoid looking at patents, because no good can come of it. Most are too vague to be useful for licensing, but it opens one up to willful infringement claims later on.

Isn't failure to perform a search with due diligence an equal liability in US patent cases?

Re: “Users will only be able to view patents via HTTP. HTTPS will no longer work”

#102

Post by paulddraper »

anigbrowl wrote: post #97
paulddraper wrote: post #77

Earlier quoted context omitted.

The gap between those two technologies is larger than you suggest. Horse carraiges: 1400 Automobiles: 1890

Pretty sure horse carriages were around a lot earlier than 1400, unless you were thinking BC.

Even better. I was giving the benefit of the doubt.

That's around the time carraiges got suspension and were pretty much like the modern form.

Re: “Users will only be able to view patents via HTTP. HTTPS will no longer work”

#103

Post by MichaelBurge »

makecheck wrote: post #23

This would be interesting for patent research; you could legitimately say "I looked for a patent that already covers X but since you cannot guarantee the data was not modified in transit, I cannot be certain that I saw what was actually in the patents I reviewed".

Don't you only need to be 51% confident? As long as fewer than 50% of all HTTP requests are modified by malicious adversaries in transit, you'd still have to pay up.

Re: “Users will only be able to view patents via HTTP. HTTPS will no longer work”

#104

Post by paulddraper »

yjftsjthsd-h wrote: post #94
paulddraper wrote: post #77

Earlier quoted context omitted.

The gap between those two technologies is larger than you suggest. Horse carraiges: 1400 Automobiles: 1890

Horses and cars were in use at the same time, just like HTTP and HTTPS; I'm not sure why their invention times are relevant?

Gunpowder and ICBMs were also in use at the same time

I'm claiming the technological backstepping is not nearly as drastic as the GP implies.

Re: “Users will only be able to view patents via HTTP. HTTPS will no longer work”

#106

Post by anticedent »

jsolson wrote: post #89
pavement wrote: post #85

Earlier quoted context omitted.

This practice has nothing to do with Java, at all. It is not an approach that was invented by Java, for Java, and it is not in any way unique to Java. Most web technologies support rendering a view based on a set of values residing in a database, and use the values to populate a template. The template contains placeholders reserved for values expected to originate from a database. The version of the page that appears…

What's being described above isn't simply template-based rendering (which, yes, essentially everything does), but the practice of building web-software like desktop software and keeping the state of the UI server-side. It ignores that browsers are capable of effectively forking the UI through (today) tabs and (historically) "Open in New Window". Interacting with such software is a profoundly unpleasant experience; th…

Which is great, because everybody should downvote anything because of a mild distinction, rather than the wildly off the mark question that prompted a reasonable response. Good job!

Re: “Users will only be able to view patents via HTTP. HTTPS will no longer work”

#107

Post by maxxxxx »

Eridrus wrote: post #65

Does anyone here actually read patent filings? I've been involved in writing a few and the result was useless drivel. Combined with the fact that there are penalties for willful infringement, I'm not sure what the benefit to reading patents in your field would be.

Patent lawyers read them and check if your work doesn't infringe. In my company that's standard procedure.

Re: “Users will only be able to view patents via HTTP. HTTPS will no longer work”

#108

Post by rhino369 »

lend000 wrote: post #51
vesinisa wrote: post #22

The USPTO databases have to be one of the most torturous services to their users in the whole of internet. The UI of both the patent and trademark search is archaic, but not in a HN way but in a really bad way. In patent search, there is no "search" box. Instead, the "quick search" forces you to specify two (and exactly two) text queries on the database columns with obligatory boolean operation.[1] Even if you happen…

Thank goodness for Google patents and patents.justia.com (which is HTTP, by the way). Regardless, much more usable than the Patent Office website.

Google Patent is a lifesaver for me. But I've noticed increasing number of errors.

Re: “Users will only be able to view patents via HTTP. HTTPS will no longer work”

#109

Post by DaiPlusPlus »

jsolson wrote: post #89
pavement wrote: post #85

Earlier quoted context omitted.

This practice has nothing to do with Java, at all. It is not an approach that was invented by Java, for Java, and it is not in any way unique to Java. Most web technologies support rendering a view based on a set of values residing in a database, and use the values to populate a template. The template contains placeholders reserved for values expected to originate from a database. The version of the page that appears…

What's being described above isn't simply template-based rendering (which, yes, essentially everything does), but the practice of building web-software like desktop software and keeping the state of the UI server-side. It ignores that browsers are capable of effectively forking the UI through (today) tabs and (historically) "Open in New Window". Interacting with such software is a profoundly unpleasant experience; th…

> It is not Java-specific, but it is common to a few specific Java frameworks as well as at least one of Microsoft's older frameworks (I forget which one).

ASP.NET WebForms has a feature where the Session ID, normally stored in a cookie, is stored in the request URL path instead. This was done back in 1999-2001 to support extremely rudimentary HTTP clients which did not support HTTP Cookies - imagine really prototypical mobile-phone web-browsers or hastily-written shell scripts using CURL.

Fortunately it was disabled by default and the documentation describes why it's a bad idea to use it - and I understand the business reasons for including it - however this design does not break things like multiple-tab browsing: that's just what happens when you have any stateful web-application, regardless of framework.

It's now gone in ASP.NET MVC (where you gave full control over rendered URLs), so that horrid chapter has ended.

Re: “Users will only be able to view patents via HTTP. HTTPS will no longer work”

#110

Post by tgjsrkghruksd »

gondo wrote: post #87
vesinisa wrote: post #22

The USPTO databases have to be one of the most torturous services to their users in the whole of internet. The UI of both the patent and trademark search is archaic, but not in a HN way but in a really bad way. In patent search, there is no "search" box. Instead, the "quick search" forces you to specify two (and exactly two) text queries on the database columns with obligatory boolean operation.[1] Even if you happen…

they actually recommend google on their search page! [1] "You can also try this same search on Google." [1] https://www.uspto.gov/blog/ebiz/search?q=

That's for searching the USPTO website. Not searching patents, or Google's patent search.
Post reply on HN