# 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 18
# self = https://watcher.sour.is/conv/qqgzqfa
@lyxal Mostly too many extra steps you have to do 😁
@lyxal Mostly too many extra steps you have to do 😁
@lyxal Mostly too many extra steps you have to do 😁
@prologic okay second question: what's a git submodule?
@prologic okay second question: what's a git submodule?
So Git Submodules are basically references to other Git repositories that are embedded in the source repository. You manage them with git submodule .... The painful thing is that you have to be careful which type of URI you add them with, git:// or https:// (_which can bite you in the ass depending on the rest of your pipelines_) and every time you make a change to a Git submodule's repository you have to go and update umpty nine other repositories that reference the submodule and update to point to a new Git sha. It's all quite painful and a waste of time!
So Git Submodules are basically references to other Git repositories that are embedded in the source repository. You manage them with git submodule .... The painful thing is that you have to be careful which type of URI you add them with, git:// or https:// (_which can bite you in the ass depending on the rest of your pipelines_) and every time you make a change to a Git submodule's repository you have to go and update umpty nine other repositories that reference the submodule and update to point to a new Git sha. It's all quite painful and a waste of time!
So Git Submodules are basically references to other Git repositories that are embedded in the source repository. You manage them with git submodule .... The painful thing is that you have to be careful which type of URI you add them with, git:// or https:// (_which can bite you in the ass depending on the rest of your pipelines_) and every time you make a change to a Git submodule's repository you have to go and update umpty nine other repositories that reference the submodule and update to point to a new Git sha. It's all quite painful and a waste of time!