Repository navigation
Update Recode.net.xml - #9583
Conversation
|
@J0WI Is this new PR because Recode.net has improved their HTTPS coverage and now we don't need all those exclusions in my older PR? |
|
Exactly. And I also added |
|
Sorry, I didn't see this PR— I just went through all our properties that are defaulting to HTTPS now. |
|
@iamcarrico could you increase the coverage of targets in your pending PR? |
|
I am doing a full audit of our subdomains and will add that in. Note: I am moving cross country this week— so implementation will be slightly delayed. |
|
@J0WI What do you want to do with this PR? |
|
Since there is no progress in #9700 I would love to see this merged. |
|
Mark as Add Also:
|
|
Sorry y'all— I have not been able to get back to this. The structure is unfamiliar, and every time I tried I kept getting bogged down. I can say for certain that all of our sites are 100% HTTPS as of now though. |
|
@iamcarrico That's fine, thanks for following up. If you are going to step back from making Vox rulesets indefinitely, please put a note in your PR #9700 and close it. Also, just FYI, for HTTPS Everywhere we consider domains rather than sites, so for example https://photos.recode.net has an invalid certificate and so we won't include it in our rulesets. From the certificate error it looks like you are relabeling a SmugMug site under |
|
I'll make a ticket to remove that domain— I think it is just legacy gunk. Thank you. |
|
@J0WI Can we move forward on this? I have a checklist #9583 (comment). |
|
|
|
I've updated the checklist through 0a6f921. There are other cookies at https://www.recode.net besides |
|
Done. |
|
Thanks, merged. |
See also #7344