Skip to main content
TM.'s user avatar
TM.'s user avatar
TM.'s user avatar
TM.
  • Member for 14 years, 7 months
  • Last seen more than 6 years ago
  • Oakland, CA, United States
awarded
awarded
revised
Stacktacular: Stack Exchange client for WebOS
added 188 characters in body
Loading…
revised
Stacktacular: Stack Exchange client for WebOS
deleted 81 characters in body
Loading…
revised
Stacktacular: Stack Exchange client for WebOS
deleted 430 characters in body
Loading…
comment
Stacktacular: Stack Exchange client for WebOS
I'll add it to my "todo" list. Please give me any other feedback you have.
awarded
revised
Stacktacular: Stack Exchange client for WebOS
deleted 64 characters in body
Loading…
revised
Stacktacular: Stack Exchange client for WebOS
added 77 characters in body
Loading…
comment
webStack - A Stack Overflow Application for webOS
@George since this never panned out, I ended up building my own WebOS client: stackapps.com/questions/1645/… I'd love to hear your opinion.
revised
Stacktacular: Stack Exchange client for WebOS
added 217 characters in body
Loading…
revised
Stacktacular: Stack Exchange client for WebOS
added 270 characters in body
Loading…
revised
Stacktacular: Stack Exchange client for WebOS
added 93 characters in body
Loading…
awarded
revised
Stacktacular: Stack Exchange client for WebOS
added 19 characters in body; edited tags; added 100 characters in body
Loading…
awarded
revised
Stacktacular: Stack Exchange client for WebOS
deleted 63 characters in body
Loading…
Loading…
comment
Conscientious use of the API
What if the requests are only triggered by user activity? For example: a refresh button for /questions results. Is allowing a manual refresh considered abusive? I can imagine some users tapping it way more than once per minute. Do we need to put a throttle on these types of things?
awarded