On macOS, it's a fairly standard practice to display a pre-roll if your application needs some form of permissions, before calling the system APIs for the first time that will actually produce the system's requested-permissions window.

For instance, for any given end-user, the following window is likely A) intimidating, and B) possibly encourages insecure habits, such as simply clicking "acce

I'd like IPFS companion to use a local gateway without exposing a local IPFS API endpoint. Unfortunately, if I do this, companion will direct all dnslink queries to the public gateway because my local IPFS node "has no peers".

If I configure companion to use a specific IPFS gateway, I expect it to always use that gateway.

There is a minor misspelling in the source file qri/api/context.go. The word "collissions" on line 14 should be changed to "collisions".

Per @lidel in ipfs-shipyard/ipfs-webui#1572 (review):

CLI tutor for Import commands ignores the fact we may be in a subdirectory.
Ideally /<dest-name> in import commands would be replaced with "${path}/<dest-name>" where path is the current dir in MFS. I started doing that in [3a337de](ipfs-shipyard/ipfs-webui@3a3

Summary

This is the main tracking issue for DNSLink support. If there is a programmable DNS service out there, we should have support for it.

Ideally even doing things like detecting the provider from the domain name and doing the right thing.

Status

Not providing any repo locking causes difficult to debug issues as I've hit earlier myself and now others have as well, see #241.

Simplest way could be to fail at Repo::init time if a lock file exists. If the lock file doesn't exist, one must be created and again removed at exit time. Probably ok to rely on deletion at Dro

We have types in various places that do not follow the Rust naming conventions. A good example are all the GraphQL* types that should be spelled GraphQl* to follow the conventions.

It would be nice to clean this up by renaming all types that don't follow the rules.

Marking this as a "good first issue", as it's low-hanging fruit and would be a good way for new contributors to contribute somet

Please add a sign up button to main page.

This package generates banners, used by our CLIs and also in some external repos :)

You can open new PRs against this file: https://github.com/berty/berty/blob/master/go/pkg/banner/quote.go