# 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 24
# self = https://watcher.sour.is/conv/nr6f4ja
Hmm, maybe I should also plot the *gaps*. 🤔 There are many projects that don’t see commits for a couple of years. Oh well, that’s task for another day.
Hmm, maybe I should also plot the *gaps*. 🤔 There are many projects that don’t see commits for a couple of years. Oh well, that’s task for another day.
Hmm, maybe I should also plot the *gaps*. 🤔 There are many projects that don’t see commits for a couple of years. Oh well, that’s task for another day.
are these projects you created?
are these projects you created?
@xuu Most of them, yes. That’s the code I host on my website. dwm-vain, tabbed-vain and qsqs are forks, though, hence dwm-vain appears to be much older. (I only started using dwm in 2012.)
I didn’t use version control systems in the distant past, but nobody wants to see that old stuff anyway. 😅
@xuu Most of them, yes. That’s the code I host on my website. dwm-vain, tabbed-vain and qsqs are forks, though, hence dwm-vain appears to be much older. (I only started using dwm in 2012.)
I didn’t use version control systems in the distant past, but nobody wants to see that old stuff anyway. 😅
@xuu Most of them, yes. That’s the code I host on my website. dwm-vain, tabbed-vain and qsqs are forks, though, hence dwm-vain appears to be much older. (I only started using dwm in 2012.)
I didn’t use version control systems in the distant past, but nobody wants to see that old stuff anyway. 😅
@movq its always fun to look back on old projects. I talked to an old coworker about a codebase i made back in 2010 that still has lots of the same architecture i built into it back then and is still in heavy use.
@movq its always fun to look back on old projects. I talked to an old coworker about a codebase i made back in 2010 that still has lots of the same architecture i built into it back then and is still in heavy use.
@xuu Oh, that’s great! 😃 It’s wonderful when things are long-lasting. 😊
@xuu Oh, that’s great! 😃 It’s wonderful when things are long-lasting. 😊
@xuu Oh, that’s great! 😃 It’s wonderful when things are long-lasting. 😊
Now the graph shows the gaps:
https://www.uninformativ.de/git/timeline.png
Much more realistic. Most stuff lies dormant most of the time. 😅
Which is a good thing in my book. I think there’s something wrong if software needs constant tinkering.
Now the graph shows the gaps:
https://www.uninformativ.de/git/timeline.png
Much more realistic. Most stuff lies dormant most of the time. 😅
Which is a good thing in my book. I think there’s something wrong if software needs constant tinkering.
Now the graph shows the gaps:
https://www.uninformativ.de/git/timeline.png
Much more realistic. Most stuff lies dormant most of the time. 😅
Which is a good thing in my book. I think there’s something wrong if software needs constant tinkering.
@movq What happened in March of 2018 with all those commits across your projects?
@mckinley That was the move away from GitHub. I then had to change all the links in the affected repos. 🥴 (It appears I skipped *some* older repos back then. 🤔)
@mckinley That was the move away from GitHub. I then had to change all the links in the affected repos. 🥴 (It appears I skipped *some* older repos back then. 🤔)
@mckinley That was the move away from GitHub. I then had to change all the links in the affected repos. 🥴 (It appears I skipped *some* older repos back then. 🤔)
@movq I see. It's interesting to see commit history visualized that way.