this post was submitted on 01 Jan 2026
617 points (99.4% liked)

Microblog Memes

10199 readers
2469 users here now

A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.

Created as an evolution of White People Twitter and other tweet-capture subreddits.

RULES:

  1. Your post must be a screen capture of a microblog-type post that includes the UI of the site it came from, preferably also including the avatar and username of the original poster. Including relevant comments made to the original post is encouraged.
  2. Your post, included comments, or your title/comment should include some kind of commentary or remark on the subject of the screen capture. Your title must include at least one word relevant to your post.
  3. You are encouraged to provide a link back to the source of your screen capture in the body of your post.
  4. Current politics and news are allowed, but discouraged. There MUST be some kind of human commentary/reaction included (either by the original poster or you). Just news articles or headlines will be deleted.
  5. Doctored posts/images and AI are allowed, but discouraged. You MUST indicate this in your post (even if you didn't originally know). If a post is found to be fabricated or edited in any way and it is not properly labeled, it will be deleted.
  6. Be nice. Take political debates to the appropriate communities. Take personal disagreements to private messages.
  7. No advertising, brand promotion, or guerrilla marketing.

Related communities:

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Zagorath@aussie.zone 15 points 3 weeks ago (24 children)

Only very, very loosely related to this. But can someone explain why we learn the OSI model, despite the fact that as far as I'm aware it's completely theoretical and has never been used, but the TCP model is ubiquitous?

[–] ekky@sopuli.xyz 19 points 3 weeks ago* (last edited 3 weeks ago) (5 children)

I think I found the source of confusion.

The OSI model describes networking in general, defining a model in which almost all networks can be categorized and compared. This is important as hundreds (if not thousands) of standards and methods exist for handling each separate layer - some publicized, but many hidden/propriety/unpublicized.

Meanwhile, the TCP/IP model describes only a very narrow subset of networks, though it just so happens to be the most used kind of network - The Internet - is part of this.

This means that if you are working with the internet, then TCP/IP will likely cover all your needs, but as soon as you move onto more specialized or simply uncommon network types TCP/IP will be close to useless.

We could take an example:

I'm setting up a LoRa network between some neighbors, measuring stations, etc. The network will not be connected directly to the internet, so there will be no possibility of data transfer between the LoRa network and the internet until you reach the OSI Presentation layer.

The LoRa network will need to be much more efficient than the general-purpose internet-networking, and since only a few machines will be connected we'll use only a single octet as device identifier (alternative to MAC/IP, lets call it SoMAC), also having to write our own discovery service.

Likewise, we will make a new custom transport layer based on TCP, but with only space for that single octet identifier, no flags, no IP, and no checksums (I like to live dangerous). Let's call that SoSTRIP.

At last, we'll need to write some kind of socket to make sending the information easy, for simplicity we'll use a Unnamed Pipe.

Now, how would we go about representing this in both models (OSI vs. TCP/IP)?

In OSI we'd have:

  • Physical Layer: LoRa (duh)
  • Data Link Layer: LoRa driver with SoMAC discovery
  • Network Layer: SoMAC addressing
  • Transport Layer: SoSTRIP
  • Session Layer: Unnamed Pipe
  • Presentation Layer: ASCII can be whatever
  • Application Layer: Cat

In TCP/IP we'd have:

  • Link Layer: LoRa + SoMAC
  • Internet Layer: No IP/Not Applicable/SoMAC(?)
  • Transport Layer: SoSTRIP, except it isn't compatible with either TCP nor IP.
  • Application Layer: Unnamed Pipe + ASCII + Cat

Please note that this is purely for demonstration purposes, as it's absolutely unfair to compare TCP/IP and OSI in this way, since they both are designed for different purposes, with TCP/IP being more popular but narrow, and OSI being more general but overly complicated for most use cases.

Also, please feel free to correct me, since it's been a hot moment since I had about OSI and TCP/IP in uni.

==EDIT== Formatting

[–] beernutz@lemmy.world 6 points 3 weeks ago (1 children)

Thank you for this deep and helpful reply! This is the kind of back and forth that really makes Lemmy great!

[–] ekky@sopuli.xyz 3 points 3 weeks ago* (last edited 3 weeks ago)

Thank you!

But don't say that too early, I think the exchange further down could have gone better (not least from my side).

The above is mostly from the top of my head plus most of us are surely still tired after tonight's' festivities. Though, I hope I'm not just reiterating what @Zagorath@aussie.zone already knows, so I hope others will correct me or add on.

load more comments (3 replies)
load more comments (21 replies)