trystero VS ipfs-webui

This looks exciting and I'm pleased to see more and more frictionless ways of making p2p apps. I've been building a somewhat similar hobby project [1] that aims to connect peers in the browser by piggybacking on open protocols out on the net (BitTorrent, MQTT, Nostr, IPFS, etc).

This project seems to be using Hyperswarm which I've looked at for use as a peering medium but it seems like it's not supported in the browser. I'd love to implement it if that story changes since it's so easy to distribute apps on the web.

[1] https://github.com/dmotz/trystero/

I was going to mention WebRTC! It seems designed for video calling, but there are lots of cool use cases - I recently ran across https://github.com/dmotz/trystero , a dead simple WebRTC library for peer-to-peer multiplayer browser games.

I strongly endorse Trystero (https://github.com/dmotz/trystero) for enabling P2P communication in web apps. It’s open source and leverages public infrastructure for matchmaking.

My attempt to get more out of all my ebook highlights using on-device AI. Click the demo button to try it.

https://github.com/dmotz/trystero

Nice work! Any reason one might use this over https://github.com/dmotz/trystero, you think?

Yes, this is a major issue that I haven't found a real solution for. There seems to be a mixture of iOS Safari bugs and intentional design limitations at play, and I don't know if a fully P2P web app like Chitchatter is practical on that platform. There's an open issue to improve this in Trystero (the networking library that Chitchatter uses), but there may be a limit to how stable iOS will be with WebRTC apps. 😕

You can use Trystero (https://github.com/dmotz/trystero) to cut server costs to zero. That’s what I used to build https://chitchatter.im/, which supports P2P audio and video calls.

WebTorrent is obviously well suited for p2p file distribution, but using a minimal subset of the protocol also provides a nice hack for easily bootstrapping peer connections between web app users. Piggybacking on public mediums already designed to do peer exchange can let you rapidly prototype a WebRTC project without the hassle of running your own server anywhere.

I built a library that explores this idea: https://github.com/dmotz/trystero

ipfs config --json API.HTTPHeaders.Access-Control-Allow-Methods '["PUT", "POST"]' ipfs config --json API.HTTPHeaders.Access-Control-Allow-Origin '["http://192.168.77.214:5001", "http://localhost:3000", "http://127.0.0.1:5001", "https://webui.ipfs.io"]'

webui.ipfs.io

You could also do this: ipfs config --json API.HTTPHeaders.Access-Control-Allow-Origin '["http://IP_ADDRESS_OF_MY_PI:5001", "http://localhost:3000", "http://127.0.0.1:5001", "https://webui.ipfs.io"]' and ipfs config --json API.HTTPHeaders.Access-Control-Allow-Methods '["PUT", "POST"]' ... again, I'm not on fire so obviously I didn't do this myself.

The webui has a pretty cool inspect function that visualizes the CID contents quite nicely.

Try the webui in a browser directly that used to work better for me than the electron wrapped webui. (https://webui.ipfs.io/)

Here is link number 1 - Previous text "bug"

(Low level local pins are not really useful for Desktop users, but since we support remote pinning since IPFS Desktop v0.15.0 and ipfs-webui v2.12 we show them for completeness :))

u/Amoreska do you mind providing more details in https://github.com/ipfs/ipfs-webui/issues/1793 ? Namely, your platform, desktop version + what you mean by "space cap" :)