4 ms·

wait, can anyone please tell me the story behind this post? i understand it is about some primitive text browser for web but why (and how) is it on google group

by Achshar 15y ago

wait, can anyone please tell me the story behind this post? i understand it is about some primitive text browser for web but why (and how) is it on google groups? google wasn't even there at that time. and how can one add a post and date it in the past?

jaredsohn 15y ago
Back in 2001, Google bought the DejaNews archives which contained old Usenet posts and imported them into Google Groups (using the original dates).
Shark-Snap 15y ago
This was the start of the web. Berners-Lee wrote the first proposal for the World Wide Web system of hyper-linked pages of information. He then wrote the first tools to help browse this collection of pages. This newsgroup post is the original announcement for the tools he had developed. Google Groups include archives of old newsgroup postings and this story is linking to the original announcement in 1991. See Wikipedia page on History of the WWW for more info. http://en.wikipedia.org/wiki/History_of_the_World_Wide_Web http://en.wikipedia.org/wiki/History_of_the_World_Wide_Web
andyjohnson0 15y ago
Its a Usenet post from 1991. In 2001 Google bought [1] the usenet archive built by Deja.com, which included that post, and added the archive's contents to Google groups to enable searching Usenet using Google. [1] http://www.google.com/press/pressrel/pressrelease48.html http://www.google.com/press/pressrel/pressrelease48.html
icebraining 15y ago
primitive text browser for web Browser, server and editor. His original view was that everyone would publish from their own machines in a P2P way.
- dexen 15y ago
  That `editor' part cannot be stressed enough. It's a shame the PUT and PATCH HTTP methods aren't widely used nor open for use.
  - ominous_prime 15y ago
    I haven't seen a PATCH used in any real fashion, but PUT is now a fairly standard part of most HTTP APIs.
    - losvedir 15y ago
      > but PUT is now a fairly standard part of most HTTP APIs. Is it? I know Rails uses "put" for editing a model, but it was my understanding that it simulates this via a hidden field in the form and actually issuing a POST request. Why does it behave that way? I thought it was because many browsers don't support PUT, but maybe it's for other reasons?
      - ominous_prime 15y ago
        I'm referring to an HTTP API (RESTful if you will). HTML forms only support GET and POST, but browsers support GET, POST, PUT, and DELETE via XMLHttpRequest. Also, access to a lot of services' APIs don't come from browsers at all.
        losvedir 15y ago
        Thanks for the clarification. I didn't realize it was only HTML forms limited to GET and POST and not the browser as a whole.
      - RyanMcGreal 15y ago
        PUT is not supported in the browser [1], but web APIs are mainly intended for non-browser clients to access. A client app that consumes a well-designed HTTP web API will use POST to create a resource, PUT to update a resource, and so on. [1] With the caveat that the Javascript XMLHttpRequest API does support PUT and DELETE.
httpsuckslikepg 15y ago
Hi, if you don't know about which you are talking it it best to phrase your question AS a question.

by Achshar 15y ago

jaredsohn 15y ago

Back in 2001, Google bought the DejaNews archives which contained old Usenet posts and imported them into Google Groups (using the original dates).

Shark-Snap 15y ago

This was the start of the web. Berners-Lee wrote the first proposal for the World Wide Web system of hyper-linked pages of information. He then wrote the first tools to help browse this collection of pages. This newsgroup post is the original announcement for the tools he had developed. Google Groups include archives of old newsgroup postings and this story is linking to the original announcement in 1991. See Wikipedia page on History of the WWW for more info. http://en.wikipedia.org/wiki/History_of_the_World_Wide_Web http://en.wikipedia.org/wiki/History_of_the_World_Wide_Web

andyjohnson0 15y ago

Its a Usenet post from 1991. In 2001 Google bought [1] the usenet archive built by Deja.com, which included that post, and added the archive's contents to Google groups to enable searching Usenet using Google. [1] http://www.google.com/press/pressrel/pressrelease48.html http://www.google.com/press/pressrel/pressrelease48.html

icebraining 15y ago

primitive text browser for web Browser, server and editor. His original view was that everyone would publish from their own machines in a P2P way.

dexen 15y ago
That `editor' part cannot be stressed enough. It's a shame the PUT and PATCH HTTP methods aren't widely used nor open for use.
- ominous_prime 15y ago
  I haven't seen a PATCH used in any real fashion, but PUT is now a fairly standard part of most HTTP APIs.
  - losvedir 15y ago
    > but PUT is now a fairly standard part of most HTTP APIs. Is it? I know Rails uses "put" for editing a model, but it was my understanding that it simulates this via a hidden field in the form and actually issuing a POST request. Why does it behave that way? I thought it was because many browsers don't support PUT, but maybe it's for other reasons?
    - ominous_prime 15y ago
      I'm referring to an HTTP API (RESTful if you will). HTML forms only support GET and POST, but browsers support GET, POST, PUT, and DELETE via XMLHttpRequest. Also, access to a lot of services' APIs don't come from browsers at all.
      - losvedir 15y ago
        Thanks for the clarification. I didn't realize it was only HTML forms limited to GET and POST and not the browser as a whole.
    - RyanMcGreal 15y ago
      PUT is not supported in the browser [1], but web APIs are mainly intended for non-browser clients to access. A client app that consumes a well-designed HTTP web API will use POST to create a resource, PUT to update a resource, and so on. [1] With the caveat that the Javascript XMLHttpRequest API does support PUT and DELETE.

httpsuckslikepg 15y ago

Hi, if you don't know about which you are talking it it best to phrase your question AS a question.