I just had that problem when you browse to a Mastodon post and ⭐️ it, or try to follow someone. The choreography is clumsy, and the kind of thing that will hinder mainstream adoption of ActivityPub.

acct is IANA official and used behind the scenes with webfinger. It’d be dead-simple to enable browsers looking up an app to handle acct: URLs: an ActivityPub client.

It’s trickier to think of how to handle posts, given the discussion about Lemmy/Mastodon interop… and the ActivityStreams spec has a dozen object types! But I think I’m going to want only as many clients as necessary, and one sounds great, so I’m interested to hear what people are thinking at an infrastructure level

  • JoeGermuska@midwest.socialOPEnglish
    0·
    9 months ago

    Thanks for the thoughtful response.

    You can’t exactly expect the URL to indicate the type

    Yes, this seems like one of the bigger hitches. I’ve never investigated, but I wonder if the git+ssh plan is formalized, and whether it is an option

    A smarter app could detect the type of server responsible for managing certain things (i.e. when you’re following a Lemmy community, treat posts in it as such, and not as a flat timeline), …

    Seems a mistake to me too imagine that the future of ActivityPub is servers limited to specific certain content types?

    Need to think more about the client/server parts of your post, but again, thanks for taking the time