Sometime this month, Reddit will go public at a valuation of $6.5bn. Select Redditors were offered the chance to buy stock at the initial listing price, which it hasn’t announced yet but is expected to be in the range of $31-34 per share. Regardless of the actual price,
Not sure if a serious question. So forgive me if your question was meant to be a statement.
The internet is a large set of computers connected via a set of protocols: IP and on top of that TCP, UDP or very occasionally SCTP (more common on mobile networks).
There’s 65000-ish ports (channels) available on the internet (IP network).
The web runs on port 80 and 443 via TCP (mostly).
The internet supports all sorts of other traffic/channels too: Time synchronisation, games, file transfer, e-mail, remote login, remote desktops etc. None of these run on the web, but is traffic that runs in parallel to the web, using either TCP or UDP protocols.
The distinction is getting blurrier as lots of traffic that used to be assigned (or simple chose) its own port number is now encapsulated in HTTP(s) traffic. But the distinction is definitely not gone.
Appreciate this, I thought they were both called “the internet”. I knew we called it the worldwide web when I was a kid, but I thought that was just a phrase that fell out of fashion.
Where does Lemmy fall on this spectrum? Obviously the website part is 100% web, but I’m accessing Lemmy through a mobile app, so I don’t see any website here.
Yes agreed. I suspect it will collapse to “non-time-critical traffic will run on HTTPS via REST” and “everything else will run on UDP, using their own ports”, except for maybe a couple of golden oldies like NTP, FTP, SMTP/POP/IMAP.
POP and IMAP are pretty much dead at this point. Email is basically dead at this point. Want to spin up a machine and have it email you system messages? Nope. Want to run a Python script that sends to gmail? lol. https://mailtrap.io/blog/gmail-smtp/
On all my microservers I have pretty much have 22, 80, and 443 open. I try to interact exclusively over web ports for as much as possible.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Not sure if a serious question. So forgive me if your question was meant to be a statement.
The internet is a large set of computers connected via a set of protocols: IP and on top of that TCP, UDP or very occasionally SCTP (more common on mobile networks).
There’s 65000-ish ports (channels) available on the internet (IP network).
The web runs on port 80 and 443 via TCP (mostly).
The internet supports all sorts of other traffic/channels too: Time synchronisation, games, file transfer, e-mail, remote login, remote desktops etc. None of these run on the web, but is traffic that runs in parallel to the web, using either TCP or UDP protocols.
The distinction is getting blurrier as lots of traffic that used to be assigned (or simple chose) its own port number is now encapsulated in HTTP(s) traffic. But the distinction is definitely not gone.
Appreciate this, I thought they were both called “the internet”. I knew we called it the worldwide web when I was a kid, but I thought that was just a phrase that fell out of fashion.
Totally serious. Never knew there is a difference. Thanks for the explanation.
Where does Lemmy fall on this spectrum? Obviously the website part is 100% web, but I’m accessing Lemmy through a mobile app, so I don’t see any website here.
Well this is what I mean. In the olden days, this would be custom traffic on a custom port. Nowadays it just uses web HTTPS REST calls as API.
The advent of REST API endpoints really muddies everything up when all requests are going over the web.
Yes agreed. I suspect it will collapse to “non-time-critical traffic will run on HTTPS via REST” and “everything else will run on UDP, using their own ports”, except for maybe a couple of golden oldies like NTP, FTP, SMTP/POP/IMAP.
POP and IMAP are pretty much dead at this point. Email is basically dead at this point. Want to spin up a machine and have it email you system messages? Nope. Want to run a Python script that sends to gmail? lol. https://mailtrap.io/blog/gmail-smtp/
On all my microservers I have pretty much have 22, 80, and 443 open. I try to interact exclusively over web ports for as much as possible.
It’s hard, but not impossible, to get a personal mail server trusted amongst the big players, agreed.
That doesn’t mean email can’t be accessed with IMAP (or heaven forbid, POP3) on the big players. Outlook, gmail, FastMail, proton etc all support it.