app.userinput.discussion

{
  "body": "Being able to link to external references would be useful. For my use-cases, I see three (maybe Windows-centric) requirements for clicking on an external ref:\n\n- URLs opening in your default browser\n- Paths opening in File Explorer\n- Filepaths opening in the default application associated with the file extension\n\nAn example workflow here is being able to open a PDF/epub directly from your reading notes for that book/paper.\n\nThere are other URI types, i.e. mailto, FTP, or ssh, but practically the first three are the most useful imo",
  "tags": [
    "feature"
  ],
  "$type": "app.userinput.discussion",
  "space": {
    "cid": "bafyreigx747usqrrq6rpotmd7dijtk3r7o2fbwdbqoyqi2ecbwxf5raioy",
    "uri": "at://did:plc:57od6g2ic3e3b3kauctjmo3k/app.userinput.space/3mqpl4jmeaa2y"
  },
  "title": "External refs",
  "createdAt": "2026-07-15T22:05:41.584Z"
}

did:plc:74adbuqkh23sfi6fxubrzs7y | at://did:plc:74adbuqkh23sfi6fxubrzs7y/app.userinput.discussion/3mqpq56ew3y2v

{
  "body": "More details here:\n[https://www.reddit.com/r/CurrentsIs/comments/1v5es7x/comment/ozj0sjj/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button](https://www.reddit.com/r/CurrentsIs/comments/1v5es7x/comment/ozj0sjj/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button)",
  "tags": [
    "feature"
  ],
  "$type": "app.userinput.discussion",
  "space": {
    "cid": "bafyreia4nrm7entk222b4hunnnzgsuqrt4hcdf24qprtqo7olvdhnb2mse",
    "uri": "at://did:plc:jaur46k6ijyfvl4lojza7eic/app.userinput.space/3mob6zfay3e2d"
  },
  "title": "Exclude boards from influencing feed recommendations",
  "createdAt": "2026-07-29T09:44:19.599Z"
}

did:plc:jaur46k6ijyfvl4lojza7eic | at://did:plc:jaur46k6ijyfvl4lojza7eic/app.userinput.discussion/3mrrnbm64ln2l

{
  "body": "I was having a look at the developer docs and was trying to connect and make some requests based on a list of AtUri I have, to check if they were already bookmarked on my end and if not to bookmark them, and I ran into some issues, getting errors 500 back.\n\nYour published DID document (https://standard-reader.app/.well-known/did.json) has:\n{\"id\":\"did:web:standard-reader:app\", ...}\n\nPer the did:web method spec, a domain-root DID should preserve dots in the hostname — colons after the first segment are reserved for encoding path components (and %3A-encoded ports). As published, did:web:standard-reader:app decodes to a host named standard-reader with path segment app, not standard-reader.app — even though the document is actually hosted at the domain root of standard-reader.app. It should read did:web:standard-reader.app.\n\nImpact: This breaks the atproto-proxy integration path your own docs recommend (calling a user's PDS with atproto-proxy: did:web:standard-reader:app#standard_reader_appview). Confirmed via testing:\n- Calling getBookmarkStatus via atproto-proxy through a standards-compliant PDS, using your exact published DID, fails with HTTP 500 ({\"error\":\"InternalServerError\",\"message\":\"Internal Server Error\"}).\n- The identical call, with the DID corrected to proper dot-form, fails the same way — consistent with your did:web resolution likely rejecting it too, since a resolver would fetch the real document and find its id field still says the colon form (a common anti-spoofing self-consistency check).\n- Calling the AppView directly with the same DPoP-authenticated token (bypassing the proxy header entirely) succeeds correctly and returns the expected response.\n\nSo the proxy-header integration path currently appears unusable for any correctly-implemented PDS, not just unusual/self-hosted ones. Fixing the id field to did:web:standard-reader.app should resolve it.\n\nA workaround, already tested and working for me was to skip the atproto-proxy header entirely, and call Standard Reader directly — override the agent's base_uri to https://standard-reader.app just for those specific calls, keeping my normal DPoP auth (no proxy, no PDS forwarding involved).\n\nIf there's another way around this and I was tackling it wrong, I'd be open to try it out too.",
  "tags": [
    "bug"
  ],
  "$type": "app.userinput.discussion",
  "space": {
    "cid": "bafyreieov4wjp5wxp5k4jrt4p5o5kijmqvstzulcntnhfbr5vjeucu674u",
    "uri": "at://did:plc:f4os2wz5fjl56xpwcvtnqu7m/app.userinput.space/3mprrc56lgd2e",
    "$type": "com.atproto.repo.strongRef"
  },
  "title": "did:web document at standard-reader.app breaks atproto-proxy interoperability",
  "createdAt": "2026-08-10T15:28:57.726Z"
}

did:plc:7qubw2z53qzfturlblaozz4a | at://did:plc:7qubw2z53qzfturlblaozz4a/app.userinput.discussion/3msqg3okp3kc7