@webbeef You're a new web browser? Neat! I don't think we have a “just do this one thing” solution for browser builders in ActivityPub right now. FedCM is a thing that people seem to be working on, but I gather it's a future target.Maybe you'd like to incorporate the functionality of https://streetpass.social natively, I think that'd be a low barrier start.Or talk to @benpate about what native browser support for Activity Intents might look like. I hear he doesn't have enough to do yet.

@smallcirclesThere are a couple of #ActivityPub projects that focus on providing the good tools that abstract away the complexities of wire-level network commsYou're talking to a developer of such project.There is no "wire chaos", where did you get this idea from?@fedify

@jdp23 Are they also using Bluesky's servers for DMs, since those are stored off-protocol?Or do non-Bluesky AppViews just don't have DMs? (Or whichever part of the stack is responsible for that.)@jaredwhite @_elena

@unattributed@gotosocial.social that's what the ATP IETF WG is all about, obviously standardisation tasks time. Little known thing, that as far as I know is true, is that ActivityPub is based on a thing Evan's startup used to do (iirc, Pump.io), and then it was brought to the W3C for standardisation

@deadsuperhero if I meet any I'll let you know

@douwe core concept: accounts are hosted separately from apps, so one account logs you in everywhere. All data is stored in your account, and different apps can re-use types of data (called Lexicons).Here’s a second view of the bookmarks I linked above, in a different app https://margin.at/bmann.ca/collection/3m5u77miiyf2hApps can be quite simple, because functions are spread across different parts of the architecture. Feel free to ask more! My atproto account is bridged here @bmann.ca