Hey Team! If you did want to fix it, I’d be happy to monitor it (providing I get notifications) and then prompt people to redirect bug reports to GitHub.
It’ll show other devs thinking of using Cordova that the project is still actively monitored and developed. Let me know! On 2 Nov 2024 at 09:37 +0000, Niklas Merz <niklasm...@apache.org>, wrote: > I'm also in favor of removing Disqus because of the monitoring issue. We > just cant keep track of those comments. > > Redirecting the users to Github discussion sounds like the best > approach. > > On November 2, 2024, Erisu <er...@apache.org> wrote: > > Our website used to display a Disqus commenting section at the bottom > > of > > each blog post, allowing readers to leave comments. > > > > It appears that this feature stopped working about nine months ago > > (based > > on the date of the last comment). > > > > While inspecting the developer tools as the website loaded, I noticed > > that > > two resource files were failing to load because they are missing from > > the > > `frame-src` directive in the Content Security Policy. > > > > I wanted to raise the following questions: > > > > - Do we want to fix and continue supporting Disqus on our blog posts? > > - Do we want to discontinue support and remove Disqus? > > - Has anyone actively monitored or reviewed the comments posted on > > Disqus > > while it was still functioning on the site? > > > > Personally, I am in favor of removing Disqus from the website. I > > haven’t > > actively monitored blog comments to see what was being discussed. Some > > users were raising issues and making requests in the comments, but I > > believe these should be posted on our GitHub repositories. General > > discussions could also be moved to the Discussions tab of our Cordova > > repo. > > > > There may be solutions for integrating GitHub Discussions into the > > blog > > posts as an alternative to Disqus, though this would require > > additional > > investigation. > > > > If we decide to keep Disqus, I’ll update the Content Security Policy > > to > > include the two missing resource files and proceed from there.
