scrap that, I see these are all feature requests that people already captured on the talk page :)

On Aug 21, 2013, at 5:31 PM, Dario Taraborelli dtaraborelli@wikimedia.org wrote:

Hi Jeph,

this is really cool and a great way of showcasing how Wikipedia articles are made.

I can think of many possible ways of expanding this tool – for example, a time range selector with a plot of the frequency of edits over time, for example: I expect people will be interested in replaying parts of an article history when edit wars happen or watch collaboration around trending topics/breaking news, I'm not sure the first N revisions are always the most interesting ones. However these are the first priorities to me:

1. having basic metadata (time/contributor) about a specific revision in the header sounds really important – I don't have any sense of the temporal scale of these edits when I replay them. A tally of unique contributors displayed at each frame would also be helpful.

2. how do you expect to handle very large articles (where you cannot fit the entire body of the article in a browser window)? Having to scroll to see what's happening below or above the fold seems to defy the purpose of a high-level visualization of edit activity.

3. are you going to host this on Labs?

Best Dario

On Aug 20, 2013, at 11:20 AM, jeph jephpaul@gmail.com wrote:

...

Hi,

Im an IEG grantee working on building a tool to visualise the edits in a wikipedia article. My proposal https://meta.wikimedia.org/wiki/Grants:IEG/Replay_Edits A live demo Would love to hear your feedback. You could add feature wishes here.

Thanks Jeph

---

EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

Hi , The visualisation tool has many new features & a new UI. http://cosmiclattes.github.io/wikireplay/player.html

- A graph at the bottom of the page which shows the edits by the size of the edit. - A zoomed in graph which shows more details also doubles up as the playback controls.

Like always feature requests ,bugs & feedback can be added at

- https://meta.wikimedia.org/wiki/Grants:IEG/Replay_Edits - https://github.com/cosmiclattes/wikireplay/issues

Known Issue

- Long articles take some time to load. I'm working on a user notification for that.

Thanks Jeph

On Fri, Aug 23, 2013 at 12:03 AM, jeph jephpaul@gmail.com wrote:

Hi Dario,

The features I'm currently working on are :

• Adding Pause/Forward/Rewind buttons
• Draggable timeline , you can select from where to start playing &

where to end.

• Skipping minor edits etc

The tool currently scrolls the added / deleted / modified content into view , so even when the article gets long it will be possible to see the changes without having to scroll and find out whats happening , did it not scroll when you tried it out ?

I'm planning on making it a js gadget. I'm hoping the tool would be really useful on mobiles as they are more interactive than desktops.

Thanks Jeph

On Thu, Aug 22, 2013 at 6:04 AM, Dario Taraborelli < dtaraborelli@wikimedia.org> wrote:

...

scrap that, I see these are all feature requests that people already captured on the talk page :)

On Aug 21, 2013, at 5:31 PM, Dario Taraborelli < dtaraborelli@wikimedia.org> wrote:

Hi Jeph,

this is really cool and a great way of showcasing how Wikipedia articles are made.

I can think of many possible ways of expanding this tool – for example, a time range selector with a plot of the frequency of edits over time, for example: I expect people will be interested in replaying parts of an article history when edit wars happen or watch collaboration around trending topics/breaking news, I'm not sure the first N revisions are always the most interesting ones. However these are the first priorities to me:

1. having basic metadata (time/contributor) about a specific revision in

the header sounds really important – I don't have any sense of the temporal scale of these edits when I replay them. A tally of unique contributors displayed at each frame would also be helpful.

2. how do you expect to handle very large articles (where you cannot fit

the entire body of the article in a browser window)? Having to scroll to see what's happening below or above the fold seems to defy the purpose of a high-level visualization of edit activity.

3. are you going to host this on Labs?

Best Dario

On Aug 20, 2013, at 11:20 AM, jeph jephpaul@gmail.com wrote:

Hi,

Im an IEG grantee working on building a tool to visualise the edits in a wikipedia article.

• My proposal https://meta.wikimedia.org/wiki/Grants:IEG/Replay_Edits
• A live demohttps://googledrive.com/host/0B1hJO1N6piYFTTVZdW1mU2c0S28/visualise.html

Would love to hear your feedback. You could add feature wishes herehttps://meta.wikimedia.org/wiki/Grants_talk:IEG/Replay_Edits#Features_for_the_tool%23Features_for_the_tool . https://googledrive.com/host/0B1hJO1N6piYFTTVZdW1mU2c0S28/visualise.html

Thanks Jeph

---

EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

---

EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

On Thu, Aug 22, 2013 at 6:04 AM, Dario Taraborelli < dtaraborelli@wikimedia.org> wrote:

...

scrap that, I see these are all feature requests that people already captured on the talk page :)

On Aug 21, 2013, at 5:31 PM, Dario Taraborelli < dtaraborelli@wikimedia.org> wrote:

Hi Jeph,

this is really cool and a great way of showcasing how Wikipedia articles are made.

I can think of many possible ways of expanding this tool – for example, a time range selector with a plot of the frequency of edits over time, for example: I expect people will be interested in replaying parts of an article history when edit wars happen or watch collaboration around trending topics/breaking news, I'm not sure the first N revisions are always the most interesting ones. However these are the first priorities to me:

1. having basic metadata (time/contributor) about a specific revision in

the header sounds really important – I don't have any sense of the temporal scale of these edits when I replay them. A tally of unique contributors displayed at each frame would also be helpful.

2. how do you expect to handle very large articles (where you cannot fit

the entire body of the article in a browser window)? Having to scroll to see what's happening below or above the fold seems to defy the purpose of a high-level visualization of edit activity.

3. are you going to host this on Labs?

Best Dario

On Aug 20, 2013, at 11:20 AM, jeph jephpaul@gmail.com wrote:

Hi,

Im an IEG grantee working on building a tool to visualise the edits in a wikipedia article.

• My proposal https://meta.wikimedia.org/wiki/Grants:IEG/Replay_Edits
• A live demohttps://googledrive.com/host/0B1hJO1N6piYFTTVZdW1mU2c0S28/visualise.html

Would love to hear your feedback. You could add feature wishes herehttps://meta.wikimedia.org/wiki/Grants_talk:IEG/Replay_Edits#Features_for_the_tool%23Features_for_the_tool . https://googledrive.com/host/0B1hJO1N6piYFTTVZdW1mU2c0S28/visualise.html

Thanks Jeph

---

EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

---

EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

On Wed, Aug 21, 2013 at 5:31 PM, Dario Taraborelli < dtaraborelli@wikimedia.org> wrote:

3. are you going to host this on Labs?

This is the tool that Jessie Wild pinged the Analytics list about last

week re: capturing usage. (Thread: "Analytics for tools hosted on labs?"). That email was prompted by a conversation that Siko, Jessie and I had.

Basically, part of Jeph's grant involves an evaluation of Replay Edits, for which he would need to log views and/or other usage data, potentially using some analytics package like Google Analytics (or possibly he can gain limited access to EventLogging?). Since it sounds like GA is discouraged/forbidden on Labs, it might not be ideal for him to host the project there initially--unless there's some more effective way for him to gather the usage data he needs. Any ideas?

- J

Best

Dario

On Aug 20, 2013, at 11:20 AM, jeph jephpaul@gmail.com wrote:

Hi,

Im an IEG grantee working on building a tool to visualise the edits in a wikipedia article.

• My proposal https://meta.wikimedia.org/wiki/Grants:IEG/Replay_Edits
• A live demohttps://googledrive.com/host/0B1hJO1N6piYFTTVZdW1mU2c0S28/visualise.html

Would love to hear your feedback. You could add feature wishes herehttps://meta.wikimedia.org/wiki/Grants_talk:IEG/Replay_Edits#Features_for_the_tool%23Features_for_the_tool . https://googledrive.com/host/0B1hJO1N6piYFTTVZdW1mU2c0S28/visualise.html

Thanks Jeph

---

EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

---

EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

Hi,

- The standalone version ( http://cosmiclattes.github.io/wikireplay/player.html) - This will be on a different domain than en.wikipedia or the other namespaces , (Toolabs, github.io etc) - Is there a way to log the username of the user if he is signed into wikipedia ? - Should we just settle for the ip, time spent, article visualized & revisions visited as metrics. - The gadget - Is it ok to log userinfo from a userscript ? - Should we only use the DB count ? - How do we measure the usage of usescripts , since they can't be counted from the DB like the gadgets ?

Thanks Jeph

On Wed, Dec 18, 2013 at 3:57 AM, Aaron Halfaker ahalfaker@wikimedia.orgwrote:

Re. analytics, Jeph should be able to capture the data he wants for analytics via his tool with some logging code. If the issue is performing analysis of the logged events, I'd be happy to lend a hand.

-Aaron

On Tue, Dec 17, 2013 at 12:36 PM, Jonathan Morgan jmorgan@wikimedia.orgwrote:

...

On Wed, Aug 21, 2013 at 5:31 PM, Dario Taraborelli < dtaraborelli@wikimedia.org> wrote:

...

3. are you going to host this on Labs?

This is the tool that Jessie Wild pinged the Analytics list about last

week re: capturing usage. (Thread: "Analytics for tools hosted on labs?"). That email was prompted by a conversation that Siko, Jessie and I had.

Basically, part of Jeph's grant involves an evaluation of Replay Edits, for which he would need to log views and/or other usage data, potentially using some analytics package like Google Analytics (or possibly he can gain limited access to EventLogging?). Since it sounds like GA is discouraged/forbidden on Labs, it might not be ideal for him to host the project there initially--unless there's some more effective way for him to gather the usage data he needs. Any ideas?

• J

Best

...

Dario

On Aug 20, 2013, at 11:20 AM, jeph jephpaul@gmail.com wrote:

Hi,

Im an IEG grantee working on building a tool to visualise the edits in a wikipedia article.

• My proposal

https://meta.wikimedia.org/wiki/Grants:IEG/Replay_Edits

• A live demohttps://googledrive.com/host/0B1hJO1N6piYFTTVZdW1mU2c0S28/visualise.html

Would love to hear your feedback. You could add feature wishes herehttps://meta.wikimedia.org/wiki/Grants_talk:IEG/Replay_Edits#Features_for_the_tool%23Features_for_the_tool . https://googledrive.com/host/0B1hJO1N6piYFTTVZdW1mU2c0S28/visualise.html

Thanks Jeph

---

EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

---

EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

-- Jonathan T. Morgan Learning Strategist Wikimedia Foundation jmorgan@wikimedia.org +1 (206) 914 - 8358

---

EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

---

EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee

On 12/19/2013 02:13 PM, Aaron Halfaker wrote:

...

Is there a way to log the username of the user if he is signed into

wikipedia ?

From the gadget, yes. From the standalone, no. I don't believe you can confirm which user someone is without having them log in or by using OAuth to let your app identify them.

OAuth isn't really recommended for this either (cases where you're not actually taking any action on a Wikimedia wiki) for security reasons (which someone else could probably explain better.

In the past, I've used the API to look at all of the user pages that end in ".js" to look for an import of my script that isn't *obviously* commented out. (E.g. no comment character before the script import and no enclosing "/* */" style comment around the import.) There ought to be a better way, but I don't know if it.

Script authors sometimes request you put a commented-out link, but this is voluntary, so won't find all imports (however, if you put it in your "please copy this" instructions, I think a lot of people tend to do it). See https://en.wikipedia.org/wiki/Special:WhatLinksHere/User:ProveIt_GT/ProveIt.... .

Matt Flaschen