# 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 24
# self = https://watcher.sour.is/conv/jj6jfrq
Hmmmm π’ The "Conversation" count/badge and "Hide when there are no replies yet" is _actually_ costing quite a bit of performance. I was a bit worried this would happen. The way this is being done is an O(n^2) type thing in Big-O notation and this _really_ sucks π’
Hmmmm π’ The "Conversation" count/badge and "Hide when there are no replies yet" is _actually_ costing quite a bit of performance. I was a bit worried this would happen. The way this is being done is an O(n^2) type thing in Big-O notation and this _really_ sucks π’
I __think__ I might revert this until I can count Twts in a conversation faster π€
I __think__ I might revert this until I can count Twts in a conversation faster π€
That's better π
Sorry @darch and @fastidious we can't have this "conversation count" and "hide when no conversation" feature until the backend either learns a way to index and cache conversations or has integrated search (_probably the later makes more sense since it has more utility beyond just counting twts in a conversation_)
That's better π
\n\n \n\nSorry @darch and @fastidious we can't have this "conversation count" and "hide when no conversation" feature until the backend either learns a way to index and cache conversations or has integrated search (_probably the later makes more sense since it has more utility beyond just counting twts in a conversation_)
That's better π
Sorry @darch and @fastidious we can't have this "conversation count" and "hide when no conversation" feature until the backend either learns a way to index and cache conversations or has integrated search (_probably the later makes more sense since it has more utility beyond just counting twts in a conversation_)
@eldersnake Sorry if you happned to pull/update to these commits in-between, if you had, please ensure you're on yarnd v0.2.0@674c163 so your Raspberry Pi and VPS doesn't melt π€£
@eldersnake Sorry if you happned to pull/update to these commits in-between, if you had, please ensure you're on yarnd v0.2.0@674c163 so your Raspberry Pi and VPS doesn't melt π€£
@fastidious Will endevour to bring it back donβt worry π€\n\nBut canβt have such disgusting performance regressions π€¦ββοΈ
@fastidious Will endevour to bring it back donβt worry π€
But canβt have such disgusting performance regressions π€¦ββοΈ
@fastidious Will endevour to bring it back donβt worry π€
But canβt have such disgusting performance regressions π€¦ββοΈ
My old man would have some bad things to say about this the next time he browses his timeline π
My old man would have some bad things to say about this the next time he browses his timeline π
@prologic tell him it was our fault, and that we beg him to go easy on you. π
@prologic All good, it's just good to see someone so hard on performance regressions π Probably some devs out there that would try justify it for the extra feature...
@eldersnake Nope! π One of the original unstated goals was always resource utilization. π It was and still is **absolutely** mandatory that a pod be capable of being hosted at a cost of a dollar a month or less π
@eldersnake Nope! π One of the original unstated goals was always resource utilization. π It was and still is **absolutely** mandatory that a pod be capable of being hosted at a cost of a dollar a month or less π
@prologic Well my (and @jlj 's) RPi thanks you π