{"action":"created","issue":{"url":"https://api.github.com/repos/publicsuffix/list/issues/145","repository_url":"https://api.github.com/repos/publicsuffix/list","labels_url":"https://api.github.com/repos/publicsuffix/list/issues/145/labels{/name}","comments_url":"https://api.github.com/repos/publicsuffix/list/issues/145/comments","events_url":"https://api.github.com/repos/publicsuffix/list/issues/145/events","html_url":"https://github.com/publicsuffix/list/issues/145","id":133526211,"number":145,"title":"Clarify number and position of wildcard labels","user":{"login":"weppos","id":5387,"avatar_url":"https://avatars.githubusercontent.com/u/5387?v=3","gravatar_id":"","url":"https://api.github.com/users/weppos","html_url":"https://github.com/weppos","followers_url":"https://api.github.com/users/weppos/followers","following_url":"https://api.github.com/users/weppos/following{/other_user}","gists_url":"https://api.github.com/users/weppos/gists{/gist_id}","starred_url":"https://api.github.com/users/weppos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/weppos/subscriptions","organizations_url":"https://api.github.com/users/weppos/orgs","repos_url":"https://api.github.com/users/weppos/repos","events_url":"https://api.github.com/users/weppos/events{/privacy}","received_events_url":"https://api.github.com/users/weppos/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-02-14T09:51:22Z","updated_at":"2016-03-16T17:09:36Z","closed_at":null,"body":"I made a commit a few weeks ago that introduced a rule like `*.*.private.domain` and the commit [caused the build to fail](https://travis-ci.org/publicsuffix/list/builds/105548386).\r\n\r\n[According to our website](https://publicsuffix.org/list/), that is supposed to be a valid format:\r\n\r\n> Wildcards are not restricted to appear only in the leftmost position, but they must wildcard an entire label. (I.e. *.*.foo is a valid rule: *bar.foo is not.)\r\n\r\n@rockdaboot [mentioned](https://github.com/publicsuffix/list/pull/123#issuecomment-177281704) a potential incompatibility of Chromium if we allow multiple wildcards. `libpsl` is currently not compatible with multiple wildcards, and to be fair [I haven't tested my Ruby implementation either](https://rubygems.org/gems/public_suffix).\r\n\r\n@gerv @sleevi can we clarify whether multiple wildcard labels are accepted? Specifically, we should be more clear if the following rules are valid:\r\n\r\n```\r\n// multiple leading wildcards (common case)\r\n*.*.foo.bar\r\n\r\n// single wildcard, but inside the rule\r\nfoo.*.bar\r\n\r\n// multiple willdcards, inside the rule\r\nfoo.*.*.bar\r\n\r\n// multiple willdcards, inside the rule, non consecutive\r\nfoo.*.bar.*.baz\r\n\r\n// I suppose this is invalid\r\nfoo.*\r\n```\r\n\r\nThe current list definition doesn't explicitly deny these rules, they are supposed to be valid.\r\n\r\nOnce the decision is taken, I think we should:\r\n\r\n1. Update the website to make it more clear\r\n2. Add some corresponding tests in the test file\r\n3. Should the rules be considered invalid, I'll also add the corresponding rules to the [linter I'm working on](https://github.com/weppos/pslint), \r\n4. Should the rules be considered valid, we should ping the various lib maintainers\r\n"},"comment":{"url":"https://api.github.com/repos/publicsuffix/list/issues/comments/197431831","html_url":"https://github.com/publicsuffix/list/issues/145#issuecomment-197431831","issue_url":"https://api.github.com/repos/publicsuffix/list/issues/145","id":197431831,"user":{"login":"User4574","id":134697,"avatar_url":"https://avatars.githubusercontent.com/u/134697?v=3","gravatar_id":"","url":"https://api.github.com/users/User4574","html_url":"https://github.com/User4574","followers_url":"https://api.github.com/users/User4574/followers","following_url":"https://api.github.com/users/User4574/following{/other_user}","gists_url":"https://api.github.com/users/User4574/gists{/gist_id}","starred_url":"https://api.github.com/users/User4574/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/User4574/subscriptions","organizations_url":"https://api.github.com/users/User4574/orgs","repos_url":"https://api.github.com/users/User4574/repos","events_url":"https://api.github.com/users/User4574/events{/privacy}","received_events_url":"https://api.github.com/users/User4574/received_events","type":"User","site_admin":false},"created_at":"2016-03-16T17:09:35Z","updated_at":"2016-03-16T17:09:35Z","body":"Hi\r\n\r\nAs you can see from our pull request here:\r\n\r\n   https://github.com/publicsuffix/list/pull/179\r\n\r\nwe need to get the double wildcard issue addressed, as we need our customer domain suffix in the PSL.\r\n\r\nWe name machines under MACHINE.GROUP.ACCOUNT.CLUSTER.bigv.io, so *.*.*.bigv.io would be ideal, or *.*.uk0.bigv.io.\r\n\r\nThanks\r\nNæþ'n"}}