-
Notifications
You must be signed in to change notification settings - Fork 8
Initial addition of BitTorrent protocol #59
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?
Conversation
jackyzha0
left a comment
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.
generally looks good! a few questions/nits
|
https://0xacab.org/sutty/distributed-press-api-client/-/issues/12 Tracking the client side |
jackyzha0
left a comment
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.
lgtm! small non-blocking question
| async unsync (id: string, _site: Static<typeof BitTorrentProtocolFields>, ctx?: Ctx): Promise<void> { | ||
| } |
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 there nothing for unsync?
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.
Whoops, not yet. It's a TODO.
|
Also, a question. What should we do about existing sites that don't have the protocol set already? I was thinking in the sites.get() function we could check for missing properties and add them in. cc @jackyzha0 thoughts? |
|
Might be good to start thinking about migration scripts? Ideally a one-time thing instead of something that runs on every |
|
great stuff |
Before I get way further it'd be nice if I could get a vibe check on what we have so far and answer any questions about it.