peer-to-peer

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

Here is what I've noticed:

• ipfs.block.get
  • docs say it returns a Block, but it returns a Uint8Array
  • docs are missing the preload option
• ipfs.block.put
  • docs say it can also take a Block as a parameter, but it can only be a Uint8Array
  • docs say it can take a cid as an option, but the implementation ignores such a parameter
  • docs say it returns a Block, b

All of the CI builds are flavors of linux. It'd be great to add some Windows / Mac ones.

Anybody know github actions and want to help out?

Background

When compaction failed as described in #5936 I got the following message:

could not start compaction, destination folder /home/bitcoin/.lnd/data/graph/mainnet only has 10823012352 bytes of free disk space available while we need at least 10196967424 for worst-case compaction

This is confusing, as 10823012352 > 10196967424.

Your environment

• 0.14.0-beta.rc2
• L

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