Mauve 👁💜 @mauve@mastodon.mauve.moe

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/

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

Then again, UX wise, random HTTP servers that stream loads of data for free (with a bunch of annoying ads) beets out the UX of any BitTorrent thing. 😂 Just enter a link, search the thing, and bam It's right in your face. No need to fuss with clients (but you lose control over how the video is presented)

Oh shit, I entered that headspace again that I call "BitTorrentMode" where I can't shake that the current state of #p2p is honestly behind what BitTorrent was in usability like a decade ago.

I love all the new protocols for their advantages, but the UX just isn't anywhere near "install some random client and paste a link".

They got it right and I wish it kept going instead of losing relevancy.

BEP46 would have solved the UX of needing to search for updated torrents as something is released.

> Body is a `FormData`
```
f = new FormData()
f.append('file', new Blob(["<h1>Hello There! :)</h1>"]), 'index.html')
```
> Add it to the request
> OH FUCK I broke the torrent thing and didn't have tests (guess I'll have to try again another day :P)

Wanted to send a friend a little message.

> Open up @agregore
> Open the Docs for bt-fetch https://github.com/RangerMauve/bt-fetch
> Open a new window (Ctrl+N)
> For get how the hell to make a torrent
> Open the unit tests to see an example: https://github.com/RangerMauve/bt-fetch/blob/default/test.js#L30
> Open Devtoosl (ctrl+shift+i)
> It's a post Request

```
r = await fetch('bittorrent://localhost', {
method: 'post',
})
```

(cont)

Bouta spend 700 bucks to set up my family and friends with NASs as a fuck you to streaming and cloud services for getting too extractive.

Of course you should only be downloading media that you have rights to and should *NOT* follow this guide for adding more search engines to the built in Download Station software.

http://www.synoboost.com/

The Download Station software *shouldn't* be used for pirating copyrighted material from the comfort of any web browser! https://www.synology.com/en-us/dsm/packages/DownloadStation

For example, this guy is going to cost less than a year of Netflix and nobody can randomly take away any media you have saved.

https://www.bhphotovideo.com/c/product/1750525-REG/synology_4tb_diskstation_ds120j_1_bay.html

For anyone else pissed off about #Netflix, I suggest cancelling your subscription and getting a Synology NAS. (and get one for whoever you were sharing Netflix with before too)

It's got a nice web interface for downloading stuff (with a search!) and it can stream to all of your devices (on your home network) via the "SMB" protocol.

Just get the cheapest one that has their browser OS thingie.

https://www.bhphotovideo.com/c/products/Servers/ci/15779?filters=fct_brand_name%3Asynology

SaaS companies are vile and greedy little leaches. They leach from people that actually create content, and they leach from people that pay for it.

I'm already paying them for their fancy mutli-device package but apparently now I need to fork over more just so that my mom can watch some shitty copaganda show once in a while.

Honestly might just cancel outright and teach my folks how to use something else.

I'm up here on the lumberjack statue trying to eat his hat but I'm not getting the cheeve for it 😨 What other hat am I even gonna fund!

My goat is now a fairy. 🥰

Honestly hard to make an image caption that captures this majesty

My goatsona. Purple hotrod fur, fairy wings to fly around, extra horns, skull mask to summon more goat friends, and taco shoes for fart jumps. 😎😎😎

Today's episode: Why is my IPFS file sync taking minutes for just a few files?

Problem: distributed.press v1 is taking like 3 minutes just to sync 44 MB of files from a static site and is taking up a strangely large amount of CPU and Disk to process. This then causes the process to be killed which corrupts the IPFS repo and requires manual intervention.

So far my gut feeling is this is due to me using `flush: true` when uploading data to MFS