No Stupid Questions
No such thing. Ask away!
!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must be legitimate questions. All post titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't intentionally annoy, mock, or harass other members.
If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here. This includes using AI responses and summaries.
Credits
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
view the rest of the comments
There's two things at play here.
First, www originated in a time when the web was not synonymous with the internet. Gopher, FTP etc were a much larger part of peoples daily internet usage, and servers would have different subdomain names to account for that. ftp.tld.edu, gopher.tld.edu and www.tld.edu were all domains you might see for a single server for example. Then of course, the web grew, and the other protocols became less relevant, but the www stuck around. One of the reasons you're seeing less of it, is because that tradition is slowly fading away given its loss of daily relevance.
The other reason you're seeing less of it is that browsers often just hide it even when it's there. And that of course, will create more future instances of servers just dropping it completely.
Fuck winsock.dll. fuck that file.
I remember being little and my dad was shaving for work for his weekend job and dragging him to my PC to show him all the other protocol apps I had downloaded.
BBS guy. Never got him on mirc.
Nowdays ftp-things are like ftp:// and normal websites use https://, is this a newer thing?
No — that prefix tells the OS which application to direct the address to.
The www., ftp., mail., etc. are on the server side, so the client gets directed to the correct computer owned by the domain owner.
To some degree, this quickly became irrelevant when virtual hosting became a thing; you could have something watching on the server side that would see an attempt to connect to port 80 or port 443, check the domain the client is looking for, and redirect them to the right internal or external IP address.
With the onset of CDNs, it became even less meaningful since load and availability balancers will now decide what computer will eventually receive the request.
All you really need is the URI (https://) and the port (:443) and everything else can be a black box.
Why don’t we see :80 and :443 on URLs anymore? Because a web browser, when it handles the URI request, auto-maps to the default ports for that URI unless it is explicitly told to use another.
As a result, you can enter example.com into a browser address bar, and you’ll automatically be taken to [https://guest@www.example.com/ :443/] but all you’ll see on the browser bar is example.com.
[edit] hah; even Lemmy is munging my URLs to remove the bits it deems unnecessary.
Use backticks to tell us exactly without Lemmy attempting to correct you or parse anything
becomes
https://www.example.com/Okay. ftp://, http://, https:// are associate with protocols that operate on a common port. You can execute “cat /etc/protocol” (on macOS or Linux terminal) and see each associate common port and their protocol name.
The protocol is associated with a port that is open on a host, which is associated with a process in the OS and that process listens and “talks” those ways when a host connects with a client, like a web browser.
Those are schemes and they are not new, there are many others as well. Some you may see in a browser are http, mailto, file. Others that you won't typically see in browsers include ldap(s), imap, jdbc, odbc, etc. https://en.wikipedia.org/wiki/List_of_URI_schemes
Newer, yes. Not very new.
The URL format of protocol://hostname.domain:port/path was defined in 1994. Prior to that you would use use an ftp client, usually on the command line like:
ftp hostname.domain