Dockerfile
This file has not been changed.
frontend/src/lib/migration/atproto-client.ts
This file has not been changed.
frontend/src/lib/migration/flow.svelte.ts
This file has not been changed.
frontend/src/lib/migration/types.ts
This file has not been changed.
src/api/repo/record/read.rs
This file has not been changed.
History
4 rounds
12 comments
5 commits
expand
collapse
getRecord requests to the user's PDS after DID resolution instead of a central AppView endpoint.
expand 0 comments
6 commits
expand
collapse
getRecord requests to the user's PDS after DID resolution instead of a central AppView endpoint.
expand 1 comment
5 commits
expand
collapse
getRecord requests to the user's PDS after DID resolution instead of a central AppView endpoint.
expand 5 comments
there, i fixed it
Would you mind rebasing or something? :p i can't see nothin in there (I know it's my fault for pushing massive changes while your PR is open but whatchagonnadoabouttit
i cant resubmit
it wont let me..
yeah it sucks
4 commits
expand
collapse
expand 6 comments
tangled is so funny why did it include the commit already merged here
i dont know how to fix that merge conflict tangled is the best git platform oat
what is this mystical BSKY_APPVIEW_ENDPOINT about :p what if im running tranquil and I wanna support every bsky-esque appview equally?? zeppelin may return in spirit
it's so i can add a backdoor to the ccp
i would reset to the commit before the port/host hardoded thing fix i did and then merge this one as it includes it
like lewis mentioned i dont quite get why the dedicated proxying to a configured bsky appview is needed here? it makes tranquil less generic, less spec compliant and i dont see what functionality it offers over the spec compliant proxying thats already there? (and that modern social-app has luckily been updated to use as it should)
wtf...