@defor More cooks are always welcome if their cooking is good!
To address your points:
1. Indeed;
2. I get that, but as I tried explaining to him, this
truly was only about MacSurf from the beginning, because I wanted to alert of a sudden, seemingly-inexplicable project status change, including both binary and source code, and potentially what I perceived as a security concern; I was only sounding the alarm, since logins etc. were involved in testing the project. Without any info or context, it all seemed too suspicious;
3. That's pretty much what I did (but admittedly with more emotion), as the screenshots were only of text, and the banter is what allowed the matter to be clarified and ultimately resolved. (Otherwise it still wouldn't have been.) Not all conflict is bad, some difficult conversations are necessary so that we are able to sort out problems and misunderstandings like this one. Also, there is a big reason I chose screenshots over just, say, linking to that thread: it is because, at that time, I didn't know if my account got compromised, because if so, my posts could have been deleted, so the screenshot route was taken as a preventative measure to retaining the alarm.
Well, that's it in a nutshell. Nonetheless, I'm glad now we have all the info, and this was all sorted out. I hope MacSurf can resume progress eventually in a normal fashion like before.
MacSurf is definitely being currently very helpful at closing gaps left behind by
WaMCom Mozilla 1.3.1 (and its successors like
Classilla). I think no one expects to do reliable netbanking here, though, so no problems there. It definitely would be "the final step" only,
if ever, and would require the most scrutiny before deemed fit for such a purpose.