this post was submitted on 08 Jul 2025
308 points (98.7% liked)

Microblog Memes

8507 readers
3943 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
[–] wetbeardhairs@lemmy.dbzer0.com 45 points 5 days ago (3 children)

Lesson #3 on why Baud/s != Bit/s

Lots of serial protocols use stuff bits at the data link layer. The data itself is the clock and if there is no change in the data, the clock is lost. So they after every 4 or so consecutive 0s it adds a fictitious 1 to make sure the recipient's clock is synchronized.

[–] Hugin@lemmy.world 9 points 4 days ago (2 children)

Doesn't USB use manchester encoding like ethernet? So you have a consistent clock frequency it's just weather the data edge is before or after the midpoint.

[–] obinice@lemmy.world 6 points 4 days ago

Hello from Manchester! 👋😃🇬🇧

Beats me. I just know that serial protocols do all kindsa fun stuff at the data link layer to maintain data integrity. Stuff bits, optional parity bits, weird timing changes.