# 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 14
# self = https://watcher.sour.is/conv/mojeqxq
@prologic It started out good, but then it plummeted into praising GitHub. š¤ I donāt really see the advantage of GitHub over something like Jira. Yes, Jira is much more complex, but GitHub is getting more complex all the time as well. GitHub used to be *way* simpler than it is now. Itās only a matter of time until it becomes indistinguishable from Jira. Plus, you also have a āvendor lock-inā when you use all those project management features of GitHub, donāt you? Those arenāt stored in a Git repo and they canāt be trivially migrated to some other tool. (And finally, if you already have āthe discipline to do lessā, you can do that with Jira just as well. Except that itās way more expensive. š
)
I think it all hinges on the *intent* to do things in a simple/minimalistic way. Once youāve reached that mindset, most other things will fall into place. Youāll automatically choose plain text, for example.
(I wanted to write a blog post about this topic a few days ago but eventually gave up on it, because who am I to tell people how to write/manage software? š Itās interesting nonetheless. Maybe Iāll pick it up some other day.)
@prologic It started out good, but then it plummeted into praising GitHub. š¤ I donāt really see the advantage of GitHub over something like Jira. Yes, Jira is much more complex, but GitHub is getting more complex all the time as well. GitHub used to be *way* simpler than it is now. Itās only a matter of time until it becomes indistinguishable from Jira. Plus, you also have a āvendor lock-inā when you use all those project management features of GitHub, donāt you? Those arenāt stored in a Git repo and they canāt be trivially migrated to some other tool. (And finally, if you already have āthe discipline to do lessā, you can do that with Jira just as well. Except that itās way more expensive. š
)
I think it all hinges on the *intent* to do things in a simple/minimalistic way. Once youāve reached that mindset, most other things will fall into place. Youāll automatically choose plain text, for example.
(I wanted to write a blog post about this topic a few days ago but eventually gave up on it, because who am I to tell people how to write/manage software? š Itās interesting nonetheless. Maybe Iāll pick it up some other day.)
@prologic It started out good, but then it plummeted into praising GitHub. š¤ I donāt really see the advantage of GitHub over something like Jira. Yes, Jira is much more complex, but GitHub is getting more complex all the time as well. GitHub used to be *way* simpler than it is now. Itās only a matter of time until it becomes indistinguishable from Jira. Plus, you also have a āvendor lock-inā when you use all those project management features of GitHub, donāt you? Those arenāt stored in a Git repo and they canāt be trivially migrated to some other tool. (And finally, if you already have āthe discipline to do lessā, you can do that with Jira just as well. Except that itās way more expensive. š
)
I think it all hinges on the *intent* to do things in a simple/minimalistic way. Once youāve reached that mindset, most other things will fall into place. Youāll automatically choose plain text, for example.
(I wanted to write a blog post about this topic a few days ago but eventually gave up on it, because who am I to tell people how to write/manage software? š Itās interesting nonetheless. Maybe Iāll pick it up some other day.)
@movq Yeah, that GitHub praise also turned me off, too. He should have stuck with plain Git or at least something self-hostable. The GitHub-lockin also jumped right at me. I find tables quite neccessary sometimes, markdown just hasn't standardized them in a single fashion, they depend on the exact implementation.
Looking forward to your article about simplicity. :-)
@lyse I wish more standardization around distributed issues and PRs within the repo ala git-bug was around for this. I see it has added some bridge tooling now.
@lyse I wish more standardization around distributed issues and PRs within the repo ala git-bug was around for this. I swlee it has added some bridge tooling now.
@lyse I wish more standardization around distributed issues and PRs within the repo ala git-bug was around for this. I see it has added some bridge tooling now.
@xuu I fully agree, distributed bug trackers are the way to go. It is just so natural to have the issues and the code at the same place together. I probably wrote it in the past, a few mates and I tried several times to roll our own, but none of them really made it in the end. We learned a lot, though. Thanks for recommending git-bug, I'll take a close look at this and see whether that suits my needs.
Remember that I don't actively use Github since some years ago š¤£ So I wasn't praising the "Github" parts of this video, just the Git and Distributed parts in general š
Remember that I don't actively use Github since some years ago š¤£ So I wasn't praising the "Github" parts of this video, just the Git and Distributed parts in general š
Remember that I don't actively use Github since some years ago š¤£ So I wasn't praising the "Github" parts of this video, just the Git and Distributed parts in general š