The Case for WordPress Telemetry

WordPress prides on being application built by the user for user. The problem is with the improvement. % ) and the user is becoming so small we know almost nothing about the actual people. I kept brining up the well known fact we do not have trace what features 80%, or even 20%, of WordPress users actually use so any claim of relevance in the 80 20 rule is guesswork at best, and in reply one developer told me, we know what the user wants.. The purpose of the Telemetry feature is to amass data about how WordPress is used in the wild. When Telemetry is first added to the page, the admin gets teach asking if they want to contribute anonymized use data to WordPress project. The selector for the number should be resurfaced on first install or when the page is updated to the version of WordPress containing the number is installed.. It is the best way to make users feel this feature is not Trojan horse is to ship it as plugin that auto-installs on opt-in and auto-uninstalls on opt-out... In addition it should be to push custom queries to activated users to test for interactions, as experience how many users double-click Underline in TinyMCE. I'm not sure exactly what the best approach here is, except this is one idea The number queries unified service on daily details to get employment on what type of data is currently being collected.. To prove the sustainability of this feature I propose not quick Start with library of certain datapoints name language setting, number of topic and plugins, and one UI interaction that needs testing.  Read more