Yep. The first one is using the photon front end, and the second is using mlmym

http and https are communication protocols, www is a way of enabling content sharing.

You use a web browser, such as Firefox or Librewolf. When you put in a URL (Uniform Resource Locator) such as https://en.wikipedia.org/ in the address bar (which shows the current URL), you tell the browser to retrieve that URL, through the HTTPS method.

Almost all websites use HTTP or HTTPS (which is more secure, as it's encrypted). The abbreviation stands for HyperText Transfer Protocol (Secure mode).

The way of 'retrieving' that URL is often done through that HTTP(S). Web browsers for that reason can be called a 'user agent'.

Search engines, such as Mojeek, are essentially websites that link to other websites, using a search query.

You can also sometimes use non-HTTPS methods, a few well-known examples are mailto and ftp (file transfer protocol) or database access like jdbc (Java database commectivity).

The internet works by encapsulating the data into layers.

After you send in the URL and method, the browser goes to look for the page. There are multiple layers to that. HTTP(S) belongs to the application layer, which tells "I make or have this data, I communicate with the same or another host". The www uses the HTTP(S)' rules to communicate.

Then there's the transport layer, that communicates "You're on this host, I'm on that host". TCP (Transmission Control Protocol) is one of those.

After that there's the internet layer, which says "This is the host address, that is the host address, both worded in the same ways" and "I send this data to that data". IP addresses are part of this one. Domains work through the DNS (Domain Name System) and you can think of them as more human-readable, more specific IP addresses.

Then there's the link layer which says "This is how things locally communicate on the same host without intervening routers." Wi-Fi and ethernet are examples.

There is another, that's not necessarily part of it, but nonetheless relevant here: the syntax (or presentation) layer. It "translates what this application layer reads to another application layer". An API is part of that.

So, then, what are front and back ends?

Think of the user interface; that is how you communicate with your computer. It's what the 'menus' look like, how logos look like, etc.

If your computer is a bicycle, what it looks like (the front end) is the user interface; and how the parts are connected, is the API. The back end is managing the previous layers I've mentioned.

I hope that that kind of explains it!