-3

Before the first image was uploaded on the World Wide Web in 1992, it was possible for people to upload images on the internet before the World Wide Web, users uploaded images on online service providers such as CompuServe, GEnie and among others, How were images uploaded in online service providers before the World Wide Web?

  • 16
    What you call "uploading an image" is no more than transferring a file. There are, and have been, any number of file transfer protocols in use. It's easy enough to define a suitable protocol once you have "send some bytes" available to you. FTP ('file transfer protocol') might be the most common immediately preceding the WWW, if the transport layer is using TCP. – dave Oct 22 '23 at 18:20
  • 9
    Kermit was a popular file transfer protocol/program back in the dark ages. – HABO Oct 22 '23 at 19:07
  • 3
    If the files were uploaded to Usenet, they would also be uuencoded. And possibly split into multiple pieces. – fadden Oct 22 '23 at 21:08
  • 4
    Photographs have been transferred commercially "by wire" since the 1920's, and FAX came before WWW. – Weather Vane Oct 22 '23 at 22:45
  • 8
    (Well, if no-one else is going to go for the obvious answer…)  How were images uploaded?  Slowly! – gidds Oct 22 '23 at 23:38
  • 1
    Originally, Compuserve etc weren't connected to the Internet but were entirely separate entities. Are you asking about pre-www Internet or other systems? In other words, upload where? Your question is unclear. – Chenmunka Oct 24 '23 at 15:53
  • I was asking about pre-www internet – Maya Anglieo Oct 25 '23 at 11:50
  • 1
    "I was asking about pre-www internet" conflicts with mentions of "CompuServe, GEnie and among others". – RonJohn Oct 29 '23 at 03:57
  • I'm unsure about the usage in classical MVS but current TK5 MVS (a runable packaging of MVS 3.8 from 1978) supports the IND$FILE tool, basically allow transfering a file via a 3270 terminal stream between the host and the user's PC (PC based 3270 terminal emulator program.) – Stefan Skoglund Oct 30 '23 at 15:53

2 Answers2

8

You may have heard the very true proverb that

There is no cloud, but someone elses computer!

right? The very same misunderstanding seems to be at work here:

There is no 'World Wide Web', only networks and communication protocols.

The Internet and its IP based protocol suite being one. HTTP for example handles request and delivery of web-pages, while FTP, handling file transfer, just to name two of them. Those protocols are used connect service providers, like mailboxes, forums and whatsoever by means of using a user client software, vulgo a browser.

Other networks, like the mentioned, have their own protocols, service providers and client programs to do the same. Some based it on more generic clients like terminal protocols (often VT100/ANSI) and standard file transfer protocols (X-Modem, Kermit, etc.), while others created and distributed their own client software - best go and ask some older person about 'AOL-CDs'.

Bottom line, as soon as there is a communication line to exchange data, data can and will be exchanged. No difference between text, sound or pictures, as they are just files of data - files to be transferred using some file transfer protocol (*1). Protocols dating back to the 1970s or even before.

That nowadays the camera app of one's phone offers a button to post a picture taken straight to some social network holds no principal difference to a 1985 Compuserve / Q-Link / AOL / mailbox / etc. user pressing some key combination to select a picture file to upload.

The only improvement is more a seamless UI integration.

... well, that and that one may now upload a 20 Megabyte picture the same ease as a 2 KiB one back then :))


*1 - Not to mention, that files can of course be transferred using sneakernet, aka good old physical media, like floppy disks or tapes. In the very early days (*2) of mailboxes it was quite common to 'upload' large amounts of data, like web comics, picture collections or (textual) data bases that way. After all, transferring a 100 KiB data blob at 300 Bd will take anywhere between one and two hours. While blocking the computer (not much background transfer back then) and the family telephone line for two hours might have still be acceptable to the uploader, the mailbox owner and other users might not be as appreciative as those systems often had only one line - or a few at best.

*2 - Not telling that Sneakernet is dead, it's still as useful for large data sets as 40 years ago - except 'large' no longer means in Kilo- or Mega-Bytes but Tera- and Peta-Bytes :))

Raffzahn
  • 222,541
  • 22
  • 631
  • 918
  • 3
    +1 for Sneakernet. Just last week, it was quicker for us to post a large USB of data to a remote site, rather than upload it. – Kingsley Oct 24 '23 at 21:36
  • FTP based on TELNET, the TELNET protocol in the FTP application allows the user application to create a local UDP port and tell the server about that one. The server will then simply throw packets over the wall to something which it doesn't know if it will receive (or what it is.) TELNET protocol is used for flow control. – Stefan Skoglund Oct 26 '23 at 19:56
  • @StefanSkoglund Err, you kinda lost me there. – Raffzahn Oct 26 '23 at 21:34
  • classical ftp uses UDP for the data stream - the signalling information moves in the TELNET TCP channel. – Stefan Skoglund Oct 28 '23 at 15:43
  • UDP is basically write an address on a stone and throw it over the wall - then it ends in a pond (and gets lost), hits a receiver (the wrong one) in the head or hits another receiver (the right one.) The signalling channel is used to tell the sender about a certain UDP end point (preferably it's own) – Stefan Skoglund Oct 28 '23 at 15:45
  • though my comment is maybe in the wrong part. – Stefan Skoglund Oct 28 '23 at 15:46
3

Before the WWW, you couldn't guarantee that:

  1. your communications link could send 8-bit bytes as a single character;
  2. the remote computer (and possibly even your local computer) represented data in bytes anyway.

So whatever protocol you used, there as a lot of conversion and escaping of characters to ensure the data made it through the wires. Compuserve, for example, used its own B Protocol to packetize data and make it safe for transmission through 7-bit data networks such as Tymnet.

In addition, simple graphics formats were developed that only used printable characters. One of these was Compuserve RLE, a disarmingly simple file format that could nonetheless encode a 256×192 monochrome bitmap in a text file that could be decoded using a short BASIC program. Because it used only simple run-length encoding, CIS RLE files didn't store stippled images efficiently.

scruss
  • 21,585
  • 1
  • 45
  • 113