Minutes of Team Meetings (2022)

[Winterhuman]

@ipns-link/members

Team Minute - 2nd Jan 2022

N/A

Agenda

• To a new year!!! (This is just an initial post for this year, no real progress update yet)

Action

N/A

[rinzler100]

😄🥳

[Winterhuman]

@ipns-link/members

Team Minute - 13th Jan 2022

N/A

Agenda

• Board members have been discussing a new feature for IPNS-Link, it's yet to be implemented and docs need to be written for it, we will announce the feature here and in the public Matrix room when it's ready.
• Board members helped @rinzler100 to setup an IPNS-Link Gateway at https://gateway.cloudydestiny.com after the previous gateway was lost.
• @LynHyper is writing a doc proposing changes to Manifests to improve security and resolution times, this should make IPNS-Link more responsive and help us achieve a solid level of security more easily, the doc is still in the works while the new Gateway logic is being figured out.

Action

New Feature

Announce to the public once implemented and ready, will appear in the Bash implementation first followed by the feature's addition in the docs and wiki.

Manifest Proposal

@LynHyper will continue working on the proposal doc until nearly all known flaws are addressed and considered, particularly concerning how Gateways should differentiate between Manifests and regular IPNS content, once approved by the board the Wiki will be changed to reflect the new system.

[Winterhuman]

@ipns-link/members

Team Minute - 21st Jan 2022

N/A

Agenda

• We now have a separate domain for own homepage! https://ipnslink.com (Gateway to be moved)
• @LynHyper has been writing more docs related to ManifestV2 and StarMapsV3, these docs are still in the works and need feedback from the board, these docs should hopefully outline more robust, efficient system for achieving IPNS-Link's goals.

Action

New domain

@rinzler100 will move https://gateway.cloudydestiny.com to https://gateway.ipnslink.com in the near future.

Manifest Proposal

@LynHyper will continue working on the docs until all flaws have been addressed, we will also communicate a strategy for how to implement these proposed changes as some changes cannot be made in the Bash implementation of IPNS-Link, there are no hard deadlines on doc completion or on feature implementation.

[Winterhuman]

@ipns-link/members

Team Minute - 30th Jan 2022

N/A

Agenda

• @rinzler100 has updated https://ipnslink.com further, not only has the theme been updated with a dynamic star background in certain pages, but, https://ipnslink.com/get-started.html, https://ipnslink.com/feedback.html, and https://redirect.ipnslink.com have been introduced. https://gateway.ipnslink.com has yet to be introduced due to complications migrating the gateway.
• @LynHyper and @rinzler100 discussed what self-hosted analytics service to use for https://ipnslink.com, we've yet to reach a conclusion on what to use, but, we plan to not use third-party analytic services for the sake of privacy.

Action

Analytics

We need to decide on what self-hosted analytics tool we should use for https://ipnslink.com, there's no hard time limit, but, the sooner we have analytics the better we can adapt our promotion of IPNS-Link to grow our community.

[Winterhuman]

@ipns-link/members

Team Minute - 11th Feb 2022

N/A

Agenda

• @LynHyper has now created https://github.com/LynHyper/ipns-link-alt where people can leave feedback on experimental ideas or suggest their own.
• We have put out a twitter post (https://twitter.com/IPNS_Link/status/1491507192972804096?s=20&t=ADw_b8fOcYwAzbuZk3Ptxg) asking for Go and JS developers interested in joining us, please see the post for details.
• The public Matrix room has been steadily growing these past two weeks. Yay!
• @LynHyper has been ill recently. "Well this sucks, it's been like three years since I've been ill!"

Action

N/A

[Winterhuman]

@ipns-link/members

Team Minute - 19th Feb 2022

N/A

Agenda

• @rinzler100 has been further advertising IPNS-Link to grow the community (Reminder to check out https://twitter.com/IPNS_Link/status/1491507192972804096?s=20&t=ADw_b8fOcYwAzbuZk3Ptxg if you want to develop for us).
• And that's it. It's been quite a slow week as we wait for more developers to join us, we as a team also have lives and even projects outside of IPNS-Link which have taken some of our time, there have been no significant changes to any of the plans set out in the previous forum posts.

Action

N/A

[Winterhuman]

@ipns-link/members

Team Minute - 27th March 2022

N/A

Agenda

• @Winterhuman has proposed an early IPNS-Link V2 spec, this spec aims to solve a few issues with the current spec in light of finding out about inline CID limits, they are requesting that the team give feedback on the spec before it is considered: https://github.com/Winterhuman/ipns-link-alt/wiki/IPNS-Link-V2
• @rinzler100 has further improved the usage of our funds as well as developing our financial reports, this includes exchanging between cryptocurrencies to ensure our funds are as stable as possible while also giving us a light income to give to our developers.
• @Winterhuman recently discovered and learned about Multistreams (https://github.com/multiformats/multistream-select), this knowledge will hopefully lead to more efficient ways of broadcasting specific information to the network as well as a better understanding of existing software.
• "@LynHyper" is now @Winterhuman, GitHub and Matrix names are now the same to prevent confusion.

Action

IPNS-Link V2

Needs to receive feedback to ensure the spec changes are as solid as possible.

[Winterhuman]

@ipns-link/members

Team Minute - 3rd April 2022

N/A

Agenda

• @rinzler100 has further improved the distribution of our funds, more of our funds are stable and in hardware wallets compared to before, this should help keep our funds in a safe and useful position for when they're needed.
• @Winterhuman has made the IPNS-Link V2 spec proposal more concise, they also plan to add IPNS-Link Gateway changes as part of the proposal since it currently only mentions changes to the Exposer.
• @Winterhuman has created a poll in the public room, both for community members and devs, to vote on a replacement for KID (Key Identifier) as the term is quite vague in what Key it's referring to.

Action

IPNS-Link V2

@Winterhuman needs to add the proposed IPNS-Link Gateway changes to the IPNS-Link V2 spec doc, this should happen in the following week.

KID poll

As many community members and devs as available should vote in the poll, or suggest more additions to the poll if none are appealing, before it should be closed. The poll isn't particularly time sensitive at this moment as it is a minor terminology change.

[Winterhuman]

@ipns-link/members

Team Minute - 10th April 2022

N/A

Agenda

• @Winterhuman has added the IPNS-Link Gateway section to the IPNS-Link V2 doc and has concluded the KID replacement poll after one week since creation (Final result was 2 votes to OID, none to the rest).
• Forest discussed with @Winterhuman in the public Matrix room about the OID proposal, he argued that using acronyms for everything isn't necessary when dealing with short names and could harm readability, therefore, @Winterhuman has changed the OID proposal to OriginID (with OID as a likely code-only term).

Action

OriginID decision

Make a decision on Origin (OID) as the term to replace KID. Then, @Winterhuman will go ahead with updating all documentation to reflect this change.

[Winterhuman]

@ipns-link/members

Team Minute - 18th April 2022

Agenda

• OriginID (OID) has now replaced KID, IPNS-Key, and other terms referring to the IPNS addresses associated with Origins.
• @Winterhuman discovered that Multistream-select is planned to be replaced with Protocol-select at some point in the future (protocol-select/: Add Protocol Select specification libp2p/specs#349). Since IPNS-Link uses Multistream protocols (/x/ipns-link/oid), @Winterhuman will keep a close eye on the proposal so we can prepare for the changes ahead of time as well as investigate if Protocol-select brings new benefits that IPNS-Link can take advantage of.
• @Winterhuman has been learning HTTP more in-depth to better understand the HTTP side of IPNS-Link better, and has also been researching the exact constraints of DNS; damn you 63 ASCII characters label limit. This should lead to better explanations/documentation as well as open up possibilities for optimisations for the interface between IPFS and HTTP.

Action

N/A

[Winterhuman]

@ipns-link/members

Team Minute - 26th April 2022

Agenda

• @Captain8771 has joined the dev team! He plans to create Javascript UI for future JS implementations of IPNS-Link.
• @Winterhuman has created a new proposal doc: https://github.com/Winterhuman/ipns-link-alt/wiki/IPNS-Link-V2.1. Most notably, this proposal doesn't use Manifests or even IPNS; the OriginIDs contain all the necessary information to connect to the Exposer. Still very much a WIP, feedback from the community and devs would be appreciated.

Action

IPNS-Link V2.1

Add New Commands section to the proposal doc (done), collect feedback on the existing proposal for any enhancements or flaws mentioned, and overall keep working on the proposal until it is complete in scope.

[Winterhuman]

@ipns-link/members

Team Minute - 2nd May 2022

Agenda

• @Winterhuman has continued to work on the IPNS-Link V2.1 proposal. Most significantly: The multihashes being inlined into OriginIDs are now termed Multihash Proofs, these multihash proofs now use Blake2s-128 instead of SHA-2 for faster hashing and even improved security, OriginIDs will use the full Host: header value since the Host: service method would either be rejected by HTTP servers or would lead to a security vulnerability for private services, and the proposal now describes how IPNS-Link Gateways use Unix sockets and their reverse proxy to redirect oid.ipfs.gateway.tld to /origin/oid at the Exposer.

Action

IPNS-Link V2.1

Add a section describing how TLS passthrough will work for IPNS-Link V2.1 Done. And, continue to gather feedback on the IPNS-Link V2.1 proposal for any enhancements or flaws.

[Winterhuman]

@ipns-link/members

Team Minute - 5th June 2022

Agenda

• Sorry for the time gap between this and the last post, things have been quite hectic outside of the project.
• As for news, no new developments have been made towards IPNS-Link itself. The only notable change is a shift in our funding because of the UST collapse (thankfully, no funds were actually lost because of this), we now spread our funds over a wider set of ecosystems to prevent something like this from happening again.

Action

N/A