this post was submitted on 01 Jan 2026
510 points (99.6% liked)

Microblog Memes

9998 readers
2870 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. Please put at least one word relevant to the post in the post title.
  2. Be nice.
  3. No advertising, brand promotion or guerilla marketing.
  4. Posters are encouraged to link to the toot or tweet etc in the description of posts.

Related communities:

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] jaybone@lemmy.zip 7 points 18 hours ago (1 children)

But TCP and IP are layers in the protocol (that are actually used.) some of the layers are then effectively bypassed as you go further up to application layer.

[–] Zagorath@aussie.zone 1 points 18 hours ago (2 children)

The TCP/IP model is a separate model that only loosely maps on to layers of the OSI model. They're two separate ways of describing how the whole network stack should work, but only one is actually used in the real world.

[–] jaybone@lemmy.zip 2 points 6 hours ago (1 children)

It maps to L4 and L3

TCP/IP also doesn’t include the media layers L2 and L1 (like MAC and frames.)

Maybe think of OSI as the spec and TCP/IP as the implementation of some portions of that spec.

Like UDP would also be L4. So you would miss that too.

[–] Zagorath@aussie.zone 1 points 5 hours ago

Maybe think of OSI as the spec and TCP/IP as the implementation

You could think of it that way. But you would be wrong. That's the whole point.

[–] 4am@lemmy.zip 1 points 17 hours ago

The OSI model is the one used in the real world