Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Reply to @mike@macgirvin.com
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).
---Reply---
Mike Macgirvin@mike@macgirvin.com (2026-06-10 09:04:43)
I might argue that what this represents is quite literally a "filtered view"...
But I could use a path instead.
My normalised-comparison function doesn't alter the original. Will review the portable objects implementation shortly and make certain I got that part right.
Reply
---Replies---
Mike Macgirvin@mike@macgirvin.com (2026-06-10 09:18:09)
But I could use a path instead.
Actually it appears that no, I cannot. Then it is a different object in the eyes of conversation containers. (Because it is a filtered view). I don't see a lot of ways out of this dilemma that doesn't involve breaking something..
[Edit: maybe being silly, but I could send back an array of collections, with the preferred presentation first. What we called multipart/alternative back in the old days. Most software will probably not handle this well, and I'm not even certain my own would. But I would be happy to implement it if it would allow us to all co-exist in the same fediverse.]