@quillmatiq @julian personally i find that interop can lead to worse UX if you have to compromise on your own experience to be compatible with someone else's assumptions. so improving UX might require explicitly breaking interop.

more generally, UX friction can be good, and good UX doesn't imply that the thing is good. putting decentralization first means you emphasize values -- do it right before you do it well. putting interop first means you defer the value judgement.

j12t@j12t.social “now I realize I am standing between you and Lunch”

Poor Johannes, at FOSDEM he was standing between us and dinner, too.

chris@socialbc.ca discussing his petition to the Government of Canada to adopt a free and open social media network for communication to all Canadians.

chris@mstdn.chrisalemany.ca talking about starting up SocialBC is inspiring!

Makes me wonder if something like this could happen in Ontario… esp. rural communities.

boris@cosocial.ca giving us ATProto 101.

Good, I have no idea what any of this is.

@julian Quick, we need a new Forkey: Moosekey!

(Or does anyone have a better pun at hand?)

The number of interesting apps and services running off BlueSky is staggering.

Just. What.

I think they’re having more fun over there in ATProto land than us AP folk.

cyberlyra@hachyderm.io on reclaiming tech!

Mm, where are we today?

Time for the panel as hosted by deadsuperhero@social.wedistribute.org

@julian There's like six attendees, not sure how much fun they are having...

@julian unfortunately, I think that’s true.

dansup@mastodon.social is on stage now!

Day 2 of FediCon begins…

Man, the past 5 years

Dan building up onboarding tools to directly counter instance paralysis. YES!

Dan proposing some big ideas to solve AP problems with tech. Nice.

@julian What makes you say that?

@julian

Thanks for sharing live(within the last 30 minutes) what happens

I can't speak for Julian, but I can talk about my impressions from @boris 's presentation.

He went through a dozen different apps running on the ATProto network that create custom data types and interactions and distribute them through the network. It's all happening on the client side, so these new apps aren't their own PDS servers; they can concentrate on cool client experience and leave the distribution up to the back end.

This is almost exactly parallel to the ActivityPub API. It was cool seeing recipes, check-ins, images, events all being created and managed by server less web clients.

It definitely reenergized me for focusing on the ActivityPub API.