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

Remove obsolete websites with shared credential backend #397

Closed
wants to merge 2 commits into from

Conversation

MartinDevi
Copy link
Contributor

There are quite a few domains which don't match the criteria. As started in the project README:

It wouldn’t be appropriate to associate google.com.il to google.com because google.com.il redirects to accounts.google.com for sign-in, and google.com.il never serves a login page.

I'm guessing that these domains matched the criteria when they were added but the website maintainers have changed the behavior since then.

By that logic, the domains in this MR are removed for the following reasons.

  • alltrails.io redirects to alltrails.com

  • ameritrade.com redirects to tdameritrade.com

  • anylistapp.com redirects to anylist.com

  • capitalone360.com redirects to capitalone.com

  • citibankonline.com and citibank.com redirect to citi.com

  • comcast.net redirects to xfinity.com

  • discordapp.com redirects to discord.com

  • getdropbox.com redirects to dropbox.com

  • microsoft.com and skype.com use live.com SSO

  • office.com uses microsoftonline.com SSO

  • mojang.com redirects to minecraft.net

  • sonyentertainmentnetwork.com doesn't seem to exist anymore

  • square.com redirects to squareup.com

  • [z] I agree to the project's Developer Certificate of Origin

  • [z] The top-level JSON objects are sorted alphabetically

  • [z] There are no open pull requests for the same update

@rmondello
Copy link
Contributor

I think this is helping to show that we need a richer schema here. Some of these are historical entries, which can still be useful for offering cleanup on the client. @Cldfire, I think this is more fuel for the conversations we’ve been having about this.

Really seems like we need a new, richer schema here, overall, which can express more types of relationships.

@Cldfire
Copy link
Collaborator

Cldfire commented Dec 17, 2020

Absolutely; these would all be a great fit for the format proposed in #389.

I plan on getting around to updating the RFC with a format that more closely integrates with what exists today soon!

@Cldfire Cldfire mentioned this pull request Apr 29, 2021
5 tasks
Copy link

@CyberFlameGO CyberFlameGO left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with this PR’s purpose

@dmmaslenn
Copy link
Collaborator

This PR was opened for a while resulting into merge conflicts, so I have tried to address conflicts by updating PR with latest main, but it does not merge cleanly and fails websites-shared-credentials test.
Please feel free to update this PR and make tests pass.

@dmmaslenn dmmaslenn self-requested a review October 7, 2024 20:54
@dmmaslenn
Copy link
Collaborator

Closing this PR due to merge conflicts, please feel free to reopen this PR.

@dmmaslenn dmmaslenn closed this Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants