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

Background

It's unclear to many people what sphinxreplay.db is for.

Context

Replying to the question: "What is sphinxreplay.db for", on Slack:
@Roasbeef : "Security: it prevents replays of onion packets, w/o this ppl can collect onion packetrs then re-inject them and see where they travel to attempt to de-annon"
@Roasbeef : "I think we might be the only impl that handles them pr

We have DAEMON_START metric which shows duration and count of times we need to start up our own daemon. However, we do not have a metric to show how often there are users who are already running an ipfs daemon.

The webui is available when running the go implementation of IPFS, so if we see a lower count for this NO_DAEMON_START metric, then we could potentially redirect any users who are alread

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

I believe these are the knobs for data limits:

https://docs.rs/quinn/latest/quinn/struct.TransportConfig.html#method.stream_receive_window
https://docs.rs/quinn/latest/quinn/struct.TransportConfig.html#method.receive_window

Would like to be able to set these per-connection.

Also, would be great to release this: quinn-rs/quinn#1315

I suppose if a client violates

There are multiple functions that return Result<T, ()> in the code, this is equivalent to Option<T>, however instead of changing those to optional types, these should return useful error messages/types so it's easier to debug.

Example: https://github.com/graphprotocol/graph-node/blob/79390c39a13f166999ceea8defc55eedd05265ab/graph/src/data/subgraph/mod.rs#L169

Some of them could just retu

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

I'm mocking a protocol with a function that looks like this:

func foo(
    completion: @escaping (
        _ bar: Int,
        _ baz: Int,
        _ qux: Int
    ) -> Void
)

The generated mocks do not properly remove the line breaks before attempting to put it into a single-line string literal, resulting in the errors Unterminated string literal, `Consecutive statement