I'm looking at the react tutorial at https://github.com/amark/gun/wiki/React-Tutorial and noticed that the code examples are using depreciated lifecycle methods such as componentWillMount.

Hello, I'm updating from 3.1.0 to 4.0.3.

Do we have some documentation available (more advance guide than README.md)? More precisely about WebSocketDelegate?

I don't really know what I should do when these methods are called:

case .viabilityChanged

or

case .reconnectSuggested

What the point of them?

I can see viabilityChanged is called when we loss an

Background

The binaries are built with most of the build flags already set, but when building from source you must specify which tags are desired. This is an important step to building a usable binary from source.

These flags should be listed in the docs, with what their use is for the entire system, and whether or not excluding it would break the normal function of the system.

A sect

To be done on lbrytech repo probably.
The wallet is currently configured as defined originally in ElectrumX, there are some docs for it already in there.

Keep in mind that we added new configuration keys and should clean up the unused ones at some point, so we need something easy

When I switch go from first tabbar controller to second title appears at the bottom.

override func viewDidLoad() {
    super.viewDidLoad()
    
    self.title = "Timers"
    
    self.navigationItem.leftBarButtonItem = UIBarButtonItem.init(image: UIImage.init(named: "close"), style: UIBarButtonItemStyle.plain, target: self, action: #selector(closeDidTap))
}

Hi,
here it is said that Error::TlsFail means we encountered problems during TLS handshake but this error is also returned by other functions e.g one that loads private key
https://github.com/cloudflare/quiche/blob/c726d349120ce72e8f0a00cd5176fd0767325511/src/lib.rs#L475

Will it be a good idea if TlsFail has message

Reading the documentation for the Consume method in the AQMP module.

I came across this (I think in reference to the nolocal parameter):

It's advisable to use separate connections for Channel.Publish and
Channel.Consume so not to have TCP pushback on publishing affect the
ability to consume messages, so this parameter is here mo

On macOS, it's a fairly standard practice to display a pre-roll if your application needs some form of permissions, before calling the system APIs for the first time that will actually produce the system's requested-permissions window.

For instance, for any given end-user, the following window is likely A) intimidating, and B) possibly encourages insecure habits, such as simply clicking "acce

While looking at the code, I noticed there are several failure paths in the QuicPacketBuilderFinalize function that don't result in the current packet metadata being cleaned up. It could have a reference to a stream, which doesn't get released. This will at best leak additional memory, and at worst cause a hang in clean up.

Add the lib directory to the PHP include_path and use an autoloader like the one in the examples directory (the code follows the PEAR/Zend one-class-per-file convention).

That might be a bit misleading for people who are not familiar with composer and don't know every package that must be installed before of trying to use this library.

I have a library that I generate all of my mocks into that is imported in my unit tests. When mocking a protocol, the generated mock object doesn't have an initializer declared. This means is uses the default initializer, which would be fine, except the default init() method is internal. I can get around this by importing my mock library @testable, but I'd suggest that protocol mocks for publi

We currently issue flow control credit immediately upon application-layer consumption of data. This is excessive; we could slightly reduce overhead by instead issuing flow control credit when the amount that would be issued is at least a certain proportion of the entire window.

The reference documentation does not mention the possibility of using a capitalised invoice (eg LNBC..), still most implementations in the wild seem to accept them.

There are good reasons to support capitalised invoices, like smaller QR codes.

My suggestion is to explicitely mention in the documentation that invoices should be case-independant so that implementations must allow both forms (

Awesome project

Perhaps add an example that shows best practice of using StatusProvider with a UITableViewController. This would be very helpful

I'm not sure if I should make use of tableView.backgroundView or set tableView.separatorStyle = .none or show a view that covers the tableView.

Is your feature request related to a problem? Please describe.

When user wants to share link, they usually copy URL from address bar.
This brings UX issue when resource was loaded from local IPFS node running on user's machine.

Describe the solution you'd like

While we have a menu option for copying a shareadble link (ipfs-shipyard/ipfs-companion#857), m