Jul 21, 2022, 06:03 am
(This post was last modified: Jul 21, 2022, 06:05 am by Fant0men. Edited 1 time in total.)
Greetings, fellow pirate degenerates. Long time no see.
I've run into an interesting problem.
I like making shell scripts, and I like bundling them with my torrents (they are usually related to the content of the torrent). For example, when I upload FLAC discographies, I'll bundle the script I use to manage my FLAC library in the hope that it will be useful to someone else. Or when I uploaded my HEVC / x265 Bluray rips, I bundled the ripping script. Cause the plan was to start a community that could do batch ripping of movies together to flood TPB with high quality rips.
When sharing scripts with people online, I had the nasty habit of using Pastebin links, and I set those to expire because I don't want old and inferior versions of my scripts to stick around (I frequently update and improve them). Pastebin was a hassle, cause every time I updated the scripts, I needed to create new Pastebin links. Sometimes I fucked up and didn't open an Incognito window in Chrome to make the links, so they referred back to my actual Pastebin account (oops). I try to avoid that cause I don't want to get doxxed.
This week, I decided it was time to stop dicking around with Pastebin and just upload my scripts to GitHub (which I have done). This is more comfy, cause not only are the links persistent, whenever someone visits them they automatically get the latest version of everything. Plus, I can update the whole Git repo (containing all my scripts) with a single command (I created a function in my ~/.bashrc for that). I have the scripts I want to share hard-linked from my ~/bin directory to a sub-directory, which is my local Git repo. I tried using symbolic links at first, but apparently those don't play nice with Git. Lesson learned.
Anyway... Now my problem is that I want to somehow reach all the people that got my scripts from my old torrents. I want them to be able to find and access the updated versions. How would I go about this? I'm sure there's an interesting and creative solution to this conundrum, and I would appreciate your input.
I think I will put a link to my GitHub repo in future torrents, instead of bundling the actual script files.
I've run into an interesting problem.
I like making shell scripts, and I like bundling them with my torrents (they are usually related to the content of the torrent). For example, when I upload FLAC discographies, I'll bundle the script I use to manage my FLAC library in the hope that it will be useful to someone else. Or when I uploaded my HEVC / x265 Bluray rips, I bundled the ripping script. Cause the plan was to start a community that could do batch ripping of movies together to flood TPB with high quality rips.
When sharing scripts with people online, I had the nasty habit of using Pastebin links, and I set those to expire because I don't want old and inferior versions of my scripts to stick around (I frequently update and improve them). Pastebin was a hassle, cause every time I updated the scripts, I needed to create new Pastebin links. Sometimes I fucked up and didn't open an Incognito window in Chrome to make the links, so they referred back to my actual Pastebin account (oops). I try to avoid that cause I don't want to get doxxed.
This week, I decided it was time to stop dicking around with Pastebin and just upload my scripts to GitHub (which I have done). This is more comfy, cause not only are the links persistent, whenever someone visits them they automatically get the latest version of everything. Plus, I can update the whole Git repo (containing all my scripts) with a single command (I created a function in my ~/.bashrc for that). I have the scripts I want to share hard-linked from my ~/bin directory to a sub-directory, which is my local Git repo. I tried using symbolic links at first, but apparently those don't play nice with Git. Lesson learned.
Anyway... Now my problem is that I want to somehow reach all the people that got my scripts from my old torrents. I want them to be able to find and access the updated versions. How would I go about this? I'm sure there's an interesting and creative solution to this conundrum, and I would appreciate your input.
I think I will put a link to my GitHub repo in future torrents, instead of bundling the actual script files.
![[Image: 78UySNh.gif]](https://i.imgur.com/78UySNh.gif)