Get short, timely messages from Geoff Pitfield.

Twitter is a rich source of instantly updated information. It's easy to stay updated on an incredibly wide variety of topics. Join today and follow @gpitfield.

Get updates via SMS by texting follow gpitfield to 40404 in the United States
Codes for other countries

Two-way (sending and receiving) short codes:
Country Code For customers of
Australia
  • 0198089488 Telstra
Canada
  • 21212 (any)
United Kingdom
  • 86444 Vodafone, Orange, 3, O2
Indonesia
  • 89887 AXIS, 3, Telkomsel
Ireland
  • 51210 O2
India
  • 53000 Bharti Airtel, Videocon
Jordan
  • 90903 Zain
New Zealand
  • 8987 Vodafone, Telecom NZ
United States
  • 40404 (any)

gpitfield

  1. @ShawInfo here's an idea. Less about the food bank, more about the stoopid Internet not working. Just sayin. 10:43 AM Apr 26th via Twitter for iPhone
  2. @leftrightminds us too. Gastown. Where are you? 10:33 AM Apr 26th via Twitter for iPhone in reply to leftrightminds
  3. @Aquamindy here's instructions bjango.com/help/crashlog/ and if you send to geoff@fleetly that would be great. Thanks & lmk if questions 6:06 PM Jan 11th via web in reply to Aquamindy
  4. @Aquamindy @Fleetly Hey I'm still working on this. Do you know how to send crash logs? Would be a big help LMK & I'll give you email address 4:29 PM Jan 11th via web in reply to Aquamindy
  5. @aschulak @Aquamindy @csitko data most definitely does not run on main thread. Not without our issues, but that ain't one of them ;-) 5:09 PM Dec 29th, 2011 via web in reply to aschulak
  6. @takaiguchi @fleetly odd. I'll have a look 10:24 AM Dec 29th, 2011 via web in reply to takaiguchi
  7. @takaiguchi @fleetly possibly doing address book or FB friend match? i.e. are they suggestions or actual friends? 10:14 AM Dec 29th, 2011 via web in reply to takaiguchi
  8. @AppDar @fleetly You won't lose your already logged stuff - it will get re-synced from the server 10:59 PM Dec 28th, 2011 via web in reply to AppDar
  9. @takaiguchi @Fleetly ...when someone logs 3 walking mi in 6 hrs, we assume they actually walked 6 hrs. Clearly not right & will be fixing 10:58 PM Dec 28th, 2011 via web in reply to takaiguchi
  10. @takaiguchi @Fleetly Yeah we need to tweak that. Points are a function of work done, but we're giving too many for some time-based entries 10:56 PM Dec 28th, 2011 via web in reply to takaiguchi
  11. ruh-roh-oops I think that if you share a challenge on the new @fleetly version it makes crashy time. We'll be fixing that shortly :-/ 10:23 PM Dec 28th, 2011 via web
  12. @AppDar @Fleetly Please do send them. Hello@fleetly is best. Thanks and glad it's fixed 8:46 PM Dec 28th, 2011 via Mobile Web in reply to AppDar
  13. @BriskFitness @Fleetly welcome and let us know what you think! 5:28 PM Dec 28th, 2011 via web in reply to BriskFitness
  14. @AppDar @Fleetly can you send us your login to hello@fleetly? We'll take a look 12:45 PM Dec 28th, 2011 via web in reply to AppDar
  15. @emchenNYC @fleetly swipe right across the record to delete. You can enter distance in distance field, or link to Nike+ or RunKeeper for GPS 12:44 PM Dec 28th, 2011 via web in reply to emchenNYC
  16. @kaylaxane @Pier_Eighteen @Tonknicity shoot us an email to hello@fleetly.com and we'll get you sorted out, promise! 5:44 PM Dec 22nd, 2011 via web in reply to kaylaxane
  17. @DesignerTi @fleetly me too! 5:43 PM Dec 22nd, 2011 via web in reply to DesignerTi
  18. @Pier_Eighteen @tonknicity ha just saw this now. Definitely that must be it - rollergirl power :-) 7:41 PM Dec 21st, 2011 via Twitter for iPhone in reply to Pier_Eighteen