Keep in mind that ranking is based on quarterly sales, not real market share of phones out there. Regardless, Microsoft assumed 3rd Place in Q1 2013, when the Z10 was launched in Canada Feb. 5th and not in the US until Mar. 26th. The Q10, which has been selling much better than the Z10, didn't launch until May 1st in Canada, and June 5th/6th in the US. So, that market position doesn't really reflect the sales of BB10 phones, and for the most part weren't available yet in Q1 2013. Windows Phone 8 on the other hand was launched Oct. 29th, 2012 and had the benefit of actually being on sale for Q1 2013. Q2 2013 will paint a much better picture of how BB10 is doing, and it won't be until Q3 2013 where there will be a full quarter of where both new BB10 phones have been available for sale.
A couple of ways I've handled the spam situation in the past:
1. Base64-encode your form field names and decode them server-side prior to processing, or...
2. Create one-time use field names using md5 hashes of random numbers, map them to their true fields and store them in a session. Then process against those on the server side post-submit and clear the slate. (I used this method more often than not.)
3. Control the visibility of the honeypot field with CSS rather than "type=hidden".
Using #1 OR #2 in addition to #3 I've never had to use CAPTCHA nor human tests. A few paid spammers have come around from time to time, but since automated software isn't sophisticated enough to pick apart which field's which it either doesn't even try or it throws whatever it can at the fields, getting locked up in server-side validation.
Good points. In regards to CSS I think it's important to specify exactly what you mean though. I've seen this implemented dangerously where they simply position the form control off the wide (left:-4000px). This is vulnerable to browsers auto filling!
However hiding it completely with display:none should be safe and is what I think you mean.
In our case, just hiding it works fine. We can upgrade this to a CSS solution if we need to upgrade it though. The main point is if your doing something, you're ahead of the herd enough for spammers to generally leave you alone.
On #3, you want to ensure that the CSS is externalized and the class name non-obvious.
The amount of additional processing power it'd take to surmount this (and the other methods) from a spammer's end at scale would be incredibly prohibitive, and that's kind of the point.
+ Unexplained slowdowns from time to time. It's Alpha. It happens.
+ Will wipe your /media/internal directory for repartitioning. Back it up first.
Overall, I'm really impressed with the speed and result of the CM7 Team's effort although I find myself missing the multitasking/switching component of webOS (but not the slowness).
webos user here. App switching, do you mean the card system ? I think its terrible in comparison to holding down the home button on any android. Hold down the home button and it shows you all the recent apps.
There's pros and cons to both systems; it's merely a preference of mine after having a mixture of both Android and webOS devices for a couple of years now.
A lot of people don't know that you can move the cards around so that you can arrange two cards to be right next to each other, if you could speed up your workflow that way. I also don't like how you have to keep the home button pressed pon android, may be it is just my phone, but I would rather have an instant response to pressing home button rather than a timed one.
The Pre3 and the Touchpad are the right thing? They may have been the right thing in HP/Palm's eyes at the time, but they're dead now. Flatlined. Time to let go.
I hope the hardware engineers land on their feet at other companies, but I have a hard time believing for a moment that 525 folks comprised the Hardware division alone and nobody else was caught up in this. Developer Relations and webOS Development seems to have escaped the axe this time, but if I were working there I'd be looking over my shoulder more than a couple times a day.
Unless webOS gets a new lease on life through either a coherent strategy or new hardware licensees (preferably both) VERY soon, it's dead. They had one massive dry spell during the transition to HP that killed what market share and most of the developer mindshare they had; they're not going to make it through another one and have both consumers and developers give it yet another chance. All but the most dedicated webOS developers have already left as it is.
My prediction: Once the CM7 (Android Gingerbread) port hits, most of the people who bought the Touchpad at firesale will evaporate away from webOS along with whatever developer revenue was left to be had, dual-boot or not. webOS will end up an embedded OS for menu-driven appliances and other applications of their ilk, but never see another non-enterprise consumer mobile device again.
SHOUTcast's recent week-long on and off outage and subsequent crippling of their APIs is evidence enough of how seriously (or lack thereof) they take some of their properties.
Anecdotally, webOS devs, given the low threshold of competition and influx of new Touchpad owners, are doing pretty fantastic sales right now. Good for a quick return at least. Since HP's also being charitable and giving away 6-packs of apps for free (and paying the dev for each one at full regular 70% share), a couple of those devs picked found themselves 5-figures richer overnight. No idea how long they intend to keep doing it, but it seems ongoing for now.
Good platform for quick wins. Mid-term and longer, it'll largely depend on whether webOS finds new hardware with which to keep it alive.
I think that's the key; new hardware. If HP relies on the TouchPad for any more than 6 months, a year tops, they'll completely lose out on all their efforts. They need someone else to make better and still cheap hardware to keep people interested and buying. There are simply too many Android devices coming out, each one better than the last (forcing a price reduction of the last), to ride their current wave for any longer than that.
It's still very curious why they called an end to the hardware production BEFORE they had someone lined up to make new devices though.
