Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add dweb.link #766

Merged
merged 3 commits into from
May 24, 2019
Merged

Add dweb.link #766

merged 3 commits into from
May 24, 2019

Conversation

mburns
Copy link
Contributor

@mburns mburns commented Feb 5, 2019

  • Description of Organization
  • Reason for PSL Inclusion
  • DNS verification via dig
  • Run Syntax Checker (make test)

Description of Organization

Organization Website: https://protocol.ai

Protocol Labs develops IPFS, which allows end-users to resolve content they have published on the IPFS network using content-based addressing. This content can be resolved by web browsers and other clients in the form http://<hash>.ipfs.dweb.link or http://<peerid>.ipns.dweb.link.

I am an engineer at Protocol Labs and represent the Infrastructure team, responsible for hosting the IPFS Gateways that provide this proxying service. Note that this PR was made as a fork on my personal GitHub account, not the Protocol Labs GitHub organization.

Reason for PSL Inclusion

Because end-users can publish arbitrary content, we would like to sandbox every subdomain as much as possible (cookies, etc).

DNS Verification via dig

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

make test

I have successfully run make test: all PASS.

@mburns mburns changed the title Add ipfs.io Add dweb.link Feb 5, 2019
@mburns mburns changed the title Add dweb.link Add ipfs.dweb.link Feb 5, 2019
@mburns mburns changed the title Add ipfs.dweb.link Add dweb.link Feb 13, 2019
@autonome
Copy link

autonome commented Apr 1, 2019

@weppos @sleevi Hello! Can you please review for inclusion? Thanks!

@autonome
Copy link

@weppos @sleevi Hi, I've read the docs through and I'm pretty sure we've got our 🦆 in a row.

Is there a schedule or process we should wait for?

Thanks!

@sleevi sleevi self-requested a review May 24, 2019 05:45
@sleevi sleevi added the h=sleevi (historical) Marked as approved and ready to merge by @sleevi label May 24, 2019
@sleevi sleevi merged commit 16fef49 into publicsuffix:master May 24, 2019
@autonome
Copy link

autonome commented May 25, 2019 via email

@autonome autonome mentioned this pull request Mar 29, 2022
8 tasks
@aschmahmann aschmahmann mentioned this pull request Aug 6, 2024
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
h=sleevi (historical) Marked as approved and ready to merge by @sleevi
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants