Feature request

Dat works great out of the box when you're on the same wifi, or are connected to the internet at large, but it's not as great when you're connected to a network that's not totally local, but isn't connected to the internet. Key uses would be something like #1066 where China was blocking traffic, or #1071 talking about mesh networks, which could be relevant to dweb camp 2019.

A brief history of the pages you've visited in the current tab when you right click the back button would make browsing feel better. This is a function that I use regularly in other modern browsers.

Here's an example from Mozilla Firefox:

Operation System: Windows 10
Beak

When installing the Debian package on Ubuntu using Ubuntu Software center, the metadata does need some updates:

• Fix license
• Better description
• icon/logo

I'm not sure this is all easy to configure. This is not critical, so this iss

Hi,

I recently stumbled upon this project. However, when coming to your landing page, I couldn't really tell what it was until reading for a bit. The first thing on the landing page is an argument as to why science fair should exist (which I think is a really great mission and great argument) but it doesn't talk about what it is. There isn't really a one or two sentence description explaining

I'm looking to incorporate support for distributed file systems into some other tools I'm building. I'm having a hard time figuring out how well supported and adopted the datproject is. It would be helpful if on this page:

https://docs.datproject.org/docs/dat-ecosystem

there was a list of libraries available for accessing DAT organized by language. Searching suggests that the primary impleme

Is this intended behaviour?

Current behaviour means that we can’t get a proper progress reading on the first few ‘put’ events.
This could be easily solved by waiting until the dry run - https://github.com/datproject/dat-node/blob/master/lib/import-files.js#L36-L49 - is completed until starting the mirroring process. But then this will also slow down the process of importing for larger dats.

Right now things go pretty poorly if you try to change the dat URL of a site. We should detect that condition and automatically recreate the archive when it occurs.

It would be great to add meaningful godoc comments and examples, document the ways the library can be used (how to use a different migration directory, how to register migrations from the code, etc.)

Collect together into one section and go more thorough.

Good examples from the DEPs:

• Wire Protocol ­— Privacy and Security Considerations
• [Discovery — Privacy concerns](https://github.com/pfrazee/DEPs/blob/discovery-dep/proposals/0000-peer-discovery.md#privacy-co

This issue is to add contributors using the All contributors bot. Merge conflicts may occur with multiple open PRs so these are handled ASAP after they come in.

On the 404 page, it would nice if there was a button to make a new page based on that path... much like the feature often found in wikis.