-
Notifications
You must be signed in to change notification settings - Fork 1
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
Allow sites to define friend domains #3
Comments
The example of "*.google.com and *.withgoogle.com" would probably be bad since I think they use separate domains for isolation. |
@NDevTK I think they use |
At least from what I can tell *.withgoogle.com hosts less sensitive applications such as event pages. |
Yep that's a good point, whatever mechanism is implemented should probably be only one-way ( |
@sohomdatta1 could you expand on the use case a bit more? I'm having a hard time understanding how this would be useful. Thanks! |
Sure, I've put together a user-story/example of where it would be useful :) Imagine I'm a user who loves reading wikipedia articles and I have already read the article Rabindranath Tagore. Now, I discover en.wikisource.org (which is owned by the same company, Wikimedia Foundation) and come across this page that lists all the works of the author, Rabindranath Tagore. At the top, it also links to the article on Rabindranath Tagore on en.wikipedia.org. Under the current restrictions, this link would not be surfaced as visited (since I haven't actually visited the page from en.wikisource.org, but have done so from en.wikipedia.org) however, if we could allow sharing of link information between trusted sites, interwiki links (which are what these kinds of links are called in the Wikimedia community) would show up as visited if both |
In certain cases, multiple sites/origins could be owned by the same org (ex:
*.wikipedia.org
and*.wikisource.org
or*.google.com
and*.withgoogle.com
). Could we provide some (opt-in) way/mechanism for a site to define other sites to with which:visited
link data can be shared?The text was updated successfully, but these errors were encountered: