# 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 12
# self = https://watcher.sour.is/conv/uckc5ia
Not using semver for my own projects was probably one of the worst decisions in the last decade. 🀦 I should change that …
Not using semver for my own projects was probably one of the worst decisions in the last decade. 🀦 I should change that …
Not using semver for my own projects was probably one of the worst decisions in the last decade. 🀦 I should change that …
@movq It's not a problem if you're the only one using and maintaining your projects. What versioning scheme have you been using?
@lyse Date-based versions, such as xiate-20.07. πŸ€” It’s rare, but some of my software does get packaged for some Linux distros … At the end of the day, most of my releases would probably end up bumping the major version number. πŸ™„ But with semver, it would at least be obvious for users that something might/will break.
@lyse Date-based versions, such as xiate-20.07. πŸ€” It’s rare, but some of my software does get packaged for some Linux distros … At the end of the day, most of my releases would probably end up bumping the major version number. πŸ™„ But with semver, it would at least be obvious for users that something might/will break.
@lyse Date-based versions, such as xiate-20.07. πŸ€” It’s rare, but some of my software does get packaged for some Linux distros … At the end of the day, most of my releases would probably end up bumping the major version number. πŸ™„ But with semver, it would at least be obvious for users that something might/will break.
@movq Ah, I see. I reckon you can just switch to semver with your next release. Just highlight the versioning switch in the readme and you're good to go.
What keeps annoying me: The changes between releases are usually tiny, for example: https://www.uninformativ.de/git/katriawm/file/CHANGES.html Very few people use my stuff anyway. I might be overthinking this … πŸ™„
What keeps annoying me: The changes between releases are usually tiny, for example: https://www.uninformativ.de/git/katriawm/file/CHANGES.html Very few people use my stuff anyway. I might be overthinking this … πŸ™„
What keeps annoying me: The changes between releases are usually tiny, for example: https://www.uninformativ.de/git/katriawm/file/CHANGES.html Very few people use my stuff anyway. I might be overthinking this … πŸ™„
@movq Looks like versioning of browsers. :'-D