···11# jetstream-proxy
2233-# WIP LOL
44-53auto-reconnecting jetstream proxy with a default pool that should work
6455+used internally for my own projects already
66+77NOTES:
88-- this should run as close to your infrastructure as possible. you then
99- would connect to `ws://localhost:6969/subscribe`
1010-- no cursor support. since there will be multiple jetstream upstreams that
88+- this should run as close to your infrastructure as possible as the proxy
99+ attempts to find the best jetstream for you. you then
1010+ would connect to `ws://localhost:<port>/subscribe` on your app
1111+- **no cursor support.** since there will be multiple jetstream upstreams that
1112 run at separate cursor timelines, it would be pretty hard to rewrite cursors
1213 in such a way that everything works. if your application relies on cursors,
1314 then it's probably best for your application to deal with multi-upstream support.