# 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 43
# self = https://watcher.sour.is/conv/gylns4a
@movq Hosting it on SourceForge fits the mould quite well. My first real software project resided over there.
@lyse Lol, the mould. 😁 Yeah, no idea why anyone would want to *start* using SF now. Those times are over, really.
@lyse Lol, the mould. 😁 Yeah, no idea why anyone would want to *start* using SF now. Those times are over, really.
@lyse Lol, the mould. 😁 Yeah, no idea why anyone would want to *start* using SF now. Those times are over, really.
@lyse @movq Sell and truly over ... 😂 SF is quite dead ☺️
@lyse @movq Sell and truly over ... 😂 SF is quite dead ☺️
@lyse @movq Sell and truly over ... 😂 SF is quite dead ☺️
@movq Oh, they're offering Git over there after all. I thought, they were still stuck with CSV or SVN. Haha, reminds me of former work mates, who even two years ago swore on CSV as the very best and easiest VCS.
@lyse … or take the OpenBSD project, they still use CVS. When asked, they say that it just works well for them and there’s not really a reason to change. That’s super hard for me to imagine. I’d love to see their daily workflow some day – how do they work, how do they think?
@lyse … or take the OpenBSD project, they still use CVS. When asked, they say that it just works well for them and there’s not really a reason to change. That’s super hard for me to imagine. I’d love to see their daily workflow some day – how do they work, how do they think?
@lyse … or take the OpenBSD project, they still use CVS. When asked, they say that it just works well for them and there’s not really a reason to change. That’s super hard for me to imagine. I’d love to see their daily workflow some day – how do they work, how do they think?
@movq @lyse I used CVS for a while for mkws, it's not horrible, I dropped off any kind of versioning system as of recently.
@movq @lyse I used CVS for a while for mkws, it's not horrible, I dropped off any kind of versioning system as of recently.
@movq @lyse I used CVS for a while for mkws, it's not horrible, I dropped off any kind of versioning system as of recently.
@adi @movq @lyse I plan to write a "dumb" versioning system at some point working with just a text file as a repository with a list of patches.
@adi @movq @lyse I plan to write a "dumb" versioning system at some point working with just a text file as a repository with a list of patches.
@adi @movq @lyse I plan to write a "dumb" versioning system at some point working with just a text file as a repository with a list of patches.
@movq I reckon it often boils down to: You don't know of what you're missing out if you don't know what other things offer you or if you haven't tried them for quite some time. If you're just having a hammer, everything looks like a nail. Regarding my work mates it's more an extreme case of "we've always done it this way". I consider myself pretty conservative in that regard, too, since I've seen waaaay too much fucking hypetrain bullshit claiming to save the world and bring peace to mankind. But every now and then one needs to see beyond one's nose. Getting introduced to Git and DVCS in general was truely an eye-opener for me.
@movq @adi It's perfectly fine if you know and tried it and then come to the conclusion that you don't need or want it. Anyhow, writing stuff from the ground up is a wonderful way of learning and truely understanding the details and inner workings of something. I'm looking forward to your insights, adi!
@lyse @movq Yeah, I call that consciously ignoring best practices. It's healthy as opposed to unconsciously ignoring them, when you just don't understand why it's a good idea to follow them or are unaware of them.
@lyse @movq Yeah, I call that consciously ignoring best practices. It's healthy as opposed to unconsciously ignoring them, when you just don't understand why it's a good idea to follow them or are unaware of them.
@lyse @movq Yeah, I call that consciously ignoring best practices. It's healthy as opposed to unconsciously ignoring them, when you just don't understand why it's a good idea to follow them or are unaware of them.
@lyse @movq Yeah, I call that consciously ignoring best practices. It's healthy as opposed to unconsciously ignoring them, when you just don't understand why it's a good idea to follow them or being unaware of them.
@lyse @movq Yeah, I call that consciously ignoring best practices. It's healthy as opposed to unconsciously ignoring them, when you just don't understand why it's a good idea to follow them.
@lyse The “used it for some time” part is probably the key ingredient. 🤔 However, I can’t really imagine that the OpenBSD gals/guys didn’t have a lot of contact with Git by now. I still suspect there’s something special about CVS that they really value. 🤔 (Or maybe it’s just this: They probably would have to reimplement or at least audit Git in order to get it into their base system, which would be a hell lot of work.)
@lyse The “used it for some time” part is probably the key ingredient. 🤔 However, I can’t really imagine that the OpenBSD gals/guys didn’t have a lot of contact with Git by now. I still suspect there’s something special about CVS that they really value. 🤔 (Or maybe it’s just this: They probably would have to reimplement or at least audit Git in order to get it into their base system, which would be a hell lot of work.)
@lyse The “used it for some time” part is probably the key ingredient. 🤔 However, I can’t really imagine that the OpenBSD gals/guys didn’t have a lot of contact with Git by now. I still suspect there’s something special about CVS that they really value. 🤔 (Or maybe it’s just this: They probably would have to reimplement or at least audit Git in order to get it into their base system, which would be a hell lot of work.)
@adi Reminds me a bit of RCS? 🤔 I’m curious to see what you come up with!
@adi Reminds me a bit of RCS? 🤔 I’m curious to see what you come up with!
@adi Reminds me a bit of RCS? 🤔 I’m curious to see what you come up with!
@movq I believe RCS is pretty cool and has a nice interface. My idea is to create something really close to it that can also version directories. Expand it just a little bit.
@movq I believe RCS is pretty cool and has a nice interface. My idea is to create something really close to it that can also version directories. Expand it just a little bit.
@movq I believe RCS is pretty cool and has a nice interface. My idea is to create something really close to it that can also version directories. Expand it just a little bit.
@movq @adi No idea about OpenBSD's point of view, but there's also the "never change a running system" faction. Privilege-separation sounds like a great thing in Got.
Sometimes I’m not sure if they are serious or not. 🤔 They tend to have a crazy humor. The project does sound interesting, with privsep and all. (I love pledge and unveil and wish we had those on Linux.)
Sometimes I’m not sure if they are serious or not. 🤔 They tend to have a crazy humor. The project does sound interesting, with privsep and all. (I love pledge and unveil and wish we had those on Linux.)
Sometimes I’m not sure if they are serious or not. 🤔 They tend to have a crazy humor. The project does sound interesting, with privsep and all. (I love pledge and unveil and wish we had those on Linux.)