Hi!

Thanks for this nice tool, I like it a lot :-)

I searched the forums and issue tracker, but could not find any discussion on this:
I would like to have a "clean" feature for Simple File Versioning. I think something similar to the feature for Trash Can File Versioning would be useful:

A configuration op

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

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.

Since we can now run interop tests against go-ipfs and js-ipfs quite easily, we could adjust some of our existing tests so that they automatically become interop tests with the right feature turned on.

Consider the recent changes to [tests::connect_two::connect_two_nodes_by_addr](https://github.com/rs-ipfs/rust-ipfs/blob/master/tests/connec