Mauve 👁💜 @mauve@mastodon.mauve.moe

@sleepycat I got my buzzword bingo in seconds. Gonna dig into the source code to see what the ginmick is 😍

@jalcine If you're exploring distros for pinephone, you might be interested in @capyloon which is based on Firefox OS and has some p2p features built in.

Super pumped to be chatting with the person behind https://unit.land/ to talk about how we can use #IPFS in @agregore to make it easy to visually assemble applications with zero extra code.

Saving and loading entire Unit graphs is super easy with IPFS+Fetch and you can even have a zero-server collaborative live coding environment just by plugging libp2p pubsub into the Units graph editor function.

Taking a small step back, and I really think I'd love to work on #Agregore full time. I like the other projects I'm working on right now, but they just don't spark joy in the same way.

@hng Like, illegal streaming sites pay people to scour for content and add it to the site? Where do those people then source it? Do they do the rips on behalf of the site from DVDs and websites?

Where the heck do streaming sites (of the not corpo variety) even source their content? Like, it feels like they're getting data more reliably than torrents these days.

@lumen Are there more local alternatives? Iimagine there's a large community of folks inro this use case over there

The #WASM support seems neat. I heard somewhere that there's a way to perform a query on multiple DB backends at once, so it'd be cool to see if that's possible here.

https://sqlite.org/wasm/doc/trunk/api-worker1.md#method-exec

With that in place you could query data from multiple peers together without needing to merge their datasets.

This is kinda the approach I took for HyperBeeDeeBee in applications where multi-author queries were important.

I feel like I should be using #sqlite in #p2p use cases way more.

Only thing that's unclear, really is how write throughput would work. It seems like doing periodic dumps of datasets is the best use case there, but that doesn't play as nice with applications UX where people expect stuff to sync on the fly.

This "Wikipedia as a static DB" use case is extremely cool for example.

http://static.wiki/en/Peer-to-peer

Neat, somebody put together a #Tor Browser POC in @electronjs a couple of years ago.

I've been thinking of adding the concept of "containers" to @agregore and I think it'd be cool to have a "tor container" which disables #WebRTC and as much fingerprinting stuff as it can to help anonymize users when browsing via Tor.

It'd be cool to do something similar for #i2p

Sadly it'll have to be a TODO since there's no one funding work or devoting spare time to that. :P

Dang, I really wish this played out differently. :(

https://torrentfreak.com/mutable-torrents-proposal-makes-bittorrent-resilient-160813/

@mitra Yeah, the fallback case is a great example of a solved UX pain. FWIW I think IPFS is the closest (non BitTorrent thing) to having a nice story for that, but I think that ends up materializing in the form of gateway URLs and clients defaulting to using those instead of even attempting the p2p in the first place.

Decentralized tech is hard to make because not only does it need to work great, the UX needs to be so much better than the state of the art (download an app from the app store that talks to a server, open a web page that loads _anything_ from a server) that someone would bother using it over their existing workflows. :P