Notices by Jeff (jeff@sanjuans.life)

@evan (I actually posted that to both Masto & Bluesky via a multi-honed client, OpenVibe - https://openvibe.social/). Still far from simple enough.

A newcomer's guide to the fediverse.

@evan I think this has an alternate wording: "An ActivityPub server should be runnable by an individual for themself and their friends and family."

The bar for hosting is too high for most people. The code needs to be simplified, rather than the individuals sent to admin school.

@evan I've been struggling to define the fediverse. I don't think it should be solely ActivityPub, but how to qualify that along with other interoperable platforms? Would love your thoughts on this.

I think fediverse >= ActivityPub >= App (Masto) >= Instances, but that might not really mean anything at this time.

@osma @FinchHaven @tchambers @activitypubblueskybridge Actually, so far we have a documented protocol, being developed open-source (https://github.com/bluesky-social/atproto, /indigo, ...) with a very early reference implantation atop that protocol.

If you're point is to write off the potential of the protocol based upon an incompletely initial service atop it, I can't argue with you.

@FinchHaven @tchambers @activitypubblueskybridge Indeed, hoping it is credible because it supports the vision of a fully distributed end state. I suspect the Bluesky instance will continue on OR give people a great tutorial on finding (or hosting!) the right community for themselves. This is not about a "service." It's about thousands of services.

@FinchHaven @tchambers @activitypubblueskybridge The users at greater risk are those who do not domain-back their identities (e.g. janedoe@bsky.social) because their history AND identity key is subject to someone else's control.

@FinchHaven @tchambers @activitypubblueskybridge Yes, but given that Bluesky is so heavily invested in the protocols, it seems like not supporting repository roaming would be unlikely for them. Of course it is possible, but I'm treating this alpha-phase usage as disposable. Once I have my own instance, I'll invest more in the identity + history.

@FinchHaven @tchambers @activitypubblueskybridge Given that a DID is domain-based, isn't the most that you risk is orphaning an early repository?

PS: I like your location.. Salish -> Cascadia -> Northamerica. Same here. I will steal from you. 🙂

@tchambers @activitypubblueskybridge Those are 4 great questions. Time will tell. I've been considering lately the contrast in approaches: Federate from the start, and confuse the hell out of most users, or Singleinstance for a while and risk unproven federation capabilities. Both approaches have advantage. Sadly, the UX/UI experiences on Mastodon make for a second hurdle for most nontechnical users.

Our sanjuans.life community has been added to the official Mastodon server list at https://joinmastodon.org/servers - congratulations, locals! We're discoverable for new users now. #fediverse #SanJuansLife #community