# Publicsuffix pull request help

**URL:** <https://community.letsencrypt.org/t/publicsuffix-pull-request-help/60315>\
**Category:** Help\
**Created:** [April 24, 2018, 8:03am UTC](https://community.letsencrypt.org/t/publicsuffix-pull-request-help/60315 "2018-04-24T08:03:03Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mattn](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mattn/32/20329_2.png) [@mattn](https://community.letsencrypt.org/u/mattn)\
**Post date:** [April 24, 2018, 8:03am UTC](https://community.letsencrypt.org/t/publicsuffix-pull-request-help/60315/1 "2018-04-24T08:03:04Z")

</div>

In few month ago, I posted [Limitation of .jp TLD suffix](https://community.letsencrypt.org/t/limitation-of-jp-tld-suffix/53063)

A person taught me kindfully that I can send GitHub PR to publicsuffix. But the owner of publicsuffix said:

> That request does not comply with our guidelines

> <https://github.com/publicsuffix/list/issues/638#issuecomment-380955494>
>
> Sorry. I don't have strong opinion but it seems that some older pull-requests ar…e not merged even though newer pull-request was merged. And the older pull-requests seems not have problems. What is order of merging them?

So disco-v8 who is administrator of mydns.jp sent request to the form (as mentioned in the GitHub PR) in few weeks ago, but there are no replies, no response, and nothing changed about limitation.

What is right way to avoid limitation?

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [April 24, 2018, 8:26am UTC](https://community.letsencrypt.org/t/publicsuffix-pull-request-help/60315/2 "2018-04-24T08:26:11Z")

</div>

I am not sure if it is the reason for your domain not being processed yet, but the PR _still_ lacks the correction to the #3 item I warned you about in February:

> [@Limitation of .jp TLD suffix](https://community.letsencrypt.org/t/limitation-of-jp-tld-suffix/53063/7):
>
> I…

---

<div class="post-metadata">

**Author:** ![mattn](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mattn/32/20329_2.png) [@mattn](https://community.letsencrypt.org/u/mattn)\
**Post date:** [April 24, 2018, 8:33am UTC](https://community.letsencrypt.org/t/publicsuffix-pull-request-help/60315/3 "2018-04-24T08:33:54Z")

</div>

Thanks for your reply! Now I commented to the PR.

---

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [April 25, 2018, 3:08am UTC](https://community.letsencrypt.org/t/publicsuffix-pull-request-help/60315/4 "2018-04-25T03:08:26Z")

</div>

@_az, maybe when you’re all done with `letsdebug` you could write a `psl-lint` tool? 🙂

---

<div class="post-metadata">

**Author:** ![mattn](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mattn/32/20329_2.png) [@mattn](https://community.letsencrypt.org/u/mattn)\
**Post date:** [April 25, 2018, 3:42am UTC](https://community.letsencrypt.org/t/publicsuffix-pull-request-help/60315/5 "2018-04-25T03:42:14Z")

</div>

Looks nice. And it should run on travis CI.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [May 25, 2018, 3:42am UTC](https://community.letsencrypt.org/t/publicsuffix-pull-request-help/60315/6 "2018-05-25T03:42:16Z")

</div>

Closed on May 25, 2018, 3:42am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.