dappnetbby / dappnet Goto Github PK

8080 is too common

Private ENS - https://twitter.com/SpiralPrivacy/status/1582444545228165121

Private IPFS using the same mechanism.

Newest .pkg appears to fail the Gatekeeper checks, have to look into that

encountered by https://twitter.com/harpethr

see https://twitter.com/lightcoin/status/1578791821651881985

ipfs has updated their schema, and check this on launch of their daemon. An outdated schema forces the ipfs daemon to ask for input from stdin, which is breaking functionality in the Dappnet Client.

Version: 1.7.2

Logs:

(base) ➜  ~ /Applications/Dappnet.app/Contents/MacOS/Dappnet
[telemetry] Telemetry enabled: true
[telemetry] Client-Id 6722a25e-76d9-4bcf-95de-988629813952
[telemetry] OS darwin
[telemetry] OS Version 21.2.0
[telemetry] Arch x64
[telemetry] App Version 1.7.2
Dappnet v1.7.2
Do what you think is great work.


/Applications/Dappnet.app/Contents/MacOS/Dappnet

updateServerUrl: https://dappnet-update-server-pi.vercel.app/update/darwin/1.7.2
[telemetry] desktop-app close {"time":1695110654556}
[telemetry] desktop-app open {"time":1695110656358}
LISTENING 0.0.0.0:6801
APP_PATH: /Applications/Dappnet.app/Contents/Resources/app.asar
APP_DATA_PATH: /Users/liamz/Library/Application Support
appPathUnpacked /Applications/Dappnet.app/Contents/Resources/app.asar.unpacked
execPath /Applications/Dappnet.app/Contents/Frameworks/Dappnet Helper.app/Contents/MacOS/Dappnet Helper
ipfsPath /Applications/Dappnet.app/Contents/Resources/app.asar.unpacked/vendor/ipfs/kubo_v0.18.1_darwin-amd64/ipfs
IPFS_PATH /Users/liamz/Library/Application Support/.ipfs/
IPFS_CONFIG_PATH /Users/liamz/Library/Application Support/.ipfs/config
IPFS: starting the daemon
launching ipfs
[exec] /Applications/Dappnet.app/Contents/Resources/app.asar.unpacked/vendor/ipfs/kubo_v0.18.1_darwin-amd64/ipfs daemon
[ipfs] Initializing daemon...
Kubo version: 0.18.1
Repo version: 13

[ipfs] System version: amd64/darwin
Golang version: go1.19.1
Found outdated fs-repo, migrations need to be run.
Run migrations now? [y/N]

Here's what we'd need to do:

• R&D: installing a new root CA
• porting: build a Windows installer executable using electron-build
• porting: including an ipfs binary for windows
• R&D: signing and notarizing the Windows installer
• testing: testing the desktop client
• testing: testing the auto update flow
• testing: testing Chrome .eth resolution and HTTPS with the Windows setup
• docs: updating the docs for windows

Right now updates are signed and delivered through a update centralized server / CDN.

mathew mcconoughhay voice couldn't you distribute em via dappnet itself?

ie. releases.dappnet.eth/v1.0.0.zip, which downloads via IPFS, and self-authenticates using the hash and ENS

https://philo.dev/electron-auto-update-explained/

"Connected to dappnet" is hardcoded rn

Version: 1.7.0

• Simpler tooling for deploying .eth dapps.
• Feedback on upload/download for content.
  • Users can see what % a torrent is, but there’s no equivalent for IPFS.
  • num leechers/seeders
• Add observability for content dissemination on Cloudflare etc - right now it’s impossible to know.
• IPNS sucks - it’s worse than DNSLink for production dapps. Automatic republishing is not built-in, IPNS records are centralized (wtf) unlike the IPFS DHT.
• IPFS node is opaque - I’ve run my node for 1 day and it’s used 10GB of download. What’s it doing? I cannot tell.
• Understanding/configuration of maximum size limits for content on the user-side.

Potential features:

• Private IPFS networks that are gated by token-access would be very useful. e.g. imagine a network of websites that permit access based on some condition.
• Very useful would be an in-browser ipfs API, similar to Metamask, that allows dapps to use "P2P storage" (as opposed to cloud storage).

Observed behaviour:

• When you access uniswap.eth, it loads the page from cache. This is because Uniswap uses the web manifest in order to improve the UX for their users.
• Unfortunately, this also means that this breaks loading from dappnet (sometimes). Ctrl+Shift+R will do a force refresh, no cache.

More investigation needed

Since the local gateway is written using Express/Node, my hunch is that the SOCKS5 server (which is pretty hacky code tbh) is probably the culprit here.

elfarouq.eth

1. Runs installer
2. CA data is generated in NPM module location. But not copied to /Application data dir.

Code signing skill issue

Make the video

• #27 the video
• Update the website with links
• Clean up the documentation
• Draft Mirror.xyz post
  • Roadmap
• Draft Twitter thread
• Notify people in advance - WeekInEth, etc.
• Open-source the repo

Itza too big

• In-browser IPFS API’s - P2P storage for dapps.
• Token gating built into the dappnet.
  • Access forum.xyz.eth only if you own a token.
  • Similar to: Unlock Protocol, Pinata submarining for IPFS
  • But at the web-layer - imagine a network of websites that permit access based on some condition.
• Ability to permalink to articles on the web without them disappearing - built-in IPFS.

• Check arch for binaries - lipo -archs vendor/local-proxy/merino is x86_64
• Check for clean git repo before running npm run publish
• Tag upon running npm run publish

• Support for Safari, MS Edge.
• Support for Windows, Linux.
• Support for mobile (iOS, Android).
  • Partner with Rainbow, Coinbase to help build integration into their wallets.
• Official release via app stores / update channels.
  • Why? Easier install for users, security updates, deliver improved IPFS clients to users.
• Improve performance.
  • #3

they were previously in the undisclosed repo. should put them in test1717

Work items

• dappnet documentation
  • add GA
• desktop app
  • open
  • close
  • launch dapp
  • upgrade
• local gateway
  • resolve-ens
  • resolve-ipfs
  • resolve-ipns
• ipfs resource usage monitoring
  • install-id datetime ipfs-daemon-tag ipfs-libp2p-peerid cpu-usage net-usage storage-usage
• update server
  • page view

How can you improve when you don't measure? What do we want to improve?

• Resolution speeds for .eth domains.
• Resolution speeds for IPFS content.
• Resource usage for P2P downloads (CPU, network).
• Convenience of Dappnet homescreen launcher.
• Convenience of which dapps are useful for users (consequence: come pre-installed by default).

Super important

getDNSEndpoints()
    // testENS

fails when no net