[Initial]: IPFS v0.15.0

[kn0wmad]

What kind of service is this?

Data

What does this service do?

The Interplanetary File System (IPFS) is a content-addressed, distributed storage network aimed at censorship resistance.  It is currently of great interest to a rapidly growing network of Freedom-oriented content-creators, many of whom already use this service, and will voice support (and possibly even funding) for the first easy-to-use application of it.

How does this service work?

IPFS uses a system of nodes that "pin" content.  These need high availability and redundancy to keep data safe and accessible.  A webUI is available, as well as a docker setup.  The reference implementation is written in Go

What alternative services exist?

Zeronet, Onionshare, Peergos (uses IPFS), Lokinet (requires a shitcoin)

How does this align with our Mission?

• Freedom Tech
• Data Privacy
• Bitcoin/Lightning
• Open Source Dev

How complex is this service?

Medium

How popular is this service?

High Demand

Upstream Repo of Proposed Service

https://github.com/chrisguida/ipfs-wrapper

[kn0wmad]

A functioning proof of concept is already on alpha and the listed repo is for that service wrapper

[kn0wmad]

@cryptodread - how does this get to the next stage? I think I need @MattDHill to give approval next, followed by Aiden. What would that flow look like?

[islandbitcoin]

@cryptodread - how does this get to the next stage? I think I need @MattDHill to give approval next, followed by Aiden. What would that flow look like?

via comments.
@MattDHill will comment here with his approval, followed by
@dr-bonez with his - based on the flowchart.
Then assignments are made (via comments and actual github issue assignments: the engineer, product lead, and marketing person should be assigned to the issue after approval, and listed in the comments.

NOTE: This is going to be a very manual process until we get the steps nailed down. then we can automate some of it.

[MattDHill]

So the service in question is a bare-bones IPFS node? Does it include a UI? How do I use it?

[kn0wmad]

Yes, this is an IPFS node with a webUI. It automatically adds peers, and you can manually add others if you'd like. You can import data from a local machine (or possibly an Embassy volume, such as FB), which will give it a CID (hash), which can be used by peers to fetch that data. A node can also "pin" content, in order to keep a full copy available for download.

Tested so far - node can connect outbound to peers via ipv4/6, and can be connected to using libp2p connections for NAT traversal. Data can be imported to the node on Embassy, and then retrieved by a remote peer.

Content creators are currently the most interested parties for this software

UI Screenshots (dark mode via browser extension, not available as a UI option at this time):

[chrisguida]

dark mode via browser extension, not available as a UI option at this time

😢

[MattDHill]

Green light from me

[islandbitcoin]

I've added labels 'company aligned' and 'architecturally aligned' for service requests. this one has been company aligned via approval by @MattDHill

[dr-bonez]

looks like it will work. please keep me in the loop during the process of building it. this is a big one, and can have a lot of integrations with other services, and could even inspire some os features

[islandbitcoin]

Approved, awesome! Next step is to assign roles for this Service so we can crush this flow and get it on the PROD marketplace:

Service Owner: @kn0wmad
Architect: @dr-bonez
Engineer: @chrisguida
Product: @gStart9
Marketing: Doc
Sovereign: @MattDHill

We are here:

[kn0wmad]

What is SOP for this ticket vs ipfs/kubo#61? They seem to be duplicates

[chrisguida]

ipfs/kubo#61 is to track the initial release, this ticket is to track product lifecycle

[kn0wmad]

So this ticket remains open in perpetuity?

[chrisguida]

It closes when it gets to the far right side of this board

[kn0wmad]

I'm going to make the case that this service be completed (it is half-done and does not appear to be a big lift) by S9 and sent directly to the Community Marketplace to sit and await a maintainer to pick it up. From my perspective, and based on today's meeting, IPFS meets all criteria for a service we would like available, is fairly highly requested by the community at large, and is in extremely high demand by many high-profile content-creators in the freedom community specifically. I'm guessing the main constraint is bandwidth, but I want to argue it remain in line.

[MattDHill]

• Fix Tor chrisguida/ipfs-wrapper#2
• Fix automatic CORS exception chrisguida/ipfs-wrapper#3
• Add FB as a dependency for file storage chrisguida/ipfs-wrapper#4
• Add redirect so user doesn't need to put /webui after the URL to see the web ui chrisguida/ipfs-wrapper#5
• Test/fix gateway chrisguida/ipfs-wrapper#6
• Hook up peer interface (port 4001) chrisguida/ipfs-wrapper#7
• Add config values chrisguida/ipfs-wrapper#8

[chrisguida]

@MattDHill How shall I prioritize this?

[MattDHill]

Let's have a planning session after the LND/CLN stack releases

[chrisguida]

Waiting on this upstream issue: ipfs/ipfs-webui#2031