-
Updated
Jun 30, 2021
protocol
Here are 1,703 public repositories matching this topic...
-
Updated
Nov 25, 2021 - JavaScript
-
Updated
Oct 22, 2021 - Swift
-
Updated
Oct 31, 2021 - Go
Background
If my node is asked to forward N sats to peer X via channel C, lnd is free to pick any other channel it might have to peer X. As far as I understand the code (switch.go:handlePacketForward), all channels to X (not just C) are checked for eligability, and a random eligable channel is then used for the actual forward.
As part of this eligability check (implemented in link.go:Che
-
Updated
Nov 25, 2021 - Rust
-
Updated
Apr 17, 2019 - Objective-C
- OS: Linux
- Version of IPFS Desktop: 0.16.2
Describe the bug
npm warns about a deprecated module called requests
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
-
Updated
Apr 13, 2020 - Swift
-
Updated
Nov 23, 2021 - C
-
Updated
Nov 25, 2021 - Java
-
Updated
Apr 21, 2021 - C++
Describe the feature you'd like supported
We should change the CID after enough idle time so that any possible NAT rebinding would be harder to be tracked by an outside observer. The simplest way to implement this would be in the flush send code path. When first starting a flush, check how much time has elapsed since the last send. If it's greater than X (20? 30?) seconds force a CID update
-
Updated
Nov 10, 2021 - Go
-
Updated
Nov 15, 2021 - C
-
Updated
Aug 20, 2021 - CSS
-
Updated
Nov 12, 2021 - C
This is a draft anti-ossification measure. See https://github.com/quicwg/quic-bit-grease.
Is your feature request related to a problem? Please describe.
On the Import page, clicking "import options" shows the desired import path that can be changed by the user. Unfortunately any changes to this setting will not be used the next time you go to the Import page.
Describe the solution you'd like
When focus of the text field is lost, it should save to the extension's storage so
-
Updated
Nov 3, 2019 - Go
-
Updated
Nov 6, 2018 - Swift
-
Updated
Nov 25, 2021 - Markdown
Take this class, for example:
`
import Foundation
// some comment has import SOMEBADTHING
public protocol TestProtocol: AnyObject {
func doSomething() -> Void
}
`
The generated mock ends up having:
... import SOMEBADTHING ...
Looks like it is looking for "{import .*}" in source files and just adding that verbatim to the output file, causing compile issues.
-
Updated
Nov 25, 2021 - Rust
Improve this page
Add a description, image, and links to the protocol topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the protocol topic, visit your repo's landing page and select "manage topics."


Creating a new issue based on lbryio/lbry-sdk#877