@trwnh@mastodon.social given that one way a context collection is discovered is via reference via a collection member itself, that's one way to define it. Admittedly, direct access to a context collection is also a legitimate use case (e.g. a NodeBB topic URL itself is the context collection), so something more explicit might be required.

@silverpill@mitra.social I think given the addressing limitations of collections, this by-proxy method of determining who to send an as:Follow to makes sense as a stopgap measure until ActivityPub's next version...

@wjmaggos@liberal.city that's true for Mastodon, but not for other servers with more of a community focused aspect, like NodeBB.

@squinky@teh.entar.net hmm, you should be able to, given it's an unauthenticated resource... But then again maybe some sites require a signed request.

@naturzukunft@mastodon.social just give up and embrace the fact that any given ID might not resolve, either temporarily or permanently.

@hexaheximal@mastodon.social that's fair. I also feel a certain responsibility to protect and defend the fediverse from bad actors, so I get being on guard. I've also seen what happens when fedi brings out the pitchforks, though

@altcode@social.vivaldi.net from what I can tell and from the people I've spoken to, the backend migration is the meat and potatoes of it all, and so the front-end would hopefully remain unchanged. It's one of those huge migrations where if everybody does everything perfectly, nobody will have known anything had happened at all