Making the cross-wiki requests client-side was a good proof of concept, and actually worked out pretty well. But as people lock up their browser privacy settings we start to run into issues and stuff.
We should make these API requests server-side using curl multi async stuff, and return the output as part of the meta=notifications API response.
| Status | Subtype | Assigned | Task | |
|---|---|---|---|---|
| · · · | ||||
| Resolved | Catrope | T130655 Enable cross-wiki notifications by default | ||
| Resolved | SBisson | T129764 New Error Message for "Error Access to the remote domain was denied." (echo-api-failure-cross-wiki) message and use errorObj? | ||
| Resolved | Catrope | T132954 Gracefully handle outdated echo_unread_wikis rows when a notification type has changed categories (alert->message or v.v.) | ||
| Resolved | matthiasmullie | T130636 Cross-wiki notifications: Make cross-wiki API requests server-side | ||
| · · · |
Change 282738 had a related patch set uploaded (by Matthias Mullie):
[WIP] server-side crosswiki requests
Change 284677 had a related patch set uploaded (by Matthias Mullie):
Server-side crosswiki requests
Change 284682 had a related patch set uploaded (by Matthias Mullie):
Let frontend always query local for foreign sources, instead of those foreign APIs
Change 282738 abandoned by Matthias Mullie:
[WIP] server-side crosswiki requests
Reason:
This one was split up into multiple patches & I forgot to set the same Change-Id. Anyway, this patch is not https://gerrit.wikimedia.org/r/#/c/284677 dependencies.
Change 286782 had a related patch set uploaded (by Catrope):
Use server-side cross-wiki requests in the frontend
Change 286782 merged by jenkins-bot:
Use server-side cross-wiki requests in the frontend
Change 284682 abandoned by Catrope:
Let frontend always query local for foreign sources, instead of those foreign APIs
Reason:
Done by Moriel in https://gerrit.wikimedia.org/r/286782 , although that commit is hacky and better approaches are welcome.