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.
Credits
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
view the rest of the comments
While everyone has covered the common cases with domains, I'll cover the less common with a basic overview of domains.
Domains are basically just mapping an IP address to a human-readable string. 127.0.0.1 might be hard to remember. But "localhost" is easy to remember. Domain Name Servers and ICANN have developed a ton of RFCs to support making the internet easy to use and safe. This has also made the whole notion of domains a bit complicated.
But - like I said - they are basically just mapping an IP address to a human-readable string.
IP addresses are unique for a given network. On your local network, you have a unique IP address (e.g. 192.168.1.50). This is unique to the local network. But if you Google for your "public IP address" you'll see that it's different than your local address. The public IP address you have is assigned by your internet service provider (ISP). It's basically the IP address of your home.
Every computer has things to optimize the domain name lookup for a given IP address. For example, your browser might cache something like google.com points to the IP address 192.168.1.50. Computers also usually have a "hosts" file. You can manually edit this file so that your computer will always try to resolve a particular IP address given a domain name. You can map Google.com to your localhost 127.0.0.1.
So the case of "who owns a domain" is actually dependent on how your computer and network is setup. You can own Google.com on your own personal computer. You just edit the /etc/hosts file (on Linux). If you own the router and have access, you can "trick" computers in thinking google.com maps to your computer's IP address. Thus in that case, you own the domain for the local network.
But your ISP owns their network. The one you use to access the internet. And they have a vested interest in making sure it adheres to the ICANN DNS resolutions. You can change your DNS server to anything you want. Doing so is usually safe since it's often 8.8.8.8 or 1.1.1.1, but I suppose it's possible you could choose a DNS server that is malicious. Though thanks to SSL they can't do much.
Now you might be thinking: wait, if I'm on a local network, they can trick my computer into thinking a domain is valid when it's really being routed to malicious server? Technically yes. However that's why HTTPS exists. We use certs via a Certificate Authority to validate that the IP address you're accessing is mapped to the right domain. That's why it's important you always make sure SSL is on a website (usually represented by the little lock icon in the search bar)