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

141–150 of 172 posts

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

#141

Post by fiatjaf »

jsolson wrote: post #129
jethrow wrote: post #117

Earlier quoted context omitted.

What's being described above isn't simply template-based rendering How are you able to draw that conclusion? The GP didn't supply a link as an example. It is simply a non-specific anecdotal remark, with no further evidence provided.

Well, the post I responded to included a more or less textbook description of template based rendering. It's a response to a response to this: > The bizarre practice of assigning session keys to visitors and somehow storing the page they're viewing in the server instead of in the URL is pretty common in Brazilian government, which is dominated by Java programmers. Having dealt with such a service just today (King Cou…

You got what I meant correctly. Thank you for understanding me.

I don't know how could anyone think I was talking about general template rendering (but maybe I expressed myself badly, English is not my first language).

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

#142

Post by trunchbull »

rsynnott wrote: post #139
timv wrote: post #124

Earlier quoted context omitted.

Historically it was fairly common. I wouldn't say it was standard, but it happened often enough to notice. There's a bunch of reasons that come together to cause that. During the explosion of the web, enterprises moved much of their development into web solutions using an existing workforce that had skills in different technologies - often client-server desktop-to-RDBMS tech. Java was a popular choice for these new p…

Also, the third likely reason is that there are still a lot of Java web codebases from the mid to late 90s around; the Java runtime can still run the code, so people keep it. Perl and TCL are less likely to be convenient to run today, and more of those codebases will have been dumped. And Java was disproportionately used for very large complex systems which would be expensive to replace, in any case.

It's a similar story with Windows, due to continuous backwards compatibility as demonstrated in videos such as:

https://www.youtube.com/watch?v=PH1BKPSGcxQ

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

#143

Post by nullc »

nullc wrote: post #133
Twirrim wrote: post #88

Earlier quoted context omitted.

FWIW, you're often better off not searching, or looking at, patents. If you end up in a patent case, your liabilities will be much higher if they can sufficiently claim you knowingly infringed. Evidence that you searched for patents can weigh against you / your employer. Even if you weren't associated with the infringing product itself.

This is largely outmoded advice in the wake of in re seagate. Simply having looked at a patent is not enough to create willful infringement.

I've just been informed that in re seagate got over turned last year. Bad news.

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

#144

Post by tormeh »

curiouscats wrote: post #136
k_sh wrote: post #125

Earlier quoted context omitted.

sounds like the US government is ripe for disruption... /s

It is one of the rare organizations where the people responsible for the budget of the organization have long track records of trying to have them disrupted (or just eliminated). Congress has often tried to undermine the ability of the EPA, IRS, NIH, NOAA... to do their job which then makes it seem they are ripe for disruption.

The Republicans are essentially government saboteurs, which is fascinating if you can look at it from a distance. Most countries' major conservative party don't do this. Quite frankly, I'd say that having a relatively small government is what saves the US from disaster, as countries with that level of government dysfunction are usually pretty poor.

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

#145

Post by 3131s »

Prime example of a government function that could benefit from the open source community. If all this patent data were dumped today, in whatever format it's stored in, I guarantee we'd be seeing a bunch of cool ShowHNs within days and all of us would be better off for it.

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

#146

Post by tyingq »

3131s wrote: post #145

Prime example of a government function that could benefit from the open source community. If all this patent data were dumped today, in whatever format it's stored in, I guarantee we'd be seeing a bunch of cool ShowHNs within days and all of us would be better off for it.

Not sure if it's everything, but the USPTO provides this http://patents.reedtech.com

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

#147

Post by knodi123 »

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…

> to release system resources allocated for you

Jesus christ.

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

#148

Post by fullDuplexxx »

fmoo wrote: post #137
diebir wrote: post #135

Earlier quoted context omitted.

Uhm... A server side session Web apps is pretty basic stuff: https://en.wikipedia.org/wiki/Session_(computer_science)#Ser... This existed since the Perl CGI times. "Bizarre practice", wow.

Server side sessions aren't the bizarre practice - Keeping track of navigation state on the server side is. This is like your whole website existing as a single endpoint and making POSTs to the same URL to get to different parts of the site.

...which is pretty much how hashtag-based single page webapps operate.

Many, if not most, isomorphic react/node.js apps have a single API url, with microservices behind the load-balanced URI, that accepts HTTP POST requests, and looks at a JSON object sent as the request body, in turn responding with a JSON object that informs the client-side app to re-render accordingly.

This isn't bizarre at all. It is very, very common; if not the norm.

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

#149

Post by kakarot »

As far as I know, this is illegal because of this:

https://obamawhitehouse.archives.gov/blog/2015/06/08/https-e...

Does anyone have any experience with their support system? On Monday I will be calling them in an attempt to understand why they are exempt from the HTTPS Everywhere federal directive.

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

#150

Post by 3131s »

tyingq wrote: post #146
3131s wrote: post #145

Prime example of a government function that could benefit from the open source community. If all this patent data were dumped today, in whatever format it's stored in, I guarantee we'd be seeing a bunch of cool ShowHNs within days and all of us would be better off for it.

Not sure if it's everything, but the USPTO provides this http://patents.reedtech.com

Does seem like I spoke too soon, though the above link is not everything. I downloaded it and it's a CSV file with three fields -- a patent ID (I think), a date, and some other number.

This however seems to be everything:

https://pairbulkdata.uspto.gov/

Looks like people tend to be satisfied with Google Patent as well.

Post reply on HN