update contact for dweb.link and libp2p.direct

[lidel]

This PR is updating contact information for dweb.link and libp2p.direct entries.
Interplanetary Shipyard is the current entity responsible for maintenance of public good utilities for IPFS and Libp2p ecosystems
(https://docs.ipfs.tech/concepts/public-utilities/)

Original PRs: #766 & #2084

---

Public Suffix List (PSL) Pull Request (PR) Template

Each PSL PR needs to have a description, rationale, indication of DNS validation and syntax checking, as well as a number of acknowledgements from the submitter. This template must be included with each PR, and the submitting party MUST provide responses to all of the elements in order to be considered.

Checklist of required steps

• Description of Organization

• Robust Reason for PSL Inclusion

• DNS verification via dig

• Run Syntax Checker (make test)

• Each domain listed in the PRIVATE section has and shall maintain at least two years remaining on registration, and we shall keep the _PSL txt record in place in the respective zone(s) in the affected section

Submitter affirms the following:

• We are listing any third-party limits that we seek to work around in our rationale such as those between IOS 14.5+ and Facebook (see Issue #1245 as a well-documented example)
  • Cloudflare
  • Letsencrypt

• This request was not submitted with the objective of working around other third-party limits

• The submitter acknowledges that it is their responsibility to maintain the domains within their section. This includes removing names which are no longer used, retaining the _psl DNS entry, responding to e-mails to the supplied address. Failure to maintain entries may result in removal of individual entries or the entire section.

• The Guidelines were carefully read and understood, and this request conforms
• The submission follows the guidelines on formatting and sorting

---

For Private section requests that are submitting entries for domains that match their organization website's primary domain, please understand that this can have impacts that may not match the desired outcome and take a long time to rollback, if at all.

To ensure that requested changes are entirely intentional, make sure that you read the affectation and propagation expectations, that you understand them, and confirm this understanding.

PR Rollbacks have lower priority, and the volunteers are unable to control when or if browsers or other parties using the PSL will refresh or update.

(Link: about propagation/expectations)

• Yes, I understand. I could break my organization's website cookies etc. and the rollback timing, etc is acceptable. Proceed.

---

Description of Organization

Interplanetary Shipyard is an engineering collective of the core maintainers of the most commonly used IPFS and libp2p implementations and public goods infrastructure.

The IPFS is a peer-to-peer content delivery network built around the innovation of content addressing: store, retrieve, and locate data based on the fingerprint of its actual content rather than its name or location.

The libp2p project enables universal connectivity between nodes across different network positions by supporting a wide range of transport protocols.

I am one of the protocol stewards at Interplanetary Shipyard and I am submitting this on behalf of Interplanetary Shipyard which is operating this infrastructure in support of IPFS and libp2p projects.

Organization Website: https://ipshipyard.com & https://docs.ipfs.tech/concepts/public-utilities/

Reason for PSL Inclusion

This PR only updates contact information.

PSL inclusion happened in original PRs: #766 & #2084

DNS Verification via dig

$ dig +short TXT _psl.dweb.link
"https://github.com/publicsuffix/list/pull/2105"
"https://github.com/publicsuffix/list/pull/766"

$ dig +short TXT _psl.libp2p.direct
"https://github.com/publicsuffix/list/pull/2105"
"https://github.com/publicsuffix/list/pull/2084"

Results of Syntax Checker (make test)

$ make test
...
============================================================================
Testsuite summary for libpsl 0.21.5
============================================================================
# TOTAL: 5
# PASS:  5
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0
============================================================================

[simon-friedberger]

Please put the PR template back, it makes sense even for changes like this. Also, please update the _psl DNS entries to this PR.

[simon-friedberger]

@lidel any updates?

[lidel]

@simon-friedberger apologies, missed notification. restored the template, added TXT records (kept old ones, can remove once this PR is merged), and run tests. lmk if anything else is needed from our end.

[wdhdev]

@lidel Please remove the old _psl TXT records, we only require the latest one.

[simon-friedberger]

If there are multiple TXT records that is totally fine with me. Thanks for adding them!

[simon-friedberger]

@lidel If these are handled by the same organization would it make sense to combine them into a single section?

[wdhdev]

If there are multiple TXT records that is totally fine with me. Thanks for adding them!

Oh, I thought we were only meant to have one.

[simon-friedberger]

@wdhdev Maybe I am missing something? What would be the downside of having multiple?

[wdhdev]

Not really any downside, but I was just thinking it would be more simple to just have one so we can easily find the latest PR for that domain. Just a little nitpick I guess.

[lidel]

@simon-friedberger I believe it is better to keep them separate, because these are two separate open source projects. Currently, infrastructure is handled by the same entity, thus the same contact email, but this is only an operational detail.