2,193 karma · joined August 12, 2010
at symbicode.com, charlie
University of Waterloo Soft Eng Grad
I work somewhere
http://hnofficehours.com/profile/charlief/
If you wanted, I could give you an MCDA showing cocaine is more harmful to society just by tweaking a few criteria a tiny bit. I could add a practicality criteria in that drinking alcohol is a cultural practice in many places, or I can separate two forms of drinking, responsible drinking and irresponsible drinking. There are so many ways to slice it that if you don't have specific decisions you're evaluating against, the whole analysis is useless.
That's not to say the value of the product doesn't lie in the keyboard research they did as well. Anyone can design a cool widget, but the idea to recognize a very innovative solution to mobile typing and perfecting it (figure-8 drawing is a great touch, assuming it works well on many phrases) is 8pen's strongest point. I just hope there is enough flexibility after the patent is issued so I or someone else can write a generalized form of this widget.
I feel the keyboard domain doesn't make use of hierarchy properly though. Let's say the 8pen keyboard divides the keys into octants. Each octant does not have a collection of related things. The letters I D G Z are not related in any way, yet they are all arrived to by first moving up and rotating right.
To illustrate a better use of the hierarchy, I'll divide the thing into quadrants instead of octants. Consider a widget to edit font. The top quadrant could be font family, the left quadrant could be colour, the bottom is size, and the right is style (bold, italic etc). Using this, if I wanted large text, I would move to the size quadrant and rotate clockwise to select a large size. Here you are taking advantage of the hierarchy and ranking such a widget could provide.
The font example is really really lame, but the GUI they present has a lot of potential. You can also divide the wheel into an arbitrary number of sections. There are tons of application domains that would work for a component like this. I just hope that 8pen isn't hell-bent only on giving us a keyboard.
Here is the original paper:
http://www.crimeandjustice.org.uk/opus1714/Estimating_drug_h...
http://en.wikipedia.org/wiki/Multi-criteria_decision_analysi...
Here's my particular case. I've been a subscriber since the third issue and 90% of the magazine content I've seen on HN, but the presentation and centralization of the best is of wonderful value. They really do a nice job on the design front. The issues also function like a library of cool articles you can show to a friend or colleague and say "Here's HN in a box, at least one particular filtering of it." I have brought at least a couple contributors to Hacker News, just because they read through an issue of Hacker Monthly.
http://www.asymco.com/2010/09/21/can-android-change-the-prof...
I am proposing to change the comments page linked at the top-level menu to a ranking scheme similar to the one that ranks threads in a submission's comments page, but favouring recently posted 1-vote comments less.
Comments are more interesting than submissions in many cases. Such a page would support bottom-up (comment to submission) navigation on the site better. I know there are some features for bottom-up navigation like the on: feature on the comments page, but isn't very useful unless the comments are good. This would allow me to explore articles I would have never found to be interesting looking at the main page but when framed in the right context with an excellent comment would be very interesting.
The usage statistics of the top-level threads and comments links could support or reject a rethinking of the functionality that those pages provide.
It isn't even a question about character here because if these people were concerned about money before everything else, many of the smartest Silicon Valley people could have had a job on Wall Street a long time ago. On Wall Street, almost 100% of the time you'll be very well off (remember how much GDP goes through that street). Wall Street will take brains anytime. If not Wall Street, FB IPO expectations haven't changed significantly in a year, these people would have moved over ages ago if they wanted a big equity cut.
There is only so much liquidity to go around with 1700+ employees and a marginally liquid market on secondmarket. For me, second market changes the game a bit because the error in valuation is potentially a lot smaller (there was a very good discussion on FB over here http://news.ycombinator.com/item?id=1719975). Either way, I wonder the size of the equity packages involved. Even if they are large, someone like Lars is very well off and spent most of his whole life building things so I don't think he is a jump to FB for the IPO kind of guy. Choosing where to work, when to work is a complex decision and not indicative of any character most of the time.
http://delimiter.com.au/2010/10/30/google-exodus-lars-rasmus...
1. http://code.google.com/p/wave-protocol/ http://www.waveprotocol.org/
2. Wave Protocol summit is in November http://googlewavedev.blogspot.com/2010/10/wave-protocol-summ...
3. Wave in a Box (server + client) (vs Outlook in enterprises?) A very interesting adoption experiment, and if they separate it enough from the cloud, it will be a straight-forward germination in Outlook's market down the road. http://googlewavedev.blogspot.com/2010/09/wave-open-source-n...
4. If they're doing this much in public, you can bet there are a few integration projects at home as well.
http://googlewavedev.blogspot.com/ http://googlewave.blogspot.com/ for Wave updates, definitely isn't dead I would say.
What we know:
a. Lars and his brother Jens have been a team or working colleagues for at least a while (maybe since 1999)[2]. They co-founded Where 2 Technologies in 2003 which got acquired by Google in 2004 and became the core for Google Maps.
b. A big proportion of the Google Wave complaints surrounded the UX, both for end-users and devs.
c. Lars on Wave "On the team after a year and a half, when we started using it, it still took us a while on how to use it... how to be more productive using it." [3] The whole video is a good watch for those interested, and so you get the context of the quote as well. We can gather that Google Wave germinated from a very organic process including the UX.
d. Google's Wave in a Box project will include a subset of the functionality (simplification) of Google Wave. "This (Wave in a Box) project will not have the full functionality of Google Wave as you know it today. However, we intend to give developers and enterprising users an opportunity to run wave servers and host waves on their own hardware"[1]
What I think but really do not know and I suck at writing:
* With Lars leaving, it adds liquidity to the possibility of further change on Google Wave development or integration. It makes it pretty certain that the leadership on the project, Wave in a Box, or subsequent integration projects will at least be tweaked. This will be further confirmed if Jens leaves as well (a), but we have no idea at this point if he will.
* Losing Lars maybe Jens maybe others and they will lose a big whack of their engineering leadership on Wave, so you can expect further developments on the core technology to slow tremendously. What's left is the community building, repackaging, marketing, open-source, maybe some hope in monetization, some more experimentation, package and publish extensible protocols[4], maybe trying an adoption experiment (Wave in a Box, maybe enterprises will use it!!!, let's fight Outlook), maybe some hope in leveraging the existing technologies with integration, etc. Google Wave's team is probably focused just on that, and the head caveat on those tasks is the UX. They'll probably bring in or already have some outstanding UX folks. Maybe the leadership on that front wasn't there from the start, but we don't know as it was created in a very organic fashion (c).
* Google is a master at integration in most cases. Just look back at all the acquisitions that went really well, and on top of that, Wave is using most of the Google ecosystem already. While the Wave in a Box project continues, you can probably expect some Google Wave functionality and technology to pop up here and there. I wouldn't be surprised if it makes an incremental and subtle appearance in some of GMail's functionality in the way Buzz has, but we don't know.
* Most of us would agree that Google Wave won't be coming back in its current form because the tarnished reputation. Such an event is more unlikely than finding a black swan, more like finding a transparent swan who can do calculus, but even finding one of those can happen. It will be interesting to see what happens with Wave in a Box, Google Wave Federation Protocol, and Google's ecosystem, hopefully good things.
[1] http://googlewavedev.blogspot.com/2010/09/wave-open-source-n...
[2] http://au.linkedin.com/pub/lars-rasmussen/5/519/16 http://au.linkedin.com/pub/jens-eilstrup-rasmussen/5/192/890
As you mention some other ways are not impossible, but have serious problems. I agree, but at the very least, I think the status quo is not optimos. If you are starting up an affiliate scheme, it would be interesting to explore all options even ones that seem more complex or unconventional, because frankly, the ultimate black magic is a spontaneous killing of a business with no warning signs or even the converse. Either eBay wins (by getting some extremely high-LVT traffic) or the affiliate wins then loses (by getting killed). There has to be a way to a middleground.
EDIT: changed official to unofficial, thanks riklomas
I can see what the practicality might be like, but it seems much simpler and fair than estimating LTV and cutting off affiliates if you were incorrect.
1. In the hypothetical situation you provided, it seems that if your CPA is based on trial signups, the cost structure doesn't scale with the demand and value you get from using the SEO charging per trial. If you generate revenue on a conversion, why do you have a CPA based on a trial registration? Doesn't eBay pay per conversion? Perhaps this is a common practice. Can you renegotiate to a more reasonable cost structure, maybe get it right from the start or allow some flexibility if you and the SEO aren't aware of how the costs will play out?
2. If eBay is unhappy about the LTV per CPA, why not agree on a cost structure that more readily scales with varying LTV rather than blame the affiliate for not meeting a particular threshold?
3. There is an opportunity cost with firing an affiliate due to poor traffic quality for a month rather than keeping them consistently there. You might fire your SEO for one month's bad performance in a heavy-handed fashion, but what if Christmas, not just any old Christmas, turns out to be a legendary one. Bingocardcreator is the new hot fad for Christmas family games night and conversion rates are through the roof. If there was a cost structure that hedges odd months like October, (3-month moving average of CPA for example) your SEO would be around consistently, ready for a key opportunity.
I see parallels here to most successful farmers that use futures to hedge their fuel costs and stabilize their revenue in varying weather and environmental conditions. It won't save you from an SEO not being economical, but it will make the costs less uncertain.
4. Helping an SEO affiliate optimize on an aspect that may or may not be under their control may be a big task, but already, providing a conversion table like you did is probably more than what was probably provided by eBay.
5. It is not economical to work with people to optimize their sites to hopefully be sending quality traffic again, since that is hard, non-obvious Sites don't have to do a lot, just be transparent and manage expectations above the bare minimum. Affiliates like everyone else don't like uncertainty mixed into their return on investment. Even if the nature is an uncertain one, you can still manage expectations to keep that fact transparent, and keep a cost structure flexible but clear enough to support.
6. might be against the interests or intentions of the site owner, and consumes resources which would be better spent optimizing the customer's own sites. Brilliant insight, this is probably a factor as well, but I care to believe that eBay still handled this case in a sloppy fashion.
I think this is not only a submission identity problem, it is also a ranking problem as many great submissions are missed that would easily make it to top 20 if they had the seed votes needed. (A parallel to startups not getting the seed funding they need :) ?) That's not to say it is a big problem, as HN has quality and in almost every case has the best on the front page.
Chuck Lorre (born October 18, 1952) is a writer, director, producer and composer who has created many American sitcoms, including Grace Under Fire, Cybill, Dharma & Greg, Two and a Half Men, and The Big Bang Theory. Lorre also serves as executive producer of the sitcom Mike & Molly which premiered on CBS in September 2010.
* I doubt offers will be as plentiful as Show, Tell, Ask.
* Offers also expire where Show, Tell and Ask are relevant for a longer periods of time. Mixing Asks, Tells, Shows, and Offers + others together allow irrelevant or aging submissions to slide, making a more useful "offers page". It makes offers compete in some sort of page ranking, instead of a usually unchanging page.
* If I want to see a recent, hot Offer, I'll see it on the top page. If I want to see medium-aged offers, by mixing them in with asks, I'll see other interesting content as well. It is a more useful offers page. Making a separate offers page will have me polling a page that doesn't change usually.
* If I want to see very old offers, I'll use searchyc, google, or check jacques' blog. Chances are I won't be doing this that often because very old offers will be expired.
edit: totally implemented, probably before I posted even a long time ago
In that case, with an offers list on the next invocation and a very functional asks link, I don't think an extra link on the bar is necessary