# 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 11
# self = https://watcher.sour.is/conv/gwbdn3q
QOTD: Do you keep a personal archive of Git repositories? If so, how? My backup system is a poorly written, inefficient shell script that I run manually when I think about it and I'd like to do something about that. The Yuzu and Citra emulators were taken down recently and I have a ~3 day old backup of Yuzu's repository but nothing for Citra.~
@mckinley I just use my Gitea instance which itself is backed up
@mckinley I just use my Gitea instance which itself is backed up
@mckinley I just use my Gitea instance which itself is backed up
@mckinley Not really. 🤔 I have some repos on disk in case they vanish, but I don’t pull them regularly or systematically … 🫤
@mckinley Not really. 🤔 I have some repos on disk in case they vanish, but I don’t pull them regularly or systematically … 🫤
@mckinley Not really. 🤔 I have some repos on disk in case they vanish, but I don’t pull them regularly or systematically … 🫤
@mckinley Wouldn’t a cronjob suffice here? Give it a list of repos to mirror, then do daily pulls. As you mentioned in the other threads, the only thing to worry about is force-pushed upstreams. 🤔 Or vandalism upstream. What if they delete all branches … Okay, now that I think about it, it might be a little more complicated. 😂
@mckinley Wouldn’t a cronjob suffice here? Give it a list of repos to mirror, then do daily pulls. As you mentioned in the other threads, the only thing to worry about is force-pushed upstreams. 🤔 Or vandalism upstream. What if they delete all branches … Okay, now that I think about it, it might be a little more complicated. 😂
@mckinley Wouldn’t a cronjob suffice here? Give it a list of repos to mirror, then do daily pulls. As you mentioned in the other threads, the only thing to worry about is force-pushed upstreams. 🤔 Or vandalism upstream. What if they delete all branches … Okay, now that I think about it, it might be a little more complicated. 😂
@mckinley No, I don't mirror code from others unless I work on that project, too. But then it's all manual git fetch, nothing automated. If something is taken down or vandalised I hope that somebody else has a mirror and can help restore. This of course only works for popular code bases.
Good thought, though. I might have to look through my dependencies and identify candidates that might not have somebody who could help to get things back online.