Review allow_sameorg.json

[nodiscc]

Make sure that requests allowed by official-allow_sameorg.json are necessary for user-desirable functionality (eg. {"o":{"h":"*.youtube.com"},"d":{"h":"*.google.com"}}, may not be necessary, youtube.com is functional without requests to google.com)

[myrdd]

exactly. see also my comment #7 (comment)

[nodiscc]

Why not drop allow_sameorg alltogether? I think we should start with a "simple" Allow Functionality subscriptions list, described in #9.

After reviewing such a list, we might want to check individual origin/destinations pairs and move them to a new Allow Functionality only from same organization (which is what allow_sameorg should be called) if appropriate. But in the first time, having 2 lists to manage complexifies things. The allow-sameorg list will be incomplete because it takes a looong time to check every pair in allow-functionality (how do we check it? WHOIS data?).

So I'd like to start fresh with a single list.

[myrdd]

That would be ok for me @nodiscc, but it might be more work if you split the json into two later (?).
However, subscriptions have way less priority than the code itself, at least that's my opinion.

whois data is an option, this probably needs to be investigated.

Please create an issue for each of the steps you're planning to do (or one issue with a task list).