Jump to content

Topic on Talk:Talk pages project/Notifications/Flow

Line 4: Line 4:
Thanks for the explanation. Interesting architecture, seems like it might work. I can recall the cases (rare indeed, but still) where Convenient Discussions failed with similar premises in Russian Wikipedia, apart from bot-created sections that I mentioned:
Thanks for the explanation. Interesting architecture, seems like it might work. I can recall the cases (rare indeed, but still) where Convenient Discussions failed with similar premises in Russian Wikipedia, apart from bot-created sections that I mentioned:
*We have an "Administrators' noticeboard" page, and admins who close requests would usually create a subsection and call it "Result". If an admin decides to close multiple requests at once or within a minute, two sections with the same name and oldest timestamp may be created. In this case, looking for the section's ancestors would help. Of course, if you plan to consider ''subsections'' subscribable at all.
*We have an "Administrators' noticeboard" page, and admins who close requests would usually create a subsection and call it "Result". If an admin decides to close multiple requests at once or within a minute, two sections with the same name and oldest timestamp may be created. In this case, looking for the section's ancestors would help. Of course, if you plan to consider ''subsections'' subscribable at all.
*On RfC/polling pages, there are often subsections pre-created for users to comment/vote in support/opposition to some idea, simply called "For" and "Against" or something like that. First of all, initially these sections are empty, with no signatures at all, so I'm curious how will you deal with such sections. When first comments/votes appear in such sections, multiple sections often have identical signatures.
*On RfC/polling pages, there are often subsections pre-created for users to comment/vote in support/opposition to some idea, simply called "For" and "Against" or something like that. First of all, initially these sections are empty, with no signatures at all, so I'm curious how you deal with such sections. When first comments/votes appear in such sections, multiple sections often have identical signatures.


May I ask about a thing that I'm strongly concerned about—will topic subscription be open to integration with user scripts? The architecture you described looks promising, so there could be no point to keep the section watching functionality in existing tools, including my CD, given that a third-party script (not an extension) would never have the capacity of a native tool with full support from backend. But for user scripts to embrace the native functionality, there should be convenient integration, for example the ability to read and write topic subscriptions using API.
May I ask about a thing that I'm strongly concerned about—will topic subscription be open to integration with user scripts? The architecture you described looks promising, so there could be no point to keep the section watching functionality in existing tools, including my CD, given that a third-party script (not an extension) would never have the capacity of a native tool with full support from backend. But for user scripts to embrace the native functionality, there should be convenient integration, for example the ability to read and write topic subscriptions using API.