-
-
Notifications
You must be signed in to change notification settings - Fork 26
Add rsky-relay #87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Add rsky-relay #87
Conversation
81e9c5d
to
b4fa73b
Compare
9396fee
to
4857c89
Compare
4857c89
to
23fb97c
Compare
|
||
// false: not polled | ||
// true: polled | ||
pub fn poll(&mut self) -> Result<bool, ConnectionError> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the idea to emulate the future trait?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess kinda, but futures really have a setup -> work -> finish cycle, while this function will be called endlessly & never really produces a result.
a3f5515
to
25f85bf
Compare
25f85bf
to
796f58d
Compare
Summary
Add a ATproto-compliant relay written in Rust.
Usage:
./rsky-relay/crawler.py
(can stop after a few requests & run relay with--no-plc-export
)./rsky-relay/ssl.sh <local ip>
(useip a
to find local ip of an interface)RUST_LOG='rsky_relay=debug' cargo run -rp rsky-relay -- -c <local ip>.crt -p <local ip>.key
./rsky-relay/bootstrap.sh
websocat -k wss://localhost:9000/xrpc/com.atproto.sync.subscribeRepos?cursor=0
Status: I'm able to listen to all bluesky PDSs + fediverse bridge PDS using 1 core & 2GB RAM.
Features:
TODO:
Related Issues
Changes
Checklist