Ugh, this wasn't meant to go on-list (obviously). Sorry!
-- Timo
On Wed, 19 Dec 2018 at 18:55, Timo Tijhof wrote:
> Hi Nuria,
>
> As I understand it, in Safari and Chrome with the default settings, there
> is a native browser feature that, when searching through the address b
Hi Nuria,
As I understand it, in Safari and Chrome with the default settings, there
is a native browser feature that, when searching through the address bar
(Google powered) by default silently starts loading the url of the top
result shown below the address bar. Maybe there's a way we opted out,
Note that the page view information can also be found within the user
interface, on the "Page information" page.
For example, at
https://en.wiktionary.org/w/index.php?title=pie=info
--Krinkle
On Tue, 23 Oct 2018 at 15:34, James Salsman wrote:
> How can I get pageview statistics for individual
On 25 August 2016 at 05:25, Aubrey Rembert wrote:
> hi,
>
> our team is trying to determine how pageviews are attributed to pages that
> redirect to other pages.
>
> for instance, the page Panic!_at_the_*d*isco redirects to the page
> Panic!_at_the_*D*isco, however, in the
It's true that MediaWiki supports search based solely on the ?search query
parameter. Regardless of whether title=Special:Search is specified.
This is mostly for legacy reasons as search predates the concept of special
pages.
However, would it make sense to instead count these as page views for
StackOverflow's recent blog post about renaming their organisation does
make an interesting claim though.
https://blog.stackoverflow.com/2015/09/were-changing-our-name-back-to-stack-overflow/
> The [Stack Exchange] network as a whole has more monthly 5-time posters
than English Wikipedia has
I'd also recommend doing both. +1 to the schema proposed by Gabriel.
I'm sure it'll come up eventually but, just a few thoughts:
* Both can be cached (one can be cached for <24h, the other longer).
* The dynamic range allows useful linking to answer canonical questions
regarding current trends.
On 24 Jul 2015, at 10:52, Dan Andreescu dandree...@wikimedia.org wrote:
I would love it if people on this list or elsewhere would start identifying
the highest value reports from wikistats. We can also use traffic data to
figure out the most popular pages, but this doesn't always mean
Reminds me of the work Next Big Sound has been doing.
Here's what the Next Big Sound dashboard looks like:
http://i.imgur.com/MQBPfdm.png http://i.imgur.com/MQBPfdm.png
.. where the music business is measuring success via popularity social media.
(Including Wikipedia page views!)
According to
On 2 Mar 2015, at 00:35, Nuria Ruiz nu...@wikimedia.org wrote:
Thanks Timo for taking the time to write this.
You're welcome. Thanks for this research. I'm excited about the results.
There are also non-MediaWiki environments (ab)using bits.wikimedia.org and
bypassing the startup
https://www.mediawiki.org/wiki/Analytics/Reports/Clients_without_JavaScript#What_about_IE6.2FIE7.3F
What about IE6/IE7
According to our code base we should not be serving any Javascript to IE6/IE7
browsers other than the startup code that checks for browser compatibility.
[..] However, we
Is that in public version control somewhere?
Assuming not, is there a path towards that?
While I don't mind so much the README, I'm more concerned about the landing
page at http://dumps.wikimedia.org/ which is quite dated and would benefit from
being in public version control so that
Wow, does Googlebot really represent over 1% of our desktop/reader traffic?
Rather interesting compared to that of e.g. WinXP/IE6, which is over 60x
smaller at 0.016%.
But never mind IE6's percentage, that of Google would seem quite high.
— Timo
On 6 Mar 2015, at 01:02, Oliver Keyes
Hi,
Here's a few thoughts about what may influence the data you're gathering.
The decision of whether a browser has sufficient support for our Grade A
runtime happens client-side based on a combination of feature tests and
(unfortunately) user-agent sniffing.
For this reason, our bootstrap
Hey,
Navigation Timing API[1] is getting critical mass[2], and we've been using[3]
it for a while now to gather network information. The timeline one would
generate in Chrome Dev Tools, shows this information. But with this API one can
measure it out in the wild.
The specification process
It seems as of November 29th, something in our logging infrastructure has
stopped.
Does anyone know what happened?
Debugging:
Looking at the graphs[1] reveals all data points have them plummeted straight
down that day and haven't shown any activity since.
Except on December 4th we observed
16 matches
Mail list logo