Just wanted to chime in before everyone starts talking about how google never sticks with their products, this is relatively unknown and better alternatives exist. There is no reason to keep this service up.
The one person I saw using it, at least when it was relatively new, was Matt Cutts to organize the questions asked for the daily Google Webmasters videos. Though those seemed to have died out almost a year ago, and they had moved to the Product Forums by then anyway.
It was used for a US presidential election debate in 2008 and 2012. But other than influencing the course of human history it has enjoyed little traction.
I have seen it only once. It was used for Obama's election campaign and they reached me with Google moderator. As it usually is, they did not even care, am I American citizen or not. Default country, what can I say.
Funny story: When you saw it, it was scheduled for shutdown. They had an announcement all planned and were ready to start turning it down, and then they delayed it so that Obama could use it for his campaign.
Google used this internally to manage questions at their all-hands meetings, letting the audience upvote good questions and avoid unimportant questions. Are there any other good solutions?
It's a real problem at conferences: many of the "questions" asked during the Q&A at public meetings are a waste of time, a chance to show off [1].
I found an example of Yik Yak used for this purpose [2]
Google Moderator was built before the smartphone era and noone was really working on it since.
We have been solving many of the issues of Google Moderator with http://www.sli.do. Even some Google offices have been using sli.do at their events instead of the moderator.
Thanks for your great comments Danny. What I meant is that the moderator was not really optimized for mobile as it was built before smartphones became dominant.
It was still a solid product, that just became a bit "old" as technology progressed. As mentioned in several comments here, better alternatives (incl sli.do) are now available.
"What I meant is that the moderator was not really optimized for mobile as it was built before smartphones became dominant."
Actually, we had a new mobile UI built in ~2010, and tested it at various conferences and in various other products.
The truth was the product wasn't going to do well outside of some niches, because the large content providers wanted something they could either control, or that was just more popular even if it wasn't a good fit (IE CNN/et al wanted facebook/twitter for their on-air shows, and were okay with hiring full time people to do curation)
So, yeah, mobile didn't really kill moderator, despite your claims.
I give credit to Google for publicly announcing the shutdown and doing so in advance. (Unlike amazon that just rips products out of the site. Can't go there to find movie times anymore!)
Moderator is relatively unheard of because it was created by one person as a 20% project, became popular internally, but less so externally. I ended up owning it for most of its life (it was a team of 3 people at one point)
Externally, we mainly used it for civics related stuff, though it saw some serious popularity in niche areas (like people using it to do youtube videos + questions), and was, in fact, in the accelerating growth phase when it was deprecated years ago, and we essentially cut off new external usage.
Because of how it was being used, despite being deprecated, it was kept running for many years to make sure people could find or build alternatives.
(Despite what people may think of Google here or there, at least all of my projects have had good shutdown plans :P)
> Despite what people may think of Google here or there, at least all of my projects have had good shutdown plans
Ironically, I think there is a connection between the first part and the last part: Google usually has well-announced shutdowns with good shutdown plans with long migration-out periods, which results in Google shutdowns spending a lot of time in the public eye (when they are first announced, when various milestones hit, and as they are in their final period), which magnifies the attention around Google product shutdowns and the impression of their significance.
OTOH, its also one of the reasons I'm very comfortable using Google products -- any product can get shutdown if its not doing well enough (and a company that won't voluntarily shutdown products that aren't contributing will find itself shutting down along with its products), but at least Google usually does a good job of handling shut downs.
> and was, in fact, in the accelerating growth phase when it was deprecated years ago, and we essentially cut off new external usage.
Would you mind elaborating why it was shut down if it had accelerating usage? seems like a good reason to keep it going instead of shutting it down to the public...
I saw a glimpse of it only during a GDC video on YouTube. This is exactly what I need for giving lectures and talks. Infact, I have an architectural sketch and UI workflow notes for this exact application. Will it be open sourced?
It's not sanely possible to open source.
All the interesting parts it depends on are in internal backend infrastructure.
The UI is written in a really old version of GWT.
Also, Moderator actually started out as an early appengine app written in python, then was ported to normal Java.
If you want the algorithms, they are mostly already public.
Given the way UI/etc frameworks are today, it would take you about 1000x less time to write moderator again from scratch than it would to try to massage an open source version into working.
I was mostly interested for pedagogical reasons, not actual reuse. I'll probably just try to simulate a session with it myself if I can still signup, and record a screencast. Be my own test user for a UX experiment.
Moderator's code would probably scare you :)
It was written in an era where optimization really matter.
Not that it's written in assembler or anything, but it minimizes the amount of reads/writes it makes to the datastore through interesting means at times.
It is unlikely, for example, you would ever be able to discern the voting and question scheduling algorithms from reading the source code, despite the fact that i could write them for you in about 1-2 pages of java.
44 comments
[ 4.0 ms ] story [ 40.9 ms ] threadJust wanted to chime in before everyone starts talking about how google never sticks with their products, this is relatively unknown and better alternatives exist. There is no reason to keep this service up.
One of the moderator series is at: https://www.google.com/moderator/?hl=ar#15/e=581e0&t=581e0.4...
Note that moderator is not only available in a ton of languages, it can do auto-translation between all language pairs google translate supports.
It's a real problem at conferences: many of the "questions" asked during the Q&A at public meetings are a waste of time, a chance to show off [1].
I found an example of Yik Yak used for this purpose [2]
[1] http://vooza.com/videos/conference-q-and-a/
[2] http://www.theconglomerate.org/2015/03/i-have-seen-the-futur...
[1] http://wisembly.com/fr/
We have been solving many of the issues of Google Moderator with http://www.sli.do. Even some Google offices have been using sli.do at their events instead of the moderator.
This is not really accurate, though i guess it depends on what you consider the smartphone era.
It was still a solid product, that just became a bit "old" as technology progressed. As mentioned in several comments here, better alternatives (incl sli.do) are now available.
Actually, we had a new mobile UI built in ~2010, and tested it at various conferences and in various other products.
The truth was the product wasn't going to do well outside of some niches, because the large content providers wanted something they could either control, or that was just more popular even if it wasn't a good fit (IE CNN/et al wanted facebook/twitter for their on-air shows, and were okay with hiring full time people to do curation)
So, yeah, mobile didn't really kill moderator, despite your claims.
I just heard some of our clients that were using Moderator before that they switched because of the mobile UI. Was it ever available for public?
Externally, we mainly used it for civics related stuff, though it saw some serious popularity in niche areas (like people using it to do youtube videos + questions), and was, in fact, in the accelerating growth phase when it was deprecated years ago, and we essentially cut off new external usage.
Because of how it was being used, despite being deprecated, it was kept running for many years to make sure people could find or build alternatives.
(Despite what people may think of Google here or there, at least all of my projects have had good shutdown plans :P)
Ironically, I think there is a connection between the first part and the last part: Google usually has well-announced shutdowns with good shutdown plans with long migration-out periods, which results in Google shutdowns spending a lot of time in the public eye (when they are first announced, when various milestones hit, and as they are in their final period), which magnifies the attention around Google product shutdowns and the impression of their significance.
OTOH, its also one of the reasons I'm very comfortable using Google products -- any product can get shutdown if its not doing well enough (and a company that won't voluntarily shutdown products that aren't contributing will find itself shutting down along with its products), but at least Google usually does a good job of handling shut downs.
Would you mind elaborating why it was shut down if it had accelerating usage? seems like a good reason to keep it going instead of shutting it down to the public...
Also, Moderator actually started out as an early appengine app written in python, then was ported to normal Java.
If you want the algorithms, they are mostly already public.
Given the way UI/etc frameworks are today, it would take you about 1000x less time to write moderator again from scratch than it would to try to massage an open source version into working.
I was mostly interested for pedagogical reasons, not actual reuse. I'll probably just try to simulate a session with it myself if I can still signup, and record a screencast. Be my own test user for a UX experiment.
It is unlikely, for example, you would ever be able to discern the voting and question scheduling algorithms from reading the source code, despite the fact that i could write them for you in about 1-2 pages of java.
I think mobile definitely played a key role, as the old UI didn't work there at all.