Emelia Smith

We've tracked this in our internal issue tracker, however, it requires SDK changes to be supported. I'm going to close this issue, as it's known and cannot be fixed at...

@Dcallies this is something else that we can tackle under that v2 API design that we've discussed.

What about using the Domain / Instance name for "Local" and then "Federated" or "Network" for the remote posts? Though, iirc, local posts do appear in the federated timeline.

Feels like we should probably support both for a few versions and then drop name, in case other fediverse software doesn't prefer summary over name

I think we should send both summary and name for at least one minor version, allowing software to switch over to the new property or implement the cascade as that...

I'm also noticing that potentially our `npm install`s in CI are passing but in local checkouts failing due to differences in peerDep algorithms between npm 8 and prior versions which...

This diff gets it building, but I still can't run the tests from within the container: ```diff diff --git i/dev.Dockerfile w/dev.Dockerfile index 4946d18725..b02384558a 100644 --- i/dev.Dockerfile +++ w/dev.Dockerfile @@ -58,8...

Interestingly, the work that would be needed to enable displaying pronouns in the composer when mentioning from profile would be the same, or at least similar to, that which would...

I think this has been fixed in https://github.com/bluesky-social/atproto/pull/4139

Out of curiosity, would it be better to have an endpoint: `//c/bank/{bank_name}/content/{content_id}/signals` which returns all signals for a given `content_id` and then allow filtering that result set by signal type?...