# 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 29
# self = https://watcher.sour.is/conv/6v5vblq
@lukem On it, Fix already commited/merged. Should get updated shortly... 😎
@lukem On it, Fix already commited/merged. Should get updated shortly... 😎
@lukem On it, Fix already commited/merged. Should get updated shortly... 😎
@prologic @lukem Well that was embarrassing I made it worse :/ When I wrote the "Mute User" feature I _thought_ I could cheat and filter the Twts at the template level. This is proving to be harder than it should so I'll just do it where it should have been donee in the first place, some call it the Controller level :D
@prologic @lukem Well that was embarrassing I made it worse :/ When I wrote the "Mute User" feature I _thought_ I could cheat and filter the Twts at the template level. This is proving to be harder than it should so I'll just do it where it should have been donee in the first place, some call it the Controller level :D
@prologic @lukem Well that was embarrassing I made it worse :/ When I wrote the "Mute User" feature I _thought_ I could cheat and filter the Twts at the template level. This is proving to be harder than it should so I'll just do it where it should have been donee in the first place, some call it the Controller level :D
@lukem I'm so embarrased 😳 I shouldn't stay up this late coding 😴
@lukem I'm so embarrased 😳 I shouldn't stay up this late coding 😴
@lukem I'm so embarrased 😳 I shouldn't stay up this late coding 😴
@prologic haven't we all done that at some point of our lives?
@prologic haven't we all done that at some point of our lives?
@prologic I, for example, once committed and published a change that broke a functionality and I didn't even blink when I saw test snapshots being overwritten with garbage. 4 hours later it turned out those parentheses in a regular expression were in fact meaningful. Several build processes on the way and full test coverage didn't protect me from my own stupidity. So yeah.
@prologic I, for example, once committed and published a change that broke a functionality and I didn't even blink when I saw test snapshots being overwritten with garbage. 4 hours later it turned out those parentheses in a regular expression were in fact meaningful. Several build processes on the way and full test coverage didn't protect me from my own stupidity. So yeah.
Yeah you're right of course! But I _should_ have tested that change a bit more! Shoulda, Coulda, Woulda, etc 😀 We will in time add more test coverage, but of course that won't save me from doing stupid things either! 🤣
Yeah you're right of course! But I _should_ have tested that change a bit more! Shoulda, Coulda, Woulda, etc 😀 We will in time add more test coverage, but of course that won't save me from doing stupid things either! 🤣
Yeah you're right of course! But I _should_ have tested that change a bit more! Shoulda, Coulda, Woulda, etc 😀 We will in time add more test coverage, but of course that won't save me from doing stupid things either! 🤣
@prologic my take is that people doing stupid things with computers is what keeps our industry alive and interesting😁
@prologic my take is that people doing stupid things with computers is what keeps our industry alive and interesting😁
@lukem haha! or in other words “hacker culture” 😎
@lukem haha! or in other words “hacker culture” 😎
@lukem haha! or in other words “hacker culture” 😎