You n*rds are 100 years behind Facebook, who already shows
Yesterday via email
About an hour ago via mobile
59 minutes ago near Tsoying, Kao-hsiung
24 minutes ago via POCO Beautycamera
Throw in the towel.
___
Wikitech-l mailing list
On Mon, Nov 19, 2012 at 7:43 PM, jida...@jidanni.org wrote:
You n*rds are 100 years behind Facebook, who already shows
Yesterday via email
About an hour ago via mobile
59 minutes ago near Tsoying, Kao-hsiung
24 minutes ago via POCO Beautycamera
Throw in the towel.
Another excellent post
On Mon, 19 Nov 2012 21:11:40 -0800, John Du Hart compwhi...@gmail.com
wrote:
On Mon, Nov 19, 2012 at 7:43 PM, jida...@jidanni.org wrote:
You n*rds are 100 years behind Facebook, who already shows
Yesterday via email
About an hour ago via mobile
59 minutes ago near Tsoying, Kao-hsiung
24
On Tue, Nov 20, 2012 at 4:00 PM, Daniel Friesen
dan...@nadir-seen-fire.com wrote:
Sooo... when do we set him as 'moderated'?
I've already notified one of the list moderators, We don't need to
discuss and bring any more attention to this.
___
True, sorry, I didn't look closely enough to realize that tag_summary is
denormalized change_tag.
However, this doesn't deal with the problem that [[Special:Tags]] will get
cluttered with this approach. It might work for a mobileedit tag, but
valid_tag cannot grow arbitrarily.
True, but
I misread this, I didn't realize MZMcBride is talking about
RecentChanges.
How unreasonable would it be to call ChangeTag::AddTags('mobile',
$rc_id); for mobile edits? On first blush, the only major consequences is
extracting the data since it'd be buried in a ts_tags
On Nov 16, 2012, at 3:25 PM, bawolff bawolff...@gmail.com wrote:
I misread this, I didn't realize MZMcBride is talking about
RecentChanges.
How unreasonable would it be to call ChangeTag::AddTags('mobile',
$rc_id); for mobile edits? On first blush, the only major
On 15.11.2012, 4:06 Diederik wrote:
I think that the Analytics team would prefer either:
1) detect source of edit in the URL
Or
2) have a hook activated after a successful edit and have the data send to
the pixel service
Having this data in a MySQL table poses a lot of challenges with
Max Semenik wrote:
On 15.11.2012, 4:06 Diederik wrote:
I think that the Analytics team would prefer either:
1) detect source of edit in the URL
Or
2) have a hook activated after a successful edit and have the data send to
the pixel service
Having this data in a MySQL table poses a lot of
On Nov 15, 2012, at 2:51 PM, MZMcBride z...@mzmcbride.com wrote:
Max Semenik wrote:
On 15.11.2012, 4:06 Diederik wrote:
I think that the Analytics team would prefer either:
1) detect source of edit in the URL
Or
2) have a hook activated after a successful edit and have the data send to
On Nov 15, 2012, at 2:51 PM, MZMcBride z...@mzmcbride.com wrote:
Right, which is why a revision tagging system exists in MediaWiki core
currently. If someone wanted to, for example, modify the MobileFrontend
extension to add a mobile tag to edits, it would be trivial to do. The
tagging
On 13/11/12 23:42, MZMcBride wrote:
Please stop top-posting. If you don't understand what that means, please
read https://wiki.toolserver.org/view/Mailing_list_etiquette.
As I posted at https://www.mediawiki.org/wiki/Talk:Revtagging, it's not
clear to me why the built-in revision tagging
On 2012-11-14, at 18:33, Platonides platoni...@gmail.com wrote:
On 13/11/12 23:42, MZMcBride wrote:
Please stop top-posting. If you don't understand what that means, please
read https://wiki.toolserver.org/view/Mailing_list_etiquette.
As I posted at
Dario has been proposing RevTagging to exactly address this need, see:
http://www.mediawiki.org/wiki/Revtagging
I really think we should put this on the roadmap for 2013 for Mediawiki, we
definitely need this more granular level of instrumentation for determining
the source of an edit.
Best
Diederik van Liere wrote:
Dario has been proposing RevTagging to exactly address this need, see:
https://www.mediawiki.org/wiki/Revtagging
I really think we should put this on the roadmap for 2013 for Mediawiki, we
definitely need this more granular level of instrumentation for determining
15 matches
Mail list logo