Right now, Syncthing seems to always use LF for line endings in config.xml and .stignore. This is a problem in Windows when trying to edit those using the built-in Notepad, which until very recently had no support for other line endings than CRLF. Support for them has only been added in the very recent versions of Windows 10.

The problem is that when opening those files in Notepad under old

Hello!

When text line in list is too long and part of it is moved on the next line, list number is placed on the last line. When I use <br>, list number is placed on the first line of multiline text.

Demo is below:

Demo text:

1. [ ] task 1
2. [ ] task 2 task 2 task 2

Forking ipfs/js-ipfs#3252 (comment) into separate issue.

Looks like some of our API calls return values that refer to same ArrayBuffer, which in turn causes one of the encoder functions https://github.com/ipfs/js-ipfs/tree/master/packages/ipfs-message-port-protocol/src to add it to the transfer list twice and error on postMessage.

Background

When a node has multiple private channels with the same peer, the hop hints in their payment requests will be populated with multiple channels. The purpose of these hop hints is to specify the next node's key and indicate the fees and cltv delta needed for route construction.

In pathfinding, due to non-strict forwarding, an LND node paying to this destination will only use the

Since the URLs are just a gate pass for the video call, there might be a chance of getting intruders into the call with a simple brute force.

Users feel more secure if we have some passcode or approval from the creator to join into call.

This was cut from the v0.2.0 release for present time constraints however making ipfs-http more accessible as "the" ipfs binary would make the project more accessible to anyone just wanting to try it out. At the moment I see the following obstacles:

• http/README.md has no tutorial on how to try out ipfs-http
• ipfs-http supports only `i