If you knew the collection ID of another instance’s users, you could in theory send them activities that would be forwarded (or not) by that other instance. (Say you knew of an “instance actor” that linked to its “users” collection.)
I guess the nodeinfo could be use to share the instance’s users collection id ? Would you recommend to use absolute or relative identifiers ? From my pov absolute is easier to handle ^^
This is all known as “identity by description”, as opposed to “identity by name” which is a thing you can do to enable easier reuse.
Since the FEP do not forbid it this kind of use case if allowed, but it think we should encourage the use of ids.
yes this was my proposition. But the problem comes when the tracks has a mbid. Various AP track with different ids can share the same mbid. So we should send the audio create activity to each one of them.
because not all audio files or tracks have mbids. When they have we use their db. The proposition was to use `musicbrainzId` on any audio object. I updated the FEP explaining the relation between AP audio objects and MusicBrainz audio objects. A funkwhale track is a musicbrainz recording.