Would it be crazy to ask for statistics of user agents per page or per namespace?
I'd hypothesize, for example, that IE is used much less outside of the article and portal namespaces.
In case you're wondering what is it useful for: When I have a patch that requires browser compatibility trickery, I may want to invest less time in IE compatibility in a page that is unlikely to be viewed in IE much.
-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore
Hi Amir,
Would it be crazy to ask for statistics of user agents per page or per
namespace?
I'd hypothesize, for example, that IE is used much less outside of the
article and portal namespaces.
I don't think it's crazy. I +1 your hypothesis :] But, yes, I see it difficult to implement:
- The new user-agent breakdown reports (browser-reports.wmflabs.org) are derived from the pageview_hourly table which comes from the webrequest table, both in hadoop. None of them has structured information about the namespace. It should be parsed from the URL or other fields, but the namespaces have different names in different languages, so this would be very tricky.
- Breaking down the user-agent statistics per article would be also very expensive computationally, given the high number of articles. The Pageview API shows pageviews per article, and to reach this we Analytics have had to solve storage and data loading and compression problems, that arose from the big size of that data. Having user-agent breakdown per article would mean multiplying the size of that by a lot.
Maybe I'm missing an easier way to do it, but it seems it would take a long time to solve this.
On Fri, Apr 29, 2016 at 1:04 PM, Amir E. Aharoni < amir.aharoni@mail.huji.ac.il> wrote:
Would it be crazy to ask for statistics of user agents per page or per namespace?
I'd hypothesize, for example, that IE is used much less outside of the article and portal namespaces.
In case you're wondering what is it useful for: When I have a patch that requires browser compatibility trickery, I may want to invest less time in IE compatibility in a page that is unlikely to be viewed in IE much.
-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Marcel is totally right! If you want to do one off analyses for specific pages or namespaces though(like browser breakdown for namespace User: on enwiki - main namespace may not be possible), that may be possible if you run some queries in our Hive store. Do you have access to stat1002(analytics-privatedata-users group)? If not you can request access as per https://wikitech.wikimedia.org/wiki/Analytics/Cluster/Access and we can help you run some one off calculations.
On Fri, Apr 29, 2016 at 10:36 AM, Marcel Ruiz Forns mforns@wikimedia.org wrote:
Hi Amir,
Would it be crazy to ask for statistics of user agents per page or per
namespace?
I'd hypothesize, for example, that IE is used much less outside of the
article and portal namespaces.
I don't think it's crazy. I +1 your hypothesis :] But, yes, I see it difficult to implement:
- The new user-agent breakdown reports (browser-reports.wmflabs.org)
are derived from the pageview_hourly table which comes from the webrequest table, both in hadoop. None of them has structured information about the namespace. It should be parsed from the URL or other fields, but the namespaces have different names in different languages, so this would be very tricky.
- Breaking down the user-agent statistics per article would be also
very expensive computationally, given the high number of articles. The Pageview API shows pageviews per article, and to reach this we Analytics have had to solve storage and data loading and compression problems, that arose from the big size of that data. Having user-agent breakdown per article would mean multiplying the size of that by a lot.
Maybe I'm missing an easier way to do it, but it seems it would take a long time to solve this.
On Fri, Apr 29, 2016 at 1:04 PM, Amir E. Aharoni < amir.aharoni@mail.huji.ac.il> wrote:
Would it be crazy to ask for statistics of user agents per page or per namespace?
I'd hypothesize, for example, that IE is used much less outside of the article and portal namespaces.
In case you're wondering what is it useful for: When I have a patch that requires browser compatibility trickery, I may want to invest less time in IE compatibility in a page that is unlikely to be viewed in IE much.
-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
-- *Marcel Ruiz Forns* Analytics Developer Wikimedia Foundation
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
I'd hypothesize, for example, that IE is used much less outside of the
article and portal namespaces. You mean "editing" versus "reading" traffic?
On Fri, Apr 29, 2016 at 10:45 AM, Madhumitha Viswanathan < mviswanathan@wikimedia.org> wrote:
Marcel is totally right! If you want to do one off analyses for specific pages or namespaces though(like browser breakdown for namespace User: on enwiki - main namespace may not be possible), that may be possible if you run some queries in our Hive store. Do you have access to stat1002(analytics-privatedata-users group)? If not you can request access as per https://wikitech.wikimedia.org/wiki/Analytics/Cluster/Access and we can help you run some one off calculations.
On Fri, Apr 29, 2016 at 10:36 AM, Marcel Ruiz Forns mforns@wikimedia.org wrote:
Hi Amir,
Would it be crazy to ask for statistics of user agents per page or per
namespace?
I'd hypothesize, for example, that IE is used much less outside of the
article and portal namespaces.
I don't think it's crazy. I +1 your hypothesis :] But, yes, I see it difficult to implement:
- The new user-agent breakdown reports (browser-reports.wmflabs.org)
are derived from the pageview_hourly table which comes from the webrequest table, both in hadoop. None of them has structured information about the namespace. It should be parsed from the URL or other fields, but the namespaces have different names in different languages, so this would be very tricky.
- Breaking down the user-agent statistics per article would be also
very expensive computationally, given the high number of articles. The Pageview API shows pageviews per article, and to reach this we Analytics have had to solve storage and data loading and compression problems, that arose from the big size of that data. Having user-agent breakdown per article would mean multiplying the size of that by a lot.
Maybe I'm missing an easier way to do it, but it seems it would take a long time to solve this.
On Fri, Apr 29, 2016 at 1:04 PM, Amir E. Aharoni < amir.aharoni@mail.huji.ac.il> wrote:
Would it be crazy to ask for statistics of user agents per page or per namespace?
I'd hypothesize, for example, that IE is used much less outside of the article and portal namespaces.
In case you're wondering what is it useful for: When I have a patch that requires browser compatibility trickery, I may want to invest less time in IE compatibility in a page that is unlikely to be viewed in IE much.
-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
-- *Marcel Ruiz Forns* Analytics Developer Wikimedia Foundation
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
-- --Madhu :)
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Can you guys remove me from this list?
If the Wikipedia communities and the WMF want to support abusive administrators and retaliatory bans on editors and do not want high output dedicated editors like me improving the projects, then I don't need to get spammed with this emails.
On Mon, May 2, 2016 at 10:58 AM, Nuria Ruiz nuria@wikimedia.org wrote:
I'd hypothesize, for example, that IE is used much less outside of the
article and portal namespaces. You mean "editing" versus "reading" traffic?
On Fri, Apr 29, 2016 at 10:45 AM, Madhumitha Viswanathan < mviswanathan@wikimedia.org> wrote:
Marcel is totally right! If you want to do one off analyses for specific pages or namespaces though(like browser breakdown for namespace User: on enwiki - main namespace may not be possible), that may be possible if you run some queries in our Hive store. Do you have access to stat1002(analytics-privatedata-users group)? If not you can request access as per https://wikitech.wikimedia.org/wiki/Analytics/Cluster/Access and we can help you run some one off calculations.
On Fri, Apr 29, 2016 at 10:36 AM, Marcel Ruiz Forns <mforns@wikimedia.org
wrote:
Hi Amir,
Would it be crazy to ask for statistics of user agents per page or per
namespace?
I'd hypothesize, for example, that IE is used much less outside of the
article and portal namespaces.
I don't think it's crazy. I +1 your hypothesis :] But, yes, I see it difficult to implement:
- The new user-agent breakdown reports (browser-reports.wmflabs.org)
are derived from the pageview_hourly table which comes from the webrequest table, both in hadoop. None of them has structured information about the namespace. It should be parsed from the URL or other fields, but the namespaces have different names in different languages, so this would be very tricky.
- Breaking down the user-agent statistics per article would be also
very expensive computationally, given the high number of articles. The Pageview API shows pageviews per article, and to reach this we Analytics have had to solve storage and data loading and compression problems, that arose from the big size of that data. Having user-agent breakdown per article would mean multiplying the size of that by a lot.
Maybe I'm missing an easier way to do it, but it seems it would take a long time to solve this.
On Fri, Apr 29, 2016 at 1:04 PM, Amir E. Aharoni < amir.aharoni@mail.huji.ac.il> wrote:
Would it be crazy to ask for statistics of user agents per page or per namespace?
I'd hypothesize, for example, that IE is used much less outside of the article and portal namespaces.
In case you're wondering what is it useful for: When I have a patch that requires browser compatibility trickery, I may want to invest less time in IE compatibility in a page that is unlikely to be viewed in IE much.
-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
-- *Marcel Ruiz Forns* Analytics Developer Wikimedia Foundation
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
-- --Madhu :)
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
The unsubscribe link is at the bottom of every email: https://lists.wikimedia.org/mailman/listinfo/analytics. https://lists.wikimedia.org/mailman/listinfo/analytics
On Mon, May 2, 2016 at 9:18 AM, Reguyla reguyla@gmail.com wrote:
Can you guys remove me from this list?
If the Wikipedia communities and the WMF want to support abusive administrators and retaliatory bans on editors and do not want high output dedicated editors like me improving the projects, then I don't need to get spammed with this emails.
On Mon, May 2, 2016 at 10:58 AM, Nuria Ruiz nuria@wikimedia.org wrote:
I'd hypothesize, for example, that IE is used much less outside of the
article and portal namespaces. You mean "editing" versus "reading" traffic?
On Fri, Apr 29, 2016 at 10:45 AM, Madhumitha Viswanathan < mviswanathan@wikimedia.org> wrote:
Marcel is totally right! If you want to do one off analyses for specific pages or namespaces though(like browser breakdown for namespace User: on enwiki - main namespace may not be possible), that may be possible if you run some queries in our Hive store. Do you have access to stat1002(analytics-privatedata-users group)? If not you can request access as per https://wikitech.wikimedia.org/wiki/Analytics/Cluster/Access and we can help you run some one off calculations.
On Fri, Apr 29, 2016 at 10:36 AM, Marcel Ruiz Forns < mforns@wikimedia.org> wrote:
Hi Amir,
Would it be crazy to ask for statistics of user agents per page or per
namespace?
I'd hypothesize, for example, that IE is used much less outside of the
article and portal namespaces.
I don't think it's crazy. I +1 your hypothesis :] But, yes, I see it difficult to implement:
- The new user-agent breakdown reports (browser-reports.wmflabs.org)
are derived from the pageview_hourly table which comes from the webrequest table, both in hadoop. None of them has structured information about the namespace. It should be parsed from the URL or other fields, but the namespaces have different names in different languages, so this would be very tricky.
- Breaking down the user-agent statistics per article would be also
very expensive computationally, given the high number of articles. The Pageview API shows pageviews per article, and to reach this we Analytics have had to solve storage and data loading and compression problems, that arose from the big size of that data. Having user-agent breakdown per article would mean multiplying the size of that by a lot.
Maybe I'm missing an easier way to do it, but it seems it would take a long time to solve this.
On Fri, Apr 29, 2016 at 1:04 PM, Amir E. Aharoni < amir.aharoni@mail.huji.ac.il> wrote:
Would it be crazy to ask for statistics of user agents per page or per namespace?
I'd hypothesize, for example, that IE is used much less outside of the article and portal namespaces.
In case you're wondering what is it useful for: When I have a patch that requires browser compatibility trickery, I may want to invest less time in IE compatibility in a page that is unlikely to be viewed in IE much.
-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
-- *Marcel Ruiz Forns* Analytics Developer Wikimedia Foundation
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
-- --Madhu :)
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Thanks Neil and not to sound rude but I was aware of that. As I told others however it's useless if the account is globally blocked as mine is. Since I cannot login I get an authentication error.
Could you please find someone at the WMF to unsubscribe me from these, because I am quite certain if I start responding to them with links to porn sites or spam someone with the access to do so will arrive. But I shouldn't have to do that.
If the WMF and the communities would rather have abusive admins bullying users than high output dedicated editors like me fine, but I shouldn't have to live with WMF spam because I cannot disenroll from it.
Reguyla
On Mon, May 2, 2016 at 1:22 PM, Neil P. Quinn nquinn@wikimedia.org wrote:
The unsubscribe link is at the bottom of every email: https://lists.wikimedia.org/mailman/listinfo/analytics. https://lists.wikimedia.org/mailman/listinfo/analytics
On Mon, May 2, 2016 at 9:18 AM, Reguyla reguyla@gmail.com wrote:
Can you guys remove me from this list?
If the Wikipedia communities and the WMF want to support abusive administrators and retaliatory bans on editors and do not want high output dedicated editors like me improving the projects, then I don't need to get spammed with this emails.
On Mon, May 2, 2016 at 10:58 AM, Nuria Ruiz nuria@wikimedia.org wrote:
I'd hypothesize, for example, that IE is used much less outside of the
article and portal namespaces. You mean "editing" versus "reading" traffic?
On Fri, Apr 29, 2016 at 10:45 AM, Madhumitha Viswanathan < mviswanathan@wikimedia.org> wrote:
Marcel is totally right! If you want to do one off analyses for specific pages or namespaces though(like browser breakdown for namespace User: on enwiki - main namespace may not be possible), that may be possible if you run some queries in our Hive store. Do you have access to stat1002(analytics-privatedata-users group)? If not you can request access as per https://wikitech.wikimedia.org/wiki/Analytics/Cluster/Access and we can help you run some one off calculations.
On Fri, Apr 29, 2016 at 10:36 AM, Marcel Ruiz Forns < mforns@wikimedia.org> wrote:
Hi Amir,
Would it be crazy to ask for statistics of user agents per page or per
namespace?
I'd hypothesize, for example, that IE is used much less outside of the
article and portal namespaces.
I don't think it's crazy. I +1 your hypothesis :] But, yes, I see it difficult to implement:
- The new user-agent breakdown reports (browser-reports.wmflabs.org)
are derived from the pageview_hourly table which comes from the webrequest table, both in hadoop. None of them has structured information about the namespace. It should be parsed from the URL or other fields, but the namespaces have different names in different languages, so this would be very tricky.
- Breaking down the user-agent statistics per article would be
also very expensive computationally, given the high number of articles. The Pageview API shows pageviews per article, and to reach this we Analytics have had to solve storage and data loading and compression problems, that arose from the big size of that data. Having user-agent breakdown per article would mean multiplying the size of that by a lot.
Maybe I'm missing an easier way to do it, but it seems it would take a long time to solve this.
On Fri, Apr 29, 2016 at 1:04 PM, Amir E. Aharoni < amir.aharoni@mail.huji.ac.il> wrote:
Would it be crazy to ask for statistics of user agents per page or per namespace?
I'd hypothesize, for example, that IE is used much less outside of the article and portal namespaces.
In case you're wondering what is it useful for: When I have a patch that requires browser compatibility trickery, I may want to invest less time in IE compatibility in a page that is unlikely to be viewed in IE much.
-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
-- *Marcel Ruiz Forns* Analytics Developer Wikimedia Foundation
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
-- --Madhu :)
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
-- Neil P. Quinn https://meta.wikimedia.org/wiki/User:Neil_P._Quinn-WMF, product analyst Wikimedia Foundation
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics