I nearly pulled my developer engagement rant from the publish queue yesterday, since Aral did a much more eloquent job of describing the problems of working with developers. But I'd been working on it for quite some time, basically jotting down frustrations and annoyances after each developer event I went to. A colleague convinced me there were enough points of differentiation to make it worth publishing as well. So it's finally hit the wires.
Still - I highly recommend you go read Aral's post:
Let me use the tools and technologies I already know instead of forcing me to learn a whole new set. Give me some open web technologies to play with and I might just stay the night.
Excellent.
Incidentally, it's not all bad - one event I went to had two highly passionate and entertaining speakers (to quote someone: "their talk was fucking ace"). Another event saw me whipping up a widget using standards-based technologies (XML, JSON, HTML, CSS) and easily deploying over bluetooth. But there's still an uphill struggle most of the time, even though it's not rocket science to get this right.
]]>1. Call a spade a spade
Before I even get involved, I want to know: what's in it for me, and why should I care. It's amazing how many organisations talk about addressable market or target technologies or available devices. Blah blah blah. I want to know: what's the future of your platform, how quickly can I be productive, and how can I get my apps in the hands of users. Seriously. Cut the fluff, cut the marketing, you're talking to a technical person here. We detect bullshit for a living. So: tell us what we get and when we get it. Clearly. Concisely. It's not difficult! In return, we might buy into your platform, and then you'll have an army of evangelists more useful than a thousand glossy corporate brochures.
2. Captain Awesome
There's a commonly-held myth that everyone develops for the iPhone because of the fantastic tools, or the fantastic documentation, or the promise of becoming an App Store Millionaire, or because the Reality Distortion Field made them do it. Well, they may all play a part, but the number one reason is this: a compelling device that people want to use. Compared to all that came before it, the iPhone was all about usability - even in the early editions of the operating system. If you don't have a compelling, awesome device, please stop asking me to develop for it.
3. Hide and Seek
So you have a compelling device. You want me to invest in your platform. You push me to your website. But then you're not prepared to let me see the details of that platform - technical documentation, wiki pages, forum searches - without forcing me to register. Why should I have to give you all my personal details when I'm not even sure your platform is viable or of interest until I've had a chance to review those materials? How are us developers supposed to share hints, tips, and pointers to useful information if it's all behind a registration wall? What's so top secret about those device APIs that you can't make them public?
4. Please Hold
The rest of the internet has accessibility-crushing CAPTCHAs and automated email verification ("click the link to confirm your account"). But your site is special, and so you give each and every sign-up request that personal bit of attention. You really want developers for your platform, which is why you make me wait 72 hours before I can login and download the material I seek. But honestly, a cooling-off period is good. You don't want me to hastily rush in and adopt your platform and start being productive. I need to take some time to reflect on my decision - time I can spend evaluating your competition. Just don't expect me to be back after those 72 hours, mmmk?
5. No really, who are you?
Please enter your login and password. My login might be my email address. It might be a username you asked me to create. It might be a randomly generated username from your firstname.lastname.integer mashomatic. I will never know, and you will provide no hint. Oh - and as a special bonus, I need a separate username and password for the forums, the download site, and the wiki. Because single sign-on is, like, so last century.
In fairness problems 3-5 are common to all sorts of websites, not just for developers. But you'd think if they got 1-5 nailed, it would be all plain sailing here on in. Dream on! As if that wasn't bad enough …
6. README.txt
I can almost guarantee your developer kit is not available for my chosen developer environment. (Hey, Linus, we'd love you to build cool stuff with our Windows SDK! Steve, old pal, try this Eclipse plugin! Balmer, dude, you'll really dig this XCode tutorial!) And if it is … what are the odds of a simple installation? If I want to develop for three different platforms, all of whom use Eclipse for their SDK? Why yes, I would like to install three personalised copies of Eclipse, thank you very much. That sounds tremendously efficient and much smarter than using a plugin ecosystem.
7. The dotted line
Please read the following license agreement carefully:
Use of this SDK is subject to the terms and conditions of our SDK license agreement. This agreement is between you ("YOU") and big faceless corporation ("THE MAN"), a company incorporated under laws in a country far far away. By accepting these terms you give us all rights to your code, to your firstborn child, to 10% of your annual income in perpetuity and furthermore you acknowledge full responsibility and warranty and fitness for purpose of your application. You will be liable for the sum of one billion dollars ($1000000000) and forfeit any right to talk about THE MAN without express consent for ever and ever, amen. Please indicate your acceptance of this agreement by depositing a litre of blood here: [ x ]
You want me to develop for your platform, and you start the relationship with 35 pages of legalese? Seriously?
8. Goodbye Cruel World
The quickest problem to describe, the hardest to solve. How long does it take from access to the website to being productive and seeing "Hello World" in an emulator? How much documentation do I need to read? Is everything self-evident, following common methodologies and best practices? Does it all fall into a typical developer workflow?
9. Deploy.
Assuming I got my "Hello World" working, how easy can I get it on my real live actual phone? My neighbour's phone? Share it with everyone in my office and gather useful feedback from them? Beware: if your answer is "send them to the app store", my neighbours and colleagues will all demand you give them bundles of cash to spend there.
10. Unconference
So, you told me why I should write for your platform. You have a compelling device. You made all your content readily available and accessible. You had a speedy sign-up, and let me pick sensible login details. Your tools were lightweight and fitted with my normal workflow. Your licensing terms were reasonable. I could become productive quickly, and get my app on several phones without too much pain. Now I want to take the next step, and meet the others who are developing for your platform, to become an active member of the ecosystem. I want meetings, get-togethers, hackathons, and conferences. You've kindly arranged all of these, but … do I get to talk technical, or will I be in a room full of suits? Will it all be glitz, glamour, vapourware roadmap and marketing, or will you concentrate on nuts and bolts and real world problems? Is there all the power and wireless I could ever need? Do you have ALL your developer materials handy (like on a USB stick) to save me waiting a day for the download? Can I run off with one of your devices, or some developer-specific test hardware? Will you have passionate spokespeople who are engaged in what they talk about, or marketing drones wheeling out the corporate message? Will it be Death by PowerPoint, or Death by Pizza?
]]>Whilst I've generally run Debian on servers with rock-solid performance and stability, on a personal server I've been experimenting with Ubuntu. I thought it was worth reporting that I smoothly upgraded that server tonight not just one release, but two releases, from 8.04 to 8.10 to 9.04. It required a couple of restarts - which generally is not ideal but doesn't matter much in a non-critical context. But that was all - and in less than an hour, I've got an up-to-date machine.
And yes, this is a long-winded way of saying "testing, testing, 1-2-3, is this thing working?"
]]>Google Chrome OS is an open source, lightweight operating system that will initially be targeted at netbooks. Later this year we will open-source its code, and netbooks running Google Chrome OS will be available for consumers in the second half of 2010. Because we're already talking to partners about the project, and we'll soon be working with the open source community, we wanted to share our vision now so everyone understands what we are trying to achieve.
Firstly, this is great news. We already have moblin , maemo, and various netbook remixes, but any big company deciding to invest in building open source platforms is likely to stimulate the ecosystem, provide competition that leads to innovation, and bring valuable eyeballs and marketing to the open source world.
Unfortunately, Google have done it again - started down the path to another "throw it over the wall" open source project, missing out on the key benefits of the open development model and skipping that most important step of all - building a community from inception to ensure the community develops and matures in line with the code.
That announcement quote again, with some emphasis added:
Google Chrome OS is an open source, lightweight operating system that will initially be targeted at netbooks. Later this year we will open-source its code, and netbooks running Google Chrome OS will be available for consumers in the second half of 2010. Because we're already talking to partners about the project, and we'll soon be working with the open source community, we wanted to share our vision now so everyone understands what we are trying to achieve.
Now, I know many people at Google, I know they have a lot of smart folk there, and I know that some parts of the organisation really understand what open source is and how it works. But how is it that there is this continuous disconnect at a fundamental level when it comes to new initiatives? We saw it with Android and we saw it with Chrome: Google do the bulk of the work behind closed doors, then dump the code out there and simply expect everyone to pick it up and run with it. If you're moving to open from a proprietary codebase, such as in Symbian's case, this approach is understandable. But if you're starting from scratch, it makes no sense at all.
Here's the thing. Either you believe in the open source model - and the open development that goes with it - or you're a cynical company using it for marketing and to leverage some free bug fixes. Which is it to be, Google? Are you going to start the conversation around code from inception, giving every motivated developer an opportunity to collaborate and contribute, accepting not just the rewards of community development but also the risks? Or are you going to do your own thing yet again, and hope no-one calls you on it?
]]>Unfortunately, there's a few bugs that cause problems when installing to an SD card, and it took a bit of time searching around to find the right solutions. I found some threads on the moblin-dev mailing list, but thought it would be useful to pull everything into one coherent guide. So here's what I did.
Firstly, create a bootable USB image. The detailed moblin live image instructions contain an error for Mac users:
sudo dd if=/path/to/downloaded.img of=/dev/diskN bs=1m
should read:
sudo dd if=/path/to/downloaded.img of=/dev/diskN bs=1024
When you've written the image to the USB key, you need to boot from the USB key. Press ESC as the machine starts up to get the boot device selection menu. When the Moblin menu appears, select the "Boot and Install" option.
When the installer starts, work through to the section for selecting the install location "Select the drive(s) to use for this installation", and select your SD card device. For me, this shows up as "sdd Single Flash Reader". Also select it as the location for the boot sector, in the "What drive you you like to boot this installation from?" option.
When the installation is complete, allow it to reboot, but again select the USB key to boot from as we need to apply some fixes to our install before it will work. At the Moblin boot menu, select "Boot" to run the live image off the USB key.
When Moblin starts, go to applications and select terminal. You now need to mount the recently installed partition and edit a few files there. Firstly, become root by typing su - (the password is moblin), and then type:
mkdir /mnt/sd
mount /dev/sdd1 /mnt/sd
cd /mnt/sd
vim etc/fstab
This will allow you to edit the location of the partitions to mount. Change any references to sdd in this file to sdc (since when we boot without the USB key, the SD card will be in a different location). There should be two entries - one for the / partition and one for the swap partition.
Next, edit the grub boot configuration (vim etc/grub.conf) and again change sdd to sdc, and also add rootdelay=10 to the kernel line.
Finally, a quick hack to make the boot process pause before checking the disks. vim etc/rc.sysinit and search for the fsckoptions section, and just before that (just after the hostname line) add: sleep 2
You should now be ok to reboot, remove the USB stick, and select your SD card as the drive to boot from.
It works, and it's possible to use the system, but beware that the SD card introduces a fair degree of lag as it is not the fastest device to read from and write to (possibly restricted by the port in the EeePC rather than the card itself).
]]>In my defense, it's been a busy time. Lots to do at work, and also lots of rental apartment hunting, followed by moving, followed by sorting out the infrastructure in the new place. On the subject of moving ....
I'm somewhat wary of drawing attention to my previous diatribe on London Estate Agents, as this year I realised I was cheerfully giving out an email address that led them straight to an incentive to screw up my move (london_estate_agents_are_scum@andrewsavory.com? estate_agents_die_die_die@andrewsavory.com?). But some parts of the recent experience I had just beg to be documented. Next year I'll have to register estateagentsaretotallywonderfulandterrificallyspecial.com, or some abbreviation thereof. Suggestions welcomed.
Last year, I saw an awful lot of properties as I narrowed down the area to live in and the exact requirements. Typically, three or four places a night. This year, I was lucky if I saw three or four places a week. The market is very strange at the moment - everyone currently renting seems to be staying put, and there's very few new properties coming on to the rental market as buy-to-let sales collapse almost as fast as the banks' profits. Sadly, any drop in prices due to the recession seems to be as frequently offset by the rise in prices due to lack of supply.
Anyway, from the ones that we did see, some highlights include:
Anyway. New place found, after much stress, and some more colourful stories of London Agents to discuss over beers.
We're writing to let you know about a pricing change to Google Apps Premier Edition.
Google reviews prices on a quarterly basis, and the price of Google Apps Premier ($50 and £25 for UK customers) has remained unchanged for the last two years. Effective immediately, the price will change from £25 per user, per year to £33 per user, per year for all customers transacting in GBP. At renewal, you will be charged the new price of £33 per user, per year. The price of Google Apps Premier for USD and EUR will remain at the same price of $50 and €40 respectively, the current increase for GBP reflects the recent unprecedented changes in the dollar versus pound exchange rate.
We believe that Google Apps Premier continues to represent affordable innovation and excellent value for money for businesses of all sizes, compared to traditional desktop solutions. We are committed to continuous innovation and helping businesses like yours benefit from seamless introduction of new features such as Google Video for business, Google Sites and Google voice and video chat. We're constantly working to build the most innovative products for our customers and look forward to introducing even more functionality to Google Apps Premier.
If you have any questions regarding this update, please don't hesitate to contact us through the support tab in your Google Apps control panel.
Thank you for using Google Apps Premier.
Ouch. Do I scream and shout at Google, or at the UK Government for screwing up our country's finances so badly that the relative value of sterling has dropped so much?
Particularly galling is the "effective immediately" line. No discussion, no forewarning.
It would be interesting to know how many UK datacentres Google have, and how much money they've saved on their UK operations as a whole when paying for them with a strong dollar.
If I'd seen a corresponding increase in the responsiveness of Google Apps Premier, I wouldn't be so annoyed, but the truth is the service has been getting progressively worse over the last few months.
Finally: why is there no global currency unit for this sort of thing?
Grumble grumble. I'll crawl back under my rock now.
]]>
A bunch of LiMo Foundation news is breaking this week in the run-up to Mobile World Congress, which hits Barcelona next week.
Here's the ones I've spotted on the wire and the website so far:
Vodafone signs Linux deal with U.S. firm Azingo
Telefonica, other telcos to launch Linux phones
That makes five operators backing LiMo, the others being Vodafone, Orange, NTT DoCoMo, SK Telecom, and Verizon Wireless. See also Telefonica and SK Telecom join LiMo Foundation Board of Directors, Global Mobile Operators confirm commitment to widely deploy LiMo handsets. 1 billion subscribers is a BIG number.
LiMo Foundation gets ready for next-generation platform
Release 2 is coming. See also LiMo Foundation announces key updates to LiMo Platform.
LiMo Foundation endorses OMTP BONDI specification to bring Web 2.0 applications to LiMo handsets
BONDI could be hugely significant in the mobile space, more on that later.
]]>Meh, where's the 'preview' button gone?
Seems strange that years after I first started using ecto, nothing better has come along to challenge it in the world of blogging on the Mac. What do others use / recommend?
]]>Hippo released CMS 7, a long-awaited update of their excellent enterprise document and content management solution, touting separation of concerns, an all-new Apache Wicket-based GUI and a super Apache Jackrabbit repository to replace the old and retired Apache Slide WebDAV repo. If you need a CMS, you know who to call.
MobileMe is still a bit of a dog's dinner. I had to sit through two painful live support sessions on Apple's website in order to get my password reset correctly. For the record, using iforgot.apple.com seemed to have issues and to be out of sync with MobileMe, and confusion abounds since an Apple ID is not a MobileMe ID. Genius. But: calendar, bookmark, and keychain syncing all seem to be working smoothly and proving useful.
If you're trying to get Yojimbo to synchronise via MobileMe, make sure you've entered a license number on both machines you're syncing and not using the free trial on one of them. It took me a couple of days of occasional googling and finally simple trial and error to track that one down. It's not documented anywhere that I could find. The irony is I was trying to do the sync so I could get hold of my Yojimbo license numbers on the new machine...
My EeePC was doing sterling work as a MiniMacbook, apart from a slight hiccup with driving a projector today. I'm still not sure why that didn't work, since I can cheerfully power a large external LCD panel with it. Other than that, I've been cheerfully using it for mail, news, twitter, powerpoint, and all the other day-to-day requirements of work, rest and play.
I say "was doing". Approximately since upgrading Quicktime, I've been getting kernel panics instead of suspends occasionally. Tonight I re-installed the kernel extensions to see if it helped - and now I have a blue screen of death, pre-login screen. Ho hum. Reinstall? Rescue boot? Who knows. One thing I do know is I've been enjoying the significantly lighter rucksack on the long walk to the office, so I'll be loath to go back to the Macbook Pro.
Right, where's my Leopard CD .... ?
Technorati Tags: apache, appstore, asus, b0rkb0rkb0rk, cloud, computing, eee pc, failure, java, macosx, open source, osx, software, workaround
]]>
Toward the end of last week, Nokia made the announcement that they would add LGPL as a license option to the QT toolkit.
QT is a highly-polished, well documented modern GUI toolkit - some consider it to be the best GUI toolkit for UNIX compatible systems.
It's well-known for being used in the KDE desktop environment, the biggest competitor to the GNOME / GTK desktop. There was some controversy in the past surrounding KDE's use of QT, as it was not originally available under any open source license. QT 2.2 added the GPL to available licenses, and while this was good for free software projects, the requirements of GPL compliance still limited it's widespread adoption.
Nokia will finally release the next major version of QT (4.5) under the LGPL as well as existing GPL/commercial licenses. Once QT is LGPL it will put them on the same licensing footing as Gnome's GTK.
General response seems to be along the lines of "this is huge!", "no more $5000 licenses!", "excited!", "huge win for cross-platform development", "sounds like Nokia is keen on pushing QT as defacto standard GUI toolkit", "the change is needed to lower the cost barrier compared to other mobile platforms".
But what's the real impact of this change? Will we see developers dropping GTK in favour of QT? Will people flock in droves to the Symbian platform with QT on top? Is KDE going to become the de facto desktop?
No. My guess is "not much change, business as usual". Alex has some interesting thoughts on it as well, as I knew he would when I asked him :-)
I think in the short term, we will see a significant amount of noise about this. It's particularly relevant in the mobile space since Nokia announced the port of QT to Symbian S60 in October. In some ways, this move was innevitable given Nokia's acquisition of Trolltech (the company behind QT, now called Qt Software), and the establishment of the Symbian Foundation.
I think Nokia are hoping they will see a few more developers adopt Symbian as a result of this move, and it makes a nice soundbite and story - but my suspicion is that a toolkit on it's own is not sufficient (the rest of the platform needs to be familiar and friendly too).
Given the momentum, ecosystem and companies around Gnome (Ubuntu, RedHat, Google, Sun, ...) I don't see Gnome / GTK being visibly impacted any time soon. There's an outside chance the next major version of GTK will be ditched in favour of QT, but I suspect inertia and fear of capitulation to Nokia will prevent this happening.
Finally - Alex wonders why we're tied so thoroughly to widget toolkits. I suspect this will change. WebKit and WebOS initiatives may make GTK and QT much less significant than it used to be, as we see native apps marginalised in favour of HTML++ for most application developers. Not least because it's only going to get harder to find "low level" developers (with Java being taught instead of C/C++ in schools and universities), and internet apps have the "cool" factor without (allegedly) needing so much of the blood, sweat and tears.
There will still be a need for someone to write the toolkits like GTK and QT - after all, how will web browsers display themselves? - but the apps on top just won't care. The big deal here is what ships in mobile application stores in the future. With the Apple iPhone app store seeing 15,000 apps and 500m downloads (and Apple redefined drag 'n' drop interface building), and Palm Pre App Catalog effectively offering a web widget store, our perception of what's in an application and what's needed to run one is going to go through some subtle but dramatic changes over the next year or so.
See also:
Technorati Tags: apple, appstore, debate, floss, gnome, iphone, kde, lgpl, linux, mobile, nokia, open source, proprietary, licensing, software, ubuntu
]]>What I hadn't counted on was the terrible problems I'd have with domestic infrastructure. Two such examples follow.
Despite living approximately one mile away from BBC Television Centre on Wood Lane, rather ironically I was unable to get a decent television signal. The Freeview website even reported that Hammersmith was not due to get a signal until 2011 or 2012, though it has since been updated to report availability. Fortunately, after complaints to the landlord, the roof aerial was rectified, and TV is now a possibility, though not with portable aerials such as the one on my TV Mini.
The second problem (and the real reason for my thinly-disguised morning rant) was the inability to get a decent broadband connection. I'd been drooling over the prospect of 24 meg broadband, but it turned out that my local exchange was full and the only provider able to offer broadband was, surprise surprise, BT Broadband. It's a bit dubious when the only provider able to offer connectivity over a forcibly derestricted monopoly line is the retail arm of said monopoly.
BT was a less than delightful option: they have been known to cap their bandwidth, to censor web access, and to offer hideous service. I swore many years ago I'd never go back to them, but faced with the option of BT or no internet, I decided to put my principles in a box in the cupboard, next to the BT Home Hub.
It turns out I should have listened to my instincts, and opted for a 3G data card, two yoghurt pots and a piece of string, a yearly subscription to WiFi in the local pub, or some other contraption. Since mid-December I've been fighting with BT over noise on the line, and for the last week I've been fighting to get a workable internet connection. Despite having a line rated for 4mb/s, I'm lucky if I can get 10k/s throughput.
So far I've had four engineers come out. Two have claimed to have "tidied up the wiring in the exchange" (how messy was it??!?), one has been unable to find any fault, and the most recent actually appeared to have done a good job, testing everything thoroughly and working inside and outside the house until the line was clear as a bell - until BT Broadband started running their tests again, once the engineer had left. According to one of the engineers, BT sold off the local exchange (West Kensington), and just before Christmas they moved everyone over to another exchange, a kilometre or so further away, with "big fat cables to try and limit the impact of the increased distance". I wonder if the money made from the sale of the exchange is greater or lesser than the cost of sending four engineers to every house affected by the move?
Meanwhile, I spent the bulk of Saturday morning and Sunday night on the phone acting as liaison between BT Openreach and BT Broadband, since open tickets with one part of BT prevent the other part taking action (even to close the ticket). On Saturday I was in the crazy situation of being asked by a BT support person to unscrew the faceplate on my socket in order to test the line myself before they would close a ticket. Shortly after that, another engineer turned up at the front door unannounced and unexpectedly. The saga continues, with the prospect of me sitting in the office at midnight this week in order to participate in online conference calls if BT are unable to get their act together.
The irony here is that in parochial Norwich, which is located just off the edge of the map of the known world, I was able to get a 10 meg internet connection and cable TV (heck, I was receiving channel 5 from virtually the first day of broadcast, not that it's something to boast about). Moving from the countryside to the city is supposed to result in a better service, no?
Technorati Tags: apartment, failure, house, life, london, norwich, bt, renting, uk
]]>That said, Hudson Crash Landing Still Better Than Heathrow is a perfect example of why I love the daily mash. Irreverant, topical (given the go-ahead for a new runway at Heathrow), and distinctly not politically correct, get your laughing gear around this:
Kathy Cook, a sales assistant from New Jersey, said: "I looked out the window and saw the water getting closer and closer. I thought of my children, my husband, all the things I've never done and then I thought, 'oh well, at least it's not Heathrow'."
Then go read the full article, and subscribe to the mash news feed. A brief flash of sanity in an otherwise insane world. It's like The Onion, only better.
Some of my other favourites there:
BBC hails new Doctor Who as much cheaper
Treasury has been able to print tenners all along
Richard Branson dies laughing
The modus operandi is as follows: the phone rings, displaying a blocked number. When I answer, after a brief pause a recorded sales pitch kicks in, prompting me at various intervals to press a number to hear more about their services. If you press the number, you're put through to a well-trained call handler scripted in selling, but also trained to give no details out about the company they are working for.
The first time it happened, yesterday, they told me they got my number from a marketing database. My number shouldn't be on any marketing database. I told them to remove my number from their list and not to call me ever again (after trying to find out everything I could about them).
This evening, they called again, interrupting my dinner. I can't ignore blocked numbers - sometimes overseas numbers or office numbers are blocked, so it could be friends, family, or work calling me. This time the person I talked to gave out no information at all about the company, other than a bogus name that comes up with no hits in the Companies House database or on Google. When asked for a phone number I could call them on, I was told it was an outbound sales centre with no incoming number, but that a manager could call me back. Needless to say, that hasn't happened.
This is a serious problem for me, as I'm often travelling, and when overseas I pay the bulk of the call charges when I receive a call. Even if it's only a few seconds, it quickly adds up, and this is the worst possible type of abusive marketing: spam you have to pay for.
Sadly, the law is woefully inadequate in this area. Ofcom, the toothless independent regulator that's little more than an industry front, recommends signing up to the Telephone Preference Service. Useful, except I signed up when it first launched, and the website confirms my mobile number is still registered with them.
Next up, the Information Commissioner's Office (ICO), who enforce and oversee the Privacy and Electronic Communications Regulations, amongst other things. What do they say? See Ofcom. Or, if I think the regulations have been breached, write to the organisation that breached them. Yes, the same marketing organisation that phoned me up twice, refusing to provide any contact details whatsoever, certainly not a postal address.
What else can the ICO do? They can ask (or even order) the organisation to follow the law, assuming I can identify them. But they cannot punish an organisation that ignores them.
So, basically, there's no one to stop these people, no way to stop these people, and no way to punish these people. I have a suspicion the future of mobile is whitelisting phone calls. That's just crazy.
Technorati Tags: debate, fraud, government, law, marketing, mobile, spam, regulation
]]>