Would you like clarification on this?
No, I don't need clarification on this. Some people call them "folders" because they are GUI users and the "folder" paradigm is very common in GUI file managers. Some people are CLI users and understand that they are "directories" because they are files that contain a list of other files. It doesn't matter how you like to refer to them, the URL for a document has no specific relationship to the folders or other means of storing the data on the server. Nothing on the network other than the web server itself can look at a URL and determine what folder that data is stored in -- so saying that a router or firewall sees that a request asks for something "in the /speedtest folder" is nonsense.
>> I would bet anything that this story is NOT in a folder "story/16/09/14/2242216/"
You sound fairly confident, good for you.
I didn't write what you are replying to. You're deliberately misquoting me. That's an unethical discussion tactic. I actually said that you don't know what directory it is in, and you don't. I made no bets.
Should I? Ok, if you say so my friend. But then again, I didn't make the claim that the terms URL and folder have a one to one relationship
And I didn't say what you quote me as saying. You have some nerve complaining about something YOU didn't say (which I never said you did anyway) after trying to put someone else's words in my mouth.
The story implies there is a one-to-one relationship, and YOU said that the "URL of the story" is in a specific directory -- something you have no evidence for, and on a website as dynamic and large as /. it is highly unlikely that they use a flat filesystem for a story database instead of a real database.
I understand that you don't care to know the difference. There are those of us who do this stuff for a living where it makes a great deal of difference. That you are incapable of accurately quoting someone you reply to BY NAME tells me that you don't care and are unlikely to be educated on the matter, so bye.