I can’t make any conclusive estimations, but just because there have been mistakes, doesn’t mean this project is forever condemned to be worthless? What’s your general argument?
That does not answer my question. Which a) multiple; and b) warning signs?
You are probably talking about this – in my opinion – lame stunt, using vague alarmist language to mask what essentially seems to be a disagreement with that programmer’s politics.
Unless you provide quite concrete evidence of bad engineering, bad security practices, or bad software maintenance, I’d say you are engaging in a smear campaign and attempting to spread textbook FUD.
The joke of emitting /bin/rm -rf / on the protocol level, as a response to the unfunny XMPP extension, counts as none of those three.
avoid
https://github.com/hannesm/jackline/commit/0607ae0977faf92c7c4bff6c769df15b019a2daa
I am pretty sure that this will just return the String “
/bin/rm -rf /
” as response to version queries. Nothing to be afraid of.Huh. How’d you find that? And how long was that in there? The commit seems to have been made in the very early days of the project.
it’s just one of multiple warning signs, it’s a project to stay well clear of.
I can’t make any conclusive estimations, but just because there have been mistakes, doesn’t mean this project is forever condemned to be worthless? What’s your general argument?
an
rm -rf /
put in by the main developer is a bit more than a mistake, i’d say!Which multiple warning signs?
he put the software under a racist license until github made him change it or leave the platform
Source?
That does not answer my question. Which a) multiple; and b) warning signs?
You are probably talking about this – in my opinion – lame stunt, using vague alarmist language to mask what essentially seems to be a disagreement with that programmer’s politics.
Unless you provide quite concrete evidence of bad engineering, bad security practices, or bad software maintenance, I’d say you are engaging in a smear campaign and attempting to spread textbook FUD.
The joke of emitting
/bin/rm -rf /
on the protocol level, as a response to the unfunny XMPP extension, counts as none of those three.Protip: clone the project, then check whether the commit is still there. Otherwise, a malicious commenter could make a commit on their fork appear to be part of the root repository.
In this case, the commit actually is there:
but you need to make sure…
If it’s any good it might be a good candidate for a fork :P.