Minutes of Team Meetings (2021)

[SomajitDey]

@ipns-link/members

Date

21-Nov-2021

Location

IPNS-Link Dev room @matrix.org

Agenda

1. Scheme for free .ipns names
2. Design of IPNS-Link Home
3. Porting to languages more suitable than Bash

Action

Free .ipns names

@LynHyper proposed StarMap draft using pubsub rooms and TOTP.
@SomajitDey proposed semi-decentralized scheme with centralized, API-based registry and decentralized resolver.
@rinzler100 pointed out the need for spam and DDoS protection. His solutions: - 1. dPoW (https://nano.org/) for anonymity 2. Email verification with disposable email detection

Required: Drafts are yet to be submitted to this repo.

Design of IPNS-Link Home

Much progress has been made. Sponsors list added, new color scheme and member roles updated.

Porting to languages more suitable than Bash

Go and JS came up as our primary goto. @rinzler100 would handle the JS implementation.

[Winterhuman]

@ipns-link/members

Date

22-Nov-2021

Location

IPNS-Link Dev room @matrix.org

Agenda

1. https://gateway.cloudydestiny.com is now functional, proving that gateway setup is working as intended.
2. http://about.ipns.live (and access through gateways) is now functional.
3. @LynHyper Wrote about a gateway vulnerability where gateway1.tld/ipns/gateway2.tld/ipns/gateway3.tld/... or gateway1.tld/ipns/gateway2.tld/ipns/gateway1.tld/... could allow an attacker to spam gateways.
4. Coming soon page (or azure link) redirection is now functional for https://about.ipns.live.
5. Rough draft needed for about page write-up.
6. https://google.cloudydestiny.com works

Action

Infinite Gateway Recursion

@LynHyper proposed restricting gateways to only allow a single /ipns/ section in the address to prevent recursion.

About page rough draft

@SomajitDey Agreed to write-up the rough draft for the about page.

[Winterhuman]

@ipns-link/members

Date

26-Nov-2021

Location

IPNS-Link Board room @matrix.org

Agenda

1. Team discussed new solution for .ipns in the form of IPDS Databases as proposed by gxnt-samir.
2. gateway.cloudydestiny.com is now a trusted gateway.

Action

IPDS

IPDS is being written up by @LynHyper, once finished it will be posted under dot-ipns as a markdown document and discussed further.

[Winterhuman]

@ipns-link/members

Date

27-Nov-2021

Location

IPNS-Link Board and Dev rooms @matrix.org

Agenda

1. Team discussed Private Gateway spec and updated the doc accordingly. Of note, we still need to figure out the Manifest for when no trusted gateways are used with Private Gateways; <meta> and <a> need a purpose for when no trusted gateways are used.
2. @rinzler100 idea's are now formalized in this discussion for later development (Nano Game Idea #3).
3. Github Donations were discussed, however, we are deciding to keep to our current donation avenues in the meantime. This is primarily due to the 10% fee and tax forms needed for it.
4. @gxnt-samir Has now begun work on the Go implementation of IPNS-Link gateways.

Action

Private Gateways

Figure out what <meta> and <a> should contain when no trusted gateways are used with Private Gateways.

[Winterhuman]

@ipns-link/members

Date

28-Nov-2021

Location

IPNS-Link Board and Dev rooms @matrix.org

Agenda

1. @gxnt-samir mentioned bringing on friends who work in webdev to help us, this could let @rinzler100 focus on the NodeJS implementation while the website work is handled by these potential new members which will help speed up development.
2. Private Gateways spec has been changed again, -g/--gateway option has been added and the secret is now the PeerID of the Listener node.
3. A standalong libp2p-relay-daemon was found: https://github.com/libp2p/go-libp2p-relay-daemon. This might be of future use.

Action

N/A

[Winterhuman]

@ipns-link/members

Date

29-Nov-2021

Location

IPNS-Link Board and Dev rooms @matrix.org

Agenda

1. @gxnt-samir discussed using IPFS-Cluster as the main core for IPFS functionality, this allows scalability later on and doesn't differ too much from go-ipfs. Additionally, he brought up the idea of creating a admin/webui for easier management of IPNS-Link gateways.
2. Discussions are now only enabled for: gateway-registry, forum, contribute, dot-ipns-registry, and specs. This makes it easier to keep track of all the project's discussions.
3. Rate-limiting Exposers to encourage exposed sites to use cache and stream instead of just the gateway's HTTP proxy was discussed, this helps bring more files to IPFS without being too restrictive or outright blocking websites with heavy bandwidth serving.

Action

N/A

[Winterhuman]

@ipns-link/members

Date

30-Nov-2021

Location

IPNS-Link Board and Public rooms @matrix.org

Agenda

1. We met Forest (@ForestJohnson:cyberia.club), the dev of Greenhouse (https://greenhouse.server.garden/), in the Selfhosted Matrix room and discussed in our Public room how they achieve trustless gateways that can't snoop on connections. Opened a discussion on adding this functionality to IPNS-Link: E2E encrypted Origin<-->Browser with TLS Passthrough at Gateway specs#3
2. @LynHyper and @jaguwr discussed how stream is planned to work in IPNS-Link.

Action

Greenhouse anti-snooping system

Need to research more into how we can achieve this in IPNS-Link, seems achievable on a technical level, but, this adds a lot of complexity.

[Winterhuman]

@ipns-link/members

Date

01-Dec-2021

Location

IPNS-Link Board and Dev rooms @matrix.org

Agenda

1. @gxnt-samir, @jaguwr, and @LynHyper discussed how gateways work and how the Go implementation should function.
2. We discussed how DNSLink + TLS passthrough can allow https://domain.tld to work as a standalone website by pointing the TXT record to IPNSKey.ipns.gateway.tld.
3. We discussed how https://ipfsvideo.cc could help with creating/testing the HLS stream feature in IPNS-Link.

Action

N/A

[Winterhuman]

@ipns-link/members

Date

02-Dec-2021

Location

IPNS-Link Board and Dev rooms @matrix.org

Agenda

1. @LynHyper wrote GitHub Wiki pages for the specs repo which covers the IPNS-Link spec more thoroughly: https://github.com/ipns-link/specs/wiki
2. More discussion on go-gateway's implementation was made in the Dev room.

Action

Spec Wiki

@LynHyper will manage the Wiki pages for the foreseeable future, this includes updating and adding new features to the Wiki as they're created. He'd also like to request that the team and community help create questions for the Considerations and Issues section of the Wiki in order to address common concerns.

[Winterhuman]

@ipns-link/members

Date

03-Dec-2021

Location

IPNS-Link Board room @matrix.org

Agenda

1. More discussion on how TLS passthrough and kid.e2e.domain.tld will work.
2. @LynHyper theorised an attack where random people could DNSLink their domains with Origins that aren't theirs. To prevent this, Origins can specify the domains the Origin is supposed to be DNSLinked with and let the Gateway reject DNSLink connections which aren't for the same domains as defined.
3. @LynHyper created a Roadmap: https://github.com/ipns-link/specs/blob/main/Roadmap.md

Action

Spec Wiki

More pages are needed, particularly regarding: TLS Passthrough, DNSLinks, etc.

Roadmap

Team should contribute some rough goals for the Roadmap, this can vary anywhere from bandwidth goals to individual feature implementations.

[Winterhuman]

@ipns-link/members

Date

04-Dec-2021

Location

IPNS-Link Board, Dev, and Public rooms @matrix.org

Agenda

1. @jaguwr, @LynHyper, and Forest from Greenhouse discussed a vulnerability with TLS Passthrough called MITM Proxy, the Gateway in our case can always fake the certificate for the Origin thus negating the usefulness of TLS Passthrough for privacy (See spec Wiki for warning).
2. Today @LynHyper found out deprecated and depreciated are two different words with slightly different meanings, who knew?
3. We are changing our meetups in the Matrix rooms for every Saturday rather than daily, right now a lot of our time is spent talking and discussing when it should be in working (both on IPNS-Link and our jobs outside of the project), we will create a timetable for when people are available for when we want to talk to each other.

Action

MITM Proxy

In response to the vulnerability, we'll be delaying the implementation of kid.e2e.gateway.tld for now.

Team Timetable

We need team members to tell us what times on Saturday they are available relative to UTC-0, this makes finding the time to discuss with each other much easier.

[Winterhuman]

@ipns-link/members

Date

10-Dec-2021

Location

IPNS-Link Board and Dev rooms @matrix.org

Agenda

1. @jaguwr has chosen to leave the Board due to personal reasons, however, he has stated that he hasn't left the project fully which we are very thankful to hear, we wish him a pleasant break.
2. @gxnt-samir has now pushed to the go-gateway repo! He has also created a GitHub Projects board to show what's been completed and what's in the works.
3. With the Next Step Microgrant confirmed and underway, @LynHyper will be writing the Minutes much more frequently than initially planned to show our development more incrementally, he plans to post on https://github.com/ipfs/community/discussions/691 weekly as well per the requirements of the grant.
4. @LynHyper has created a doc for Static Manifest Gateways, this converts Manifests into Static Gateways for a single Exposer and eliminates privacy and security concerns that Public Gateways have, feel free to read it here: https://github.com/ipns-link/forum/blob/main/static-gateway/Static%20Manifest%20Gateways.md
5. @rinzler100 is looking into securing a new domain, https://ipns.live is currently owned by Jaguwr (which he is generously still hosting for us, thank you), we are also considering using fleek.co to host the about page in order to further leverage IPFS in our project.
6. @LynHyper has revamped the Roadmap: https://github.com/ipns-link/specs/blob/main/Roadmap.md

Action

N/A

[rinzler100]

As a side note, I've started the prototype for our project webpage.

[Winterhuman]

@ipns-link/members

Date

15-Dec-2021

Location

IPNS-Link Board and Dev rooms @matrix.org

Agenda

1. Chaitanya has chosen to leave the Board due to unknown personal reasons, we're deeply hopeful that everything is alright and that whatever situation they are in improves.
2. @rinzler100 discussed getting t-shirts for the team to help promote IPNS-Link.
3. Dev team discussed how IPNS-Link Gateways are structured and how they should react to different situations.
4. @LynHyper responded to the Dev discussion by writting a new Wiki page detailing how Gateways work: https://github.com/ipns-link/specs/wiki/Gateway
5. @LynHyper and @rinzler100 discussed how to design the project website, we're currently thinking about a minimal website to reduce complexity and size, this is in an effort to both simplify designing for the website and to better prepare the website for use in Static Gateways in future.
6. @rinzler100 discussed creating a short description or diagram for IPFS in order to better explain the concept for people new to IPFS and IPNS-Link.

Action

Gateway Wiki Page

@LynHyper needs to complete the Wiki page by writing the Step-by-step section.

Project Website Design

An agreement needs to be made on the final design of the project website.

Short IPFS Description/Diagram

@LynHyper plans to rewrite an old doc of theirs to be shorter and easier to explain.

[rinzler100]

Note that IPNS-Link logo is in the works (by @SayantaniBris and @LynHyper), but we have not settled on a final design as of yet.

[Winterhuman]

@ipns-link/members

Team Minute - 22nd Dec 2021

IPNS-Link Board and Dev rooms @matrix.org

Agenda

• The board has chosen @SayantaniBris's design as IPNS-Link's logo going forward.
• @LynHyper wrote a new Wiki page detailing how Exposers work, as well as correct some mistakes related to how cache and stream should function across the Wiki, the Step-by-Step section of the Gateway page has been removed as it proved to be redundant: https://github.com/ipns-link/specs/wiki
• @LynHyper and @rinzler100 have further discussed and developed the project website, we currently have some prototype websites setup at:
  https://prototype1.cloudydestiny.com/ (Dynamic)
  https://ipnslink.cloudydestiny.com/ (Static build of prototype1)

Action

N/A

[Winterhuman]

@ipns-link/members

Team Minute - 27th Dec 2021

IPNS-Link Board room @matrix.org

Agenda

• @LynHyper and @rinzler100 have further developed the project website designs, we will put the designs to a vote to decide on the design going forward.
• Somajit will be running https://ipns.live as a Public IPNS-Link Gateway while we manage the project website separate (domain to be secured at some point), this ensures that if the DNS registrar receives a complaint about content being served at the Gateway we won't lose the project website as well.
• Development overall has slowed down due to the holidays, but, this will pick up in January. We hope you had a wonderful Christmas and a great New Year's day ahead of you.

Action

Project Website

Team needs to vote on a final design to go with, this will be organised soon as both are near initial stage completion.

[Winterhuman]

@ipns-link/members

Team Minute - 30th Dec 2021

IPNS-Link Board room @matrix.org

Agenda

• The project website is now officially here! https://ipnslink.cloudydestiny.com/
  @LynHyper and @rinzler100 made sure to sort out the licensing, both from us and resources we used, and has now made the repo public: https://github.com/ipns-link/project-website
• We still haven't received the Microgrant funds yet, but, we plan to purchase the domain regardless at some point. Once that's done, we'll update all links to point to the new domain.

Action

N/A

[rinzler100]

Wohoo! The website code is now open sourced and can be accessed here!