Nick Sivo's dashboard

Nick Sivo set one of Nick Sivo's replies as an official response to "i need to reset my password. can someone please help me" in Loopt

Nick Sivo replied on December 15, 2008 19:49 to the question "i need to reset my password. can someone please help me" in Loopt:

Hi sheila,

You can reset your password and perform other account management functions at http://support.loopt.com/

Nick Sivo set one of Nick Sivo's replies as an official response to "I can't login, link, or update Twitter from Loopt. What's going on?" in Loopt

Nick Sivo replied on December 13, 2008 04:38 to the question "I can't login, link, or update Twitter from Loopt. What's going on?" in Loopt:

We've fixed it. Thanks for letting us know :)

Nick Sivo replied on November 25, 2008 03:29 to the idea "Windows Mobile support for Loopt" in Loopt:

The straight answer:

There are no plans in the next six months to release a native WinMo build. Can't say anything about after that because it's too far in the future.

We're in the process of a complete re-write of our J2ME application, and it currently runs just fine in the JVM on the AT&T Tilt and Blackjack 2. We aren't explicitly targeting WinMo for this project. If when we're done the J2ME application runs on WinMo in a JVM, I'll personally do the extra work to interface with the native GPS support (not accessible from J2ME on WinMo).

None of this is set in stone, and it may change, but it's not likely.

In response to recent comments:

Regarding an API: we don't have anything polished or robust enough to expose to third parties yet. We won't in the next year.

We're not ignoring WinMo to make people buy iPhones. As awesome as it would be if we had that kind of power, we don't. If we did have it, we wouldn't use it that way, since doing so would only hurt us.

It's a time issue, not a money issue.

I truly am sorry. I genuinely want us to support WinMo. But that isn't enough. It simply isn't going to happen soon unless we can get it for free. I know this isn't what any of you want to hear, but it's the honest truth.

Nick Sivo set one of Nick Sivo's replies as an official response to "cant receive confirmation text...help!" in Loopt

Nick Sivo replied on November 25, 2008 02:37 to the problem "cant receive confirmation text...help!" in Loopt:

Fixing your problem is as simple as sending "start" to 56678.

Please let me know if this doesn't work.

Nick Sivo replied on November 23, 2008 03:47 to the idea "Windows Mobile support for Loopt" in Loopt:

Jamon -

There are three ways a phone gets Loopt support:
1. A carrier or handset OEM asks us to support it or offers to pre-load it (ship Loopt on the device out of the box).
2. The phone accounts for a large percentage of a carrier's user base. (ex: the Motorola Razr)
3. A developer a Loopt has the phone and makes a build for it on their own time. The iPhone and Nokia N95 builds started this way.

Currently one person at Loopt (not a mobile developer) has a windows mobile phone. There's not a strong internal push for it.

I would love to see a WinMo build, and may myself get an AT&T Fuze.

Sadly, right now it gets attention when we're not busy making a build for a pre-load opportunity, improving the service, or keeping the service up (see twitter threads on GetSatisfaction for one example).

Sorry :(

Nick Sivo set one of Nick Sivo's replies as an official response to "How do I stop this?" in Loopt

Nick Sivo replied on November 22, 2008 01:11 to the question "How do I stop this?" in Loopt:

Hi Beth,

You can reply "STOP" to any of the messages to block all messages from Loopt. To permanently delete the Loopt account associated with your number, please email us at support@loopt.com.

Nick Sivo replied on November 16, 2008 20:43 to the problem "Loopt no longer posting to Twitter via iPhone app." in Loopt:

Thanks for letting us know. We're working on some changes that should keep it up in the future.

Should be working... for now :)

Nick Sivo replied on November 11, 2008 05:35 to the idea "Windows Mobile support for Loopt" in Loopt:

I'm getting an AT&T Fuze so I want WinMo support as well.

The build we tested on a Tilt was not beta. It uses a new method of communicating with the server that currently only works against my development machine. All it can do is log in and download friend information; It's incapable of publishing new content.

If and when a beta is available, I'll let you know. We just don't have one yet.

Nick Sivo replied on November 09, 2008 21:45 to the question "can I change the iPhone text alert to a custom tone?" in Loopt:

Hi MarkR,

We don't have the resources to assist customers with non-Loopt related phone problems. For any questions you may have about your iPhone, please contact AT&T by dialing 611 from your phone .

Nick Sivo replied on November 07, 2008 20:19 to the problem "Loopt no longer posting to Twitter via iPhone app." in Loopt:

In every test we've run, this now works.

If you're still having problems, please let us know, but we think we've fixed it.

Nick Sivo replied on November 07, 2008 20:16 to the question "Is it possible to track a stolen Iphone?" in Loopt:

Unfortunately, background tracking is not currently possible on the iPhone. The only way to determine your phone's location would be to get the thief to open Loopt and, if necessary, log in.

I"m sorry :(

Nick Sivo started following the idea "Exporting a Loopt journal as a KMZ or KML file" in Loopt.

Nick Sivo set one of Nick Sivo's replies as an official response to "Japanese and other URL encoded text." in Loopt

Nick Sivo replied on October 23, 2008 09:06 to the problem "Japanese and other URL encoded text." in Loopt:

Fixed now :)

Nick Sivo set one of Nick Sivo's replies as an official response to "Japanese and other URL encoded text." in Loopt

Nick Sivo replied on October 23, 2008 08:13 to the problem "Japanese and other URL encoded text." in Loopt:

Hi gSOLO,

This problem has been fixed in our latest code and will go live with our next maintenance release. Thanks for reporting it :)

Our URL encoding function used the non-standard %uXXXX encoding for high order Unicode characters. I fixed it to be standards compliant.