# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 7
# self = https://watcher.sour.is/conv/7ldrcdq
@lyse Thanks dude, I'll take a look. If you need any specific feedback or to ping-pong ideas, throw me an @
@eaplmx The big question is: How to deal with different sorts of exercises. Like situps and pushups require a counter, but a bike ride or hike do not. They require a distance, a route and what not. Should I go full overboard and make the exercise types completely user-configurable? Or should I just offer two different things built in with the option to expand later on in the code if necessary? Two fundamentally different solutions.
@lyse interesting question. When I reached the drawing board I got the same question. Should we register everything? Calories, distance, steps, time and such?
I thought it was going to be tedious to type every kind of info, so I went down to a single number representing I did any exercise, being the final goal to do more.
It was burned calories for me...
So unless you have an automatic way to store all that geeky data, I'll suggest to ask for the min amount of numbers.
That said, anything user-configurable is a pain in the back since you have to add editors, validators, tutorials and such. I wouldn't do it yet, unless you have a paying user or similar. Perhaps you can add 2 or 5 presets which you can rename for general purposes. And then you store the amounts for that activity and have an equivalent numeet between exercises, again, like calories.
So unless you have an automatic way to store all that geeky data, I'll suggest to ask for the min amount of numbers.
That said, anything user-configurable is a pain in the back since you have to add editors, validators, tutorials and such. I wouldn't do it yet, unless you have a paying user or similar. Perhaps you can add 2 or 5 presets which you can rename for general purposes. And then you store the amounts for that activity and have an equivalent number across exercises, again, like calories.
To avoid premature optimization you can have room for further expansions but not implementing it yet. For instance saying "this record is version 1" if it's V2, then look into this other table with more details.
Just a wild idea, it would depend on your current architecture and how much it could change soon
@eaplmx You're spot on. Making everything configurable opens a whole sea container of worms. You convinced me to make it as simple as possible. Haha, no, I do not have paying users, in fact it's just me. Maybe up to three other mates in the future. It's just a hobby project, so there won't be anybody paying anything. And that's perfectly fine for me as nobody can force me to do something. :-)
I'll go with two predefined exercise types, that's all that *I* need at the moment. Yeah, keeping extensability in mind is very important. Thank you very much for all your valuable input!
Our approaches differ in measurements, I don't care about calories, although, that is most likely by far the best meaningful number. It's just not something I'm interested in and I also don't have any way to measure it. In that regard I'm like a child and want to play with counting exercises. ;-)