FTP in the browser typically looks something like this https://imgur.com/20ooI9f
Plenty of space for ads.
HTTP is basically FTP with ads.
Funny thought. Imagine if, to this day, the internet consisted of pretty much that.
You go to ftp://nytimes.com and it just has a directory structure that consists of yyyy/mm/dd and the file names where things like statement-from-chinese-ambassador-to-australia.txt
And maybe a directory named breaking-news
Imagine if Twitter was a list of text files named yyyy-mm-dd-hh-mm-ss-username.txt
Ha.
Imagine if you had to upload a text file like this
---
Please place an x between the brackets as desired
[ ] Whopper Meal
[ ] Super sized Whopper Meal
[ ] Coke
[ ] Sprite
[ ] Eat-in
[ ] Takeaway
etc
Name on card:
Card number:
Expiry:
Card Security Code:
Sponsored by Nike and the Ford Motor Company
----
That's pretty much Gopher. Another protocol that Chrome no longer supports.
On Usenet newsgroups and BBS conferences, sellers would post forms that looked exactly like that, except for the ads of course. Buyers would then send in their completed order form via either email/netmail or, preferably, via fax for added security.
I remember always choosing to fax in my orders; even way back then, sharing credit card details via email seemed like a very bad idea.
I would love this. This has better UX than the food ordering sites we have to deal with in the real world.
Nobody would actually bother to download it would they!
Sounds like a total improvement over websites I have suffered... not to mention allows all kinds of third parties to create their own fancier ordering systems on top!