Yesterday I’ve released sanguinews v0.47 and this release marks the end of alpha stage. It doesn’t mean that the software is bug free. It means that I am quite happy with it and it should be able to provide desired results. If there are some bugs(and I presume that there are) – I don’t know about them at the moment. So, I will need your help. Use it, test it, inform me of any strange behavior. Bugs need to be crushed!
In the meantime, I will be improving the “progressbar” feature. Currently it displays only the average speed. I will be adding “ETA” and some kind of actual, moving progress/status bar. One more thing that I would like to see in my program is the capability to tweak headers. I am fan of Gentoo distribution. I like tinkering with the system and I think that a user should have as much freedom and options as it’s possible. Usenet’s standards include quite a lot of headers. Some are required, some are taken by usenet providers, but there are some that could be used, for any reason, by us. I will make sure that there is an easy way to change them.
What I will do after that? No idea. Time will tell, but at the moment I am still having fun and it means that I will continue improving this particular project of mine.
I didn’t want to do this, but scripting languages aren’t as good for pure computing as C. After spending more than 10 hours running various benchmarks, I’ve rewritten yencoding function in inline C code. As much as I hate debugging C problems, it gives 3500% increase in performance compared to the pure ruby solution. So, it was definitely worth it.
Update to the new version via Github.
Thank you for your feedback everyone. I have revamped the code behind the upload scheduling and have achieved much better upload performance. The new version(0.44) is available on Github now. Please keep in mind that I’ve updated nzb gem also. Version 0.2.1 is required now. The code behind gem version check isn’t working at the moment, so you will need to reinstall the gem yourself.
As always, feedback is welcome.
After I’ve added newsmangler’s support to my script, I was thinking that I don’t like newsmangler that much. It has no SSL support and it should be a major turn down for anyone, who is security conscious. I don’t want to send my password in a plain text. What about you?
But I didn’t want to learn python just be able to fix this thing myself. I decided to write something similar, but in ruby. And this way sanguinews was born. Feel free to test it and leave some feedback.
Installation is simple. First install nzb library:
gem install nzb
And you will need one other gem:
gem install parseconfig
Then get the latest code from the github:
git clone https://github.com/tdobrovolskij/sanguinews.git
Copy sample.conf to your home directory:
cp sample.conf ~/.sanguinews.conf
Adjust it as needed and run. It accepts pretty much the same options as newsmangler does. It should be compatible with the latest version of my script – v0.85.
If you notice any bug – just leave a comment here or on the github.
P.S. If you are unfamiliar with git, you need to be aware that you need to run git pull inside the projects directory to update the code. Something like this:
cd sanguinews && git pull
Many people have asked me to add the option to upload files automatically with newsmangler. I thought that this is a great idea and decided to implement it in the next release. So, in the new(0.80) version, you’ll see two new options -U(upload) and -X(path to newsmangler executable). They should not cause any problems, if you are familiar with the script already. In case you aren’t, you could always check the detailed guide prepared by my friend. Continue reading
I just want to let you know that the rarnpar is now available also on github. You can download the latest version with:
git clone https://github.com/tdobrovolskij/rarnpar.git
I am also licensing the script under GPL v2. Feel free to modify it.
I bring you a new rarnpar release with config file support, because I’ve promised this feature in comments to the previous version and because I think that this feature could really prove useful to advanced users.
The code behind this addition is really simple:
If you are like me, you have some scripts which report to you via email. Most of the time the report is just a simple text, but sometimes you will want to receive a file(f.e. a screenshot).
It isn’t the bad idea per se, but emails travel unencrypted through the Internet. As you know, NSA and other bastards are there to gather all the data which passes through. Therefore it’s a good idea to encrypt everything you send. I won’t tell you how to encrypt your personal email. It’s kinda simple task and multiple guides exist. I would like to share with you a way to encrypt an output from your script, which will be passed to sendmail.
I am using sendmail, not mailx, because you can find it on almost every system, much like vi. This how-to is based on following post: http://backreference.org/2013/05/22/send-email-with-attachments-from-script-or-command-line/ . So I will tackle two problems at once here: files and encryption. Of course, if attachments aren’t needed, it is even simpler. Continue reading
When I was asked to add an option to generate random passwords during the raring process, I was quite sceptical. It didn’t appear to me that someone would use such a feature, but after reading the following explanation, I decided to add this option and now it’s up to you, if you will use it or not.
By the way, there is also a small bug fix. Some users were complaining that directories in –subdir mode have .tmp suffix. You shouldn’t see this suffix now. Continue reading
After getting some feedback for my previous rarnpar release(version 0.7), I was actively implementing new features and fixing some old bugs. There were some releases during that time, which were accessible to anyone via the most recent version link.
If you did get the version 0.71-0.74 during this time, you could download the updated script(v0.75) now.
I have fixed the bug with unnecessary .nfo file creation and I have added two additional options: –par and –rar. You will be able to add some additional files for raring and/or paring. Like, for example, –par *.sfv to add a dynamically created .sfv file(keep in mind that you won’t be able to add dynamically created files to a rarset as it makes no sense in almost all cases).
Full diff looks like this: Continue reading