# 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 10
# self = https://watcher.sour.is/conv/z4daphq
Speaking of "never done in software" I believe mkws is done. I also believe chasing progress is a trap, that's why people believe software is "never done".
@adi Oh, software can be very much “done”. Define a scope, implement all required features, done. Everything after that is / should be fixing bugs. 😊
@adi Oh, software can be very much “done”. Define a scope, implement all required features, done. Everything after that is / should be fixing bugs. 😊
@adi Oh, software can be very much “done”. Define a scope, implement all required features, done. Everything after that is / should be fixing bugs. 😊
@vain Agree!
@vain Agree!
@vain Agree!
@vain is right, But it's also about managing change. Software _can_ be considered done, absolutely, but as is the case for Yarn.social (_since we've decided on the rebranding now_), we're quite a long ways from even considering it "done". 🤣
@vain is right, But it's also about managing change. Software _can_ be considered done, absolutely, but as is the case for Yarn.social (_since we've decided on the rebranding now_), we're quite a long ways from even considering it "done". 🤣
@vain is right, But it's also about managing change. Software _can_ be considered done, absolutely, but as is the case for Yarn.social (_since we've decided on the rebranding now_), we're quite a long ways from even considering it "done". 🤣