Community Discussions
Explore the latest discussions and community conversations related to this domain.
How does websites works?
Main Post: How does websites works?
Top Comment: Here are all the steps: 1) You register the domain name with a domain name registrar. The registrar registers the domain ownership with whoever manages the TLD (top level domain). So .com is managed by another firm than .co, for example. The registrar has a relationship with the management firm for the TLD and will make sure that the TLD knows who the domain is owned by and, more importantly, what the name server (DNS server) for that domain are. For example, ns1.domain.com [ http://ns1.domain.com ]and ns2.domain.com [ http://ns2.domain.com ]. Learn more about TLDs here: Top-level domain [ https://en.wikipedia.org/wiki/Top-level_domain ] 2) The DNS servers will associate IPs with various aspects of the domain name. Those would be things like domain.tld, www.domain.tld, ftp.domain.tld, mail records for the domain etc. If you use a registrar like GoDaddy that also does hosting, they'll already configure the DNS servers for you. Otherwise, you need to do that yourself (or hire a systems admin). 3) On the server that will 'host' the Website, you will want to install a Webserver software and make it listen to certain ports. Then upload the files and/or code and configure everything to be perfect (the details of that will depend on the Web server used (apache, nginx etc.), the language (straight HTML, PHP, Python, Ruby etc.) and maybe additional libraries and frameworks used. So what happens when you type the URL into your Web browser? 1) Your browser will check its own DNS cache, the computer's cache and the computer's hosts (or similar) file to see if it knows what IP corresponds to the domain name you just entered. If it doesn't find a match, it will query the DNS server provided by your ISP (either statically or dynamically), if those DNS servers don't know the IP, it will go up the DNS server chain all the way to the TLDs name servers, which will know that the name servers for the domain are ns1.domain.tld and ns2.domain.tld. So the name servers will query those to get the information about the address entered. The information is then cached in the chain of name servers for performance reasons (so not every entry for Facebook.com goes through this chain), but only for some time (know as the TTL of the DNS entry). After the TTL, the lookup is refreshed (in case the site was moved to a new server etc.). At the end of the lookup, your browser will know that www.domain.tld corresponds to some IP, such as 12.34.56.78. 2) The browser than makes an HTTP request to the IP, either on port 80 for http:// or port 443 for https:// or you can request another port by adding :port to your URL such as www.domain.tld:99 (but unless the server is setup for this, it will usually just hit a firewall or be ignored). I am also ignoring SPDY and HTTP2 here. 3) Using the TCP/IP protocol, machines will relay the browser's request to that IP via a chain of machines in between your computer and the server. The Internet forms a giant network for computers, switches and routers, connected by various nodes (hence the term interNET). Hopefully eventually the request reaches the server. 4) The server will have daemon (running background process) running that hopefully answers on the port that you requested. If it's setup correctly, the request reach the Web server software such as apache (but there are others, I will use apache as an example as other generally are similar). Apache will receive the request and process it via various rules that are setup, generally referred to as vhost rules. Those rules will tell it that if there is a request coming in for www.domain.tld, it will route that request to a certain folder. At this point, a variety of things can occur. a) If the requests points to a static resource, Apache will just serve that file back to the Web browser via an HTTP response (200 response code) or, if it doesn't exist or there is another error, return an error response (such as 404 for page not found). b) If the requests points to a URL mapped to a code file such as an HTML with PHP file when PHP is installed and configured, Apache will trigger the PHP interpreter and first evaluate the PHP code in the file and replace it with the output of the code. Then it will serve the result back to the Web browser c) More complex configurations exist, where Apaches uses a WSGI app or similar to send the request to another program, such as Python for a Django/Flask app. Python processes the site code based on it's own set of rules and then returns the result back to Apache via WSGI and Apache then sends the result back to the browser. d) Once the browser gets the HTML response back, it will see what other resources it contains (such as images, CSS files, JS files, videos etc.) and will request those separately from the server. There are limitations in the HTTP protocal, so it can only request a certain number of resources at once from the same domain name, so for performance, often developers put resources under different subdomains to get around this protocol limitation and speed things up. 5) More complex setups could exist, where there is a CDN or proxy server in front of apache, but for the sake of keeping this simple and basic, I will ignore those scenarios. Also, generally the language used (PHP, Python etc.) will also talk to a database server in composing the response to the request. It may also involve a caching resource such such a memcache, a text based search appliance such as elasticsearch etc. 6) Usually, the server will return the response along with some headers, telling it things such as how long to cache the resource for in the browser. So images, once downloaded, may stay in the browser cache until they either expire or the browser cache runs out of space and the resource is purged. You can also cause a force reload (how depends on the exact browser - but hitting F5 or command/control-R repeatedly will usually trigger that as will clearing the browser cache). The browser can also send a HEAD request rather than a normal POST or GET request to the browser to see if the resource was recently updated and needs to be refreshed. This is the simple, short answer and I am glancing over a lot of details and simplifying the process for this basic introduction, but you get the idea.
Website won’t load properly on my phone but works fine on others? : iphonehelp
Main Post: Website won’t load properly on my phone but works fine on others? : iphonehelp
Website https://ipfs.io no longer works. Why? : ipfs
Main Post: Website https://ipfs.io no longer works. Why? : ipfs
I need a website that only works with internet explorer : sysadmin
Main Post: I need a website that only works with internet explorer : sysadmin
A new getmonero.org website is in the works!
Main Post:
Consensus has been reached at today's website meeting, and a new website is on the way! It will be designed by Diego Salazar (the same designer as the current website) and will be implemented using the Astro JavaScript framework.
You heard that right. The new website will not use Jekyll, but Astro, a wonderful framework written in JavaScript, primarily meant to be used as a static site generator. Obviously, that means it will not ship any JavaScript and will be compatible with our fellow Tor users at the safest level.
A rough prototype of the current getmonero.org website ported to Astro can be found here:
(demo): http xi2nhkuzm2hzgyedprs3n65wmudrq4rekbzire67oomiwk5x5h6w7nqd dot cryingvegetable
(repository): https://github.com/SyntheticBird45/monero-site-astro
You can check out the current state of the (work in progress) redesign at: https://www.figma.com/design/OuY892nD4zD1CEQDvC2Kty/Monero-Website-Redesign-2024-(Copy)?node-id=0-1&t=KoAMdY5uGn7fCNWJ-1 (Warning: WebGL is required, use Librefox or Chromium-based browser)
Top Comment: Cool to hear!
Retraction works in TeachingTech calibration website generated gcode but not in Cura generated gcode
Main Post:
I have been trying to calibrate my printer using the TeachingTech calibration website and it is able to generate gcode for a retraction tower with quite good results, however, when I attempt to print this same tower with cura, with settings kept the exact same, the result comes out quite stringy.
Top: TeachingTech website gcode, Bottom: Cura gcodeHelp would be appreciated and do let me know if any other information is needed to diagnose the issue.
Top Comment:
Look at the rest of the teaching tech site. Print and travel speeds, cooling options, print temps, coasting, wiping, zhop etc. This might be different.
An app or streaming website that have terrifier 3? (Works in lebanon)
Main Post: An app or streaming website that have terrifier 3? (Works in lebanon)
Top Comment:
You can use stremio (which plays torrent files in a Netflix-like interface) on android/windows
However terrifier 3 is only available in HDCam version so not a really good quality