Chris Clark's dashboard

Well you'd get beta access to TTR 1.3, too ;)

lol. Yeah we're having all kinds of *ahem* "challenges" getting the Ad Hoc Distribution system to work.

More than half of the Twinkle community is Twinkle-only -- they don't have Twitter accounts -- so the following won't carry over to Twitter. If you follow a Twitter user from within Twinkle it should carry over to Twitter immediately. – Chris Clark, on August 09, 2008 22:04

Sorry, we're only getting submissions from Twinkle. Could you tell me how Twinkle is behaving on your Touch? Maybe we can fix the problem :)

Only the currently-downloadable tracks need to be played. We pulled a few tracks (including Goodbye Railroad) a while ago that we're in the process of re-tapping because we felt the tap patterns weren't up to standard :)

You're right -- 30,000 points probably won't get you on the leaderboards, so we'll just be checking our databases for scores above 30,000. Shakes on or off, we don't mind.

Twinkle doesn't require you to have a Twitter account, so TwinkleKing will get your message regardless :) Thanks for playing!

1.2 has received a number of tweaks under the hood which should result in far smoother play.

As to the OP's question, there is an "exact" correct moment to tap, which is programmed into the track by our music wizard, and that's the point when the bubble 'pops' on the line. That'll score you 150 points, but there's a buffer on either side of that (for early tappers and late tappers) with lower score values.

Blocking is in 1.2, I can confirm that for sure :) There are still other features being built into 1.2 before we release it though...

Unfortunately, the phone's addressbook frameworks don't even know which card is your Me Card -- Friend Book must ask you to pick it out before you can share it. So although I'm not *certain* I'd guess it doesn't know which fields are private, either. Private fields aren't a feature of Friend Book 1.0 (or the forthcoming 1.1 re-release) but it's something to consider for the future. – Chris Clark, on August 09, 2008 11:16

I like your idea :)

It'll still be a while yet, I'm sorry to say. No confirmed date.

On the other topic, there are two reasons (reasons we believe are very good) for using Device IDs instead of passwords. One is security, and the other is convenience.

Normally, security and convenience are at opposing ends of a spectrum. Things that are very secure are generally inconvenient and vice versa. Having five deadbolts on your door is pretty secure, but it sucks to have to lock and unlock them every day.

In this case, security and convenience are on the same side for once. As I said in my earlier post, it's like your phone's fingerprint. So, while the phone belongs to you, it's a proxy for *your* fingerprint. On Twinkle, your phone = you.

The device ID is also more secure than the average password (40 characters of utterly random hex) and it's very convenient. You never have to type it or even remember it -- it's part of the phone.

Where this *does* pose a problem is the situation that has been described where you sell your phone on eBay and now your phone doesn't = you. In this case you can follow the instructions in the Help screen to log out of your phone before you sell it, and it's done. We're working on ways to make the logout easier than it is already, but right now it's not hard. And if you forget to do it, you can always email us.

We're also working on ways to ensure that if you wipe your phone before selling it (but forget to log out) the buyer can't impersonate you.

Passwords are a very old security technology that (for the vast majority) are insecure. Ten years ago the most common password on the web was 'password' and today it's 'password1'. Good banks are starting to use multi-factor authentication because passwords just aren't good enough to protect your money. iPhone is a new platform with new ways of doing things, and we're trying to do authentication in a way that's new, inventive, secure, and convenient. So please, give it a chance :)

My apologies for neglecting this thread. I used to be Tapulous' main support guy and spend hours a day in here, but have been spending more time in product design lately and have let our man Ed take the reigns of GetSatisfaction.

To get straight to the point: device IDs don't pose a privacy threat. If we used something else to identify you (like passwords, or facial recognition, or your phone's M.A.C. address) we'd *still* have a complete database of everything mentioned above: email address, geographical location, twinkle messages and photos. So whatever privacy concerns you might have about our databases being full of *that* information are unrelated to device IDs.

The ID itself is literally only useful as confirmation that the phone in your hand today is the same phone that was in your hand yesterday. It's your phone's fingerprint.

We can't use your phone's ID to impersonate you and we can't use it to find out any additional information about you. If anyone has a legitimate argument as to *how* we might use device IDs to invade privacy, I'd really love to engage in a discussion.

Hey codedigital,

Your Twitter posts are private, but you're still posting replies publicly to the Tapulous network. To disable this, go to Settings and turn off Broadcast Location. Then your posts won't show up in the Nearby tab. Hope that helps.

We always like hearing ways to improve things -- some of them are of course viable and some aren't, and some are easier to get into a 1.x release and some have to wait for a major update like 2.0. We're always looking at these things though :)

Hey Dan, it turns out the 14 Tapulous Promoter winners weren't submitted to Lala with the original batch of winners because Ed was still waiting on contact details for a few of you. I believe Ed has submitted most of you now.

New songs are listed in the "Download New Tracks" menu.

Blocking is part of Twinkle 1.2, which we're in the process of developing now. Please be patient, if we post a half-baked update to the App Store it'll cause a lot of problems.

In the mean time, if you can report really offensive people to Andrew (see http://tapulous.com/about/andrew/ for contact details) he can look into them and warn and/or ban them from the network.

*bump*

If you're on this list, be sure to post your Tapulous ID or your email address so you can get your free album!

OK -- it turns out the 14 Tapulous Promoters' emails haven't been sent to Lala yet! Sorry, we're still waiting on the last few people to identify themselves here :(

http://getsatisfaction.com/tapulous/t...

OK -- it turns out the 14 Tapulous Promoters' emails haven't been sent to Lala yet! Sorry, we're still waiting on the last few people to identify themselves here :(

http://getsatisfaction.com/tapulous/t...