Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Reply to @mike@macgirvin.com
silverpill@silverpill@mitra.social (2026-06-09 18:25:27)
@mike
Yes, whenever the context element is referenced from a naked object per the current FEP-f228.
I tried to fetch context from one of your (private) posts, but the collection contains activities:
https://macgirvin.com/.well-known/apgateway/did:key:z6MkhPXNfiHDh2qSNjFzZ9yY27C1iHnHVbb1eaxuoiEe4tjk/conversation/bf59f105-711d-4c71-96a3-923e90f76e18?posts=true
but trying to still provide reactions since our software considers them to be an integral part of the conversation
One way to provide reactions when only "collection of posts" is available is to use likes and emojiReactions collections, but I doubt that any implementation would actually resolve them.
---Reply---
Mike Macgirvin@mike@macgirvin.com (2026-06-10 05:50:05)
I get exactly one "post", but the collection metadata was incorrect and said it was a collection of 3, and a collectionOf 'activity'. Are you seeing actual activities, or just incorrect metadata? Might need to DM a snippet if the former. If the latter, that should be resolved now.
Reply
---Replies---
silverpill@silverpill@mitra.social (2026-06-10 06:23:02)
@mike I see activities, but I figured out why. The URL is normalized before fetching and ?posts=true parameter is removed during the normalization.
This is because query parameters are not significant in 'ap' URIs:
https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md#comparing-ap-uris
Not sure how to deal with this. I think collections shouldn't have query parameters in their IDs, but query parameters should be allowed in collection views (when filtering is applied).