protocol

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

• Update ensure_directory_exists() to check that the directory is writable by the current process.
• If it's not, return a useful error
• Add tests to cover the case when
  • download directory does not exist
  • download dir exists but is not writable
  • dir exists an

In the output of list channels the private/public status of the channel is returned, but in the output of pending channels the status is not revealed. To allow for recognizing a pending open channel as a private requires waiting for the channel to confirm.

Ideally the PendingChannelsResponse would include the channel flags or the private/public status of the channel to know which type of chan

• OS: Linux
• Version of IPFS Desktop: 0.16.2

Describe the bug
npm warns about a deprecated module called requests

npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142

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

This is a draft anti-ossification measure. See https://github.com/quicwg/quic-bit-grease.

Seems that Firefox (around version 96-97) changed somethign and is now way more aggresive when a gateway does not start returning response immediately.

For example, first load (empty ipfs repo) of http://dist.ipfs.io.ipns.localhost:8080/go-ipfs/v0.11.0 in Firefox 97 produces:

![2022-02-11_19-09](https://user-images.githubusercontent.com/157609/153646056-9bc942ec-bec7-4f0a-b61b-53db7bf6896

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.