specifically, most silos don't have unique permalinks for likes or comments, so bridgy often uses the post's url, which will obviously be shared across its comments and/or likes. bridgy sometimes fabricates synthetic unique permalinks (snarfed/bridgy#215), but not consistently for all responses yet.
fwiw, the mf2, mf1, and hCard/vCard specs/wiki all consistently say that uid should be (universally) unique, but not that url necessarily has to be.
we noticed today that
/api/mentions.json
doesn't return theuid
property to clients. this is unfortunate because it makes some clients (e.g. https://waterpigs.co.uk/services/webmention-io-comments/ , http://stream.thatmustbe.us/ ) fall back to de-duping onurl
, which is usually unique, but not always.specifically, most silos don't have unique permalinks for likes or comments, so bridgy often uses the post's url, which will obviously be shared across its comments and/or likes. bridgy sometimes fabricates synthetic unique permalinks (snarfed/bridgy#215), but not consistently for all responses yet.
fwiw, the mf2, mf1, and hCard/vCard specs/wiki all consistently say that
uid
should be (universally) unique, but not thaturl
necessarily has to be.cc @dissolve @tantek @kevinmarks