Closed rcsilva83 closed 1 year ago
I was thinking of URI scheme that represents Activity objects that can be interpreted by clients. My general idea was to isolate activity type from other properties so that applications can decide how to handle that. Here's my effort.
There is a good conversation going on at https://codeberg.org/fediverse/fediverse-ideas/issues/1 for ways to solve this problem. That might be the best venue for this discussion. This kind of standardisation is important for the ''fediverse'', but is a layer on top of ActivityPub itself. There may be multiple complementary solutions to the problem.
Makes sense, @evanp . I'll close this issue.
Today there is no standard and easy way for one user follow a user from other instance from the same service or from other service. Mastodon guides the user through a workflow involving copy-and-paste, which is a bad UX specially to newcomers from centralized services.
In this issue on Mastodon's repository there is a discussion about a possible solution for this problem by using web-based protocol handlers. I think it would be great if this becomes a Fediverse standard present on all services that support ActivityPub.