Jan Winkelmann

@Kubuxu I'm not convinced. Imagine the daemon does not yet have the file that the user requested and needs to get it from the ipfs network. That will take a...

@Stebalien @Kubuxu @diasdavid @dignifiedquire What is your opinion on using HTTP/2 directly, without a generic layer of abstraction such as libp2p? It seems to satisfy all of our requirements, and...

@Kubuxu you're right, that would work. However, that sounds like a simple muxing protocol to me. And yes, it has backpressure, but at a huge price: After requesting a file,...

@Kubuxu right, you can reduce roundtrips significantly with pipelining. However in that case, we need to schedule the requests in some way, such that none of our requests starve or...

In https://github.com/ipfs/go-ipfs/issues/5576 a user noted that `ipfs add` responds with objects that contain the file size as string and suggested using ints instead. I agree this is better, but noted...

We had a session on this today. We realized that we have too many targets we want to optimize for, so we won't have a one-size-fits-all solution. For example, it's...

@dignifiedquire I think you may have objections wrt. client implementation complexity, but we'll try to keep this down for the HTTP version. Does that sound good to you?

@whyrusleeping @dignifiedquire Actually JSON doesn't use floats but Numbers, and big.Int implements json.Marshaler and json.Unmarshaler so you can actually do it that way if you expect big.Int. It's just that...

@lgierth I think you know most about what HTTP headers to expect. When configured to accept all origins, old versions of rs/cors send an `AllowOrigin: ` header. New versions will...

Saving also doesn't work, and when clicking the save button this pops up in the console: