@MegaMichelle@a2mi.social
@MegaMichelle@a2mi.social avatar

MegaMichelle

@MegaMichelle@a2mi.social

Ann Arbor City Council thoughts, and also random nonsense.

Special abilities: Flying, shooting lasers out of eyes -- you know, "girl power". "Ms. Information". (She/Her) 🏳️‍⚧️

DJ on WCBN-FM, 88.3, https://wcbn.org. Tue 6-9am Eastern time. I play music that is made primarily by people other than cis men. And then I talk about city council stuff.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

MegaMichelle, to random
@MegaMichelle@a2mi.social avatar

#ActivityPub has a lot of the same characteristics as email. But in email, the duties of each part of the process are split up, and you can mix-and-match software. Fediverse software is more tightly coupled than that.

SMTP is like the ActivityPub server-to-server protocol. Like in email with sendmail/exim/postfix/etc, you could have a program that does just this.

IMAP is like the server-to-client protocol. Like in email, with courier/dovecot/etc, you could have a program that does just this.

MegaMichelle,
@MegaMichelle@a2mi.social avatar

One thing the fediverse DOES have is multiple client programs. Like with Thunderbird/Roundcube/K-9 Mail, you can use a few different fediverse client apps, or even a couple that run on the web, like what's that one, Elk?

But a bunch of them, the "user-agents" are tied to the backend. Like, you can't use Mastodon's client with a Firefish server. I think it'd be better for the ecosystem if the clients were split from the servers, and the servers were split into S2S and S2C.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • meta
  • Macbeth
  • All magazines
    •