# 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 6
# self = https://watcher.sour.is/conv/jrucdka
@prologic I've thought about that, but it seems awfully inefficient to host a full code forge with a Web interface just to mirror some Git repositories.
How does Gitea store repositories? Are they just bare Git repositories on the filesystem that can be cloned separately? Also, how does it handle the upstream force-pushing an empty repository? Will that destroy your archive?
@mckinley Normally I just fork by hand actually and use normal Git operations.
@mckinley Normally I just fork by hand actually and use normal Git operations.
@mckinley Normally I just fork by hand actually and use normal Git operations.
Whoops, I started a thread when I meant to reply to the other one. I don't think I've ever done that before.