abemassry
commented
10 years ago Yes I apologize, I haven't updated wsend in a while and the github url change has affected this project because I had hardcoded the github urls in and had not set up the proper redirection. Thanks for your support and enthusiasm for this project. It really makes me feel like I'm working on this for a purpose when people use my projects.
I've tested this and 708cf21aabf726eda2d9d48b0c31ddcc87e34a9a fixes the install problem.
The auto update function in wsend should follow future redirects, and I will have to periodically check the install scripts to make sure they work. I plan on puting this into a package manager in the future. I started on node-wsend and it updates through npm but it's missing some functionality such as the delete command and the list command. I would like to work on this if I can find the time. The bash script and the node installable are problematic if the same user on the same system trys to install both at the same time.
Sorry for the long reply. Thanks for your feedback and the problem should be all fixed up!
-Abe
As a followup to my issue on wsend-gpg, I'm now having troubles with wsend's install/update scripts.
I updated wsend-gpg with the corrected code and tried to invoke, but when it calls wsend it remarks about a new version being available and chokes. I rm'ed the entire .wsend directory and ran the "two-line install" command from readme.md, but all the files created (version, update.sh, README.md, etc) were html saying "400 bad request / your browser sent a request that this server could not understand"
This update mechanism is rather brittle!