Marcin Rataj

I believe _raison d'être_ is to - provide mechanism for updating desktop users to the latest go-ipfs - provide GUI for starting/stopping IPFS node and opening specific webui screens: >...

Added a quick note from my end: **ensure webui works in offline mode** If we stop bundling webui with ipfs-desktop and open webui in a web browser, then we need...

For the record, we successfully decoupled codebases :partying_face: - Desktop settings were removed from WebUI and are now in tray icon's menu (https://github.com/ipfs-shipyard/ipfs-desktop/pull/1640, https://github.com/ipfs-shipyard/ipfs-webui/pull/1628) - Also removed special-casing for folder...

> if ipfs.io is blocked at DNS level, I guess that's alright, since that's the user option to do so? Not always. Users in specific countries may have `ipfs.io` blocked...

Hm.. dial check would improve onboarding of new users, but we should avoid using centralized services for the check. AFAIK go-ipfs ships with [AutoNAT](https://github.com/libp2p/go-libp2p-autonat) enabled to determine if node should...

According to those docs, we can specify several publishers in electron-builder. It sounds like a nice migration path: when we are sure self-hosted is stable, we can make it the...

I really like the idea of persisting the list in a configuration file on MFS. Been thinking about doing that for other node-bound features in ipfs-companion as well, and it...

I think if we go with **(B)** and agree that instead of `latest` directory we use regular `YYYY-MM-DD--HHMMSS`, then we could: 1. sort timestamps and grab the latest to tell...

@hacdias I took a stab at writing a spec for this, let's continue in https://github.com/ipfs-shipyard/cohosting/pull/2

Adding Tor support to IPFS Desktop is blocked by https://github.com/ipfs/notes/issues/37: > We have no plans on integrating TOR into go-ipfs _officially_ until there has been full security audit. Then another...