├── img ├── 菜市场.jpg ├── 初剑锋不懂离散数学.jpg ├── 初剑锋欺压女生1.jpeg ├── 初剑锋欺压女生2.jpeg ├── 形势与政策抓作弊.jpg ├── 初剑锋的qq评价2.jpeg ├── 初剑锋的qq评价3.jpeg ├── 初剑锋的知乎评价1.jpeg ├── 初剑锋的知乎评价2.jpeg ├── 初剑锋的知乎评价3.jpeg └── 初剑锋的qq空间评价1.jpeg ├── xueshu ├── 异构信任域的跨域授权_孟欣.pdf ├── IBE体系的密钥管理机制_胡亮.caj ├── IBE体系的密钥管理机制_胡亮.pdf ├── Web服务器隐秘破袭技术_初剑峰.caj ├── 基于信任服务的IBE体系_初剑峰.caj ├── 基于信任服务的IBE系统_胡亮.pdf ├── 基于身份的商品双重防伪机制_胡亮.pdf ├── 单向性策略与AES密钥生成算法的改进_胡亮.pdf ├── 基于信任服务IBE体系的权限管理_胡亮.pdf ├── 基于鼠标移动轨迹的真随机数产生方法_胡亮.pdf ├── 基于抵抗故障引入攻击的RC4算法的改进_胡亮.pdf ├── 基于群密钥协商的无线传感器网络签名协议_于斌斌.pdf ├── 改进的国际数据加密算法的子密钥扩展算法_胡亮.pdf ├── 一种改进的适用于多服务器架构的匿名认证协议_余宜诚.pdf └── 适用于无线传感器网络密钥管理LEAP方案的改进与优化_余宜诚.pdf ├── doc ├── 导师评价网部分评价 ├── 2016年网络协议分析实验考试的遭遇 └── 就2018年初剑峰巡考事件致吉林大学公开信 ├── README.md └── LICENSE /img/菜市场.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/img/菜市场.jpg -------------------------------------------------------------------------------- /img/初剑锋不懂离散数学.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/img/初剑锋不懂离散数学.jpg -------------------------------------------------------------------------------- /img/初剑锋欺压女生1.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/img/初剑锋欺压女生1.jpeg -------------------------------------------------------------------------------- /img/初剑锋欺压女生2.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/img/初剑锋欺压女生2.jpeg -------------------------------------------------------------------------------- /img/形势与政策抓作弊.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/img/形势与政策抓作弊.jpg -------------------------------------------------------------------------------- /img/初剑锋的qq评价2.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/img/初剑锋的qq评价2.jpeg -------------------------------------------------------------------------------- /img/初剑锋的qq评价3.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/img/初剑锋的qq评价3.jpeg -------------------------------------------------------------------------------- /img/初剑锋的知乎评价1.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/img/初剑锋的知乎评价1.jpeg -------------------------------------------------------------------------------- /img/初剑锋的知乎评价2.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/img/初剑锋的知乎评价2.jpeg -------------------------------------------------------------------------------- /img/初剑锋的知乎评价3.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/img/初剑锋的知乎评价3.jpeg -------------------------------------------------------------------------------- /img/初剑锋的qq空间评价1.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/img/初剑锋的qq空间评价1.jpeg -------------------------------------------------------------------------------- /xueshu/异构信任域的跨域授权_孟欣.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/xueshu/异构信任域的跨域授权_孟欣.pdf -------------------------------------------------------------------------------- /xueshu/IBE体系的密钥管理机制_胡亮.caj: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/xueshu/IBE体系的密钥管理机制_胡亮.caj -------------------------------------------------------------------------------- /xueshu/IBE体系的密钥管理机制_胡亮.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/xueshu/IBE体系的密钥管理机制_胡亮.pdf -------------------------------------------------------------------------------- /xueshu/Web服务器隐秘破袭技术_初剑峰.caj: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/xueshu/Web服务器隐秘破袭技术_初剑峰.caj -------------------------------------------------------------------------------- /xueshu/基于信任服务的IBE体系_初剑峰.caj: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/xueshu/基于信任服务的IBE体系_初剑峰.caj -------------------------------------------------------------------------------- /xueshu/基于信任服务的IBE系统_胡亮.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/xueshu/基于信任服务的IBE系统_胡亮.pdf -------------------------------------------------------------------------------- /xueshu/基于身份的商品双重防伪机制_胡亮.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/xueshu/基于身份的商品双重防伪机制_胡亮.pdf -------------------------------------------------------------------------------- /xueshu/单向性策略与AES密钥生成算法的改进_胡亮.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/xueshu/单向性策略与AES密钥生成算法的改进_胡亮.pdf -------------------------------------------------------------------------------- /xueshu/基于信任服务IBE体系的权限管理_胡亮.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/xueshu/基于信任服务IBE体系的权限管理_胡亮.pdf -------------------------------------------------------------------------------- /xueshu/基于鼠标移动轨迹的真随机数产生方法_胡亮.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/xueshu/基于鼠标移动轨迹的真随机数产生方法_胡亮.pdf -------------------------------------------------------------------------------- /xueshu/基于抵抗故障引入攻击的RC4算法的改进_胡亮.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/xueshu/基于抵抗故障引入攻击的RC4算法的改进_胡亮.pdf -------------------------------------------------------------------------------- /xueshu/基于群密钥协商的无线传感器网络签名协议_于斌斌.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/xueshu/基于群密钥协商的无线传感器网络签名协议_于斌斌.pdf -------------------------------------------------------------------------------- /xueshu/改进的国际数据加密算法的子密钥扩展算法_胡亮.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/xueshu/改进的国际数据加密算法的子密钥扩展算法_胡亮.pdf -------------------------------------------------------------------------------- /xueshu/一种改进的适用于多服务器架构的匿名认证协议_余宜诚.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/xueshu/一种改进的适用于多服务器架构的匿名认证协议_余宜诚.pdf -------------------------------------------------------------------------------- /xueshu/适用于无线传感器网络密钥管理LEAP方案的改进与优化_余宜诚.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chengyumeng/chujianfeng/HEAD/xueshu/适用于无线传感器网络密钥管理LEAP方案的改进与优化_余宜诚.pdf -------------------------------------------------------------------------------- /doc/导师评价网部分评价: -------------------------------------------------------------------------------- 1 | https://mysupervisor.org/viewtopic.php?f=326&t=36391&sid=cf61efc8265a6824751e905229ac18d8 2 | 3 | 4 | 自证认识导师：长的又肥又难看眼睛又小又猥琐 5 | 6 | 学术水平：没有，吹牛逼到时很厉害 7 | 8 | 科研经费：不知道 9 | 10 | 学生补助：很少 11 | 12 | 师生关系：差，瞧不起别人，溜须院长到是很在行 13 | 14 | 工作时间：加个P 15 | 16 | 学生前途：在他手下就是废 17 | 18 | 19 | 自证认识导师：爱吹牛 20 | 21 | 学术水平：不存在的 22 | 23 | 师生关系：不尊重学生，用各种方式恶心人 24 | 25 | 工作时间：有没有事所有人都要整整齐齐 26 | 27 | 学生前途：浪费学生时间，耽误前途 28 | 29 | 30 | 自证认识导师：开局一张嘴，经费全靠吹 31 | 32 | 学术水平：吹牛逼一流 33 | 34 | 科研经费：不清楚 35 | 36 | 师生关系：你拿他当亲儿子，他却不把你当亲爹 37 | 38 | 学生前途：以后过日子全靠吹牛逼 39 | 40 | 41 | 自证认识导师：WC组合中的C，他只会玩小黑 42 | 43 | 学术水平：没有学术水平 44 | 45 | 科研经费：全靠骗 46 | 47 | 学生补助：500 48 | 49 | 师生关系：垃圾，没有不骂傻逼的，传对研究生还行是谣传 50 | 51 | 工作时间：加班一天不来-200 52 | 53 | 学生前途：不能实习，耽误学生前途 54 | 55 | 56 | 自证认识导师：计院四大名捕之一 57 | 58 | 学术水平：垃圾一个, 本科生的课程都讲不明白, 有问题问他回答都是似是而非, 狗屁不懂. 59 | 60 | 师生关系：没有任何一个吉大计院学生喜欢他, 区别只是讨厌他和恶心而已. 61 | 62 | 63 | 学术水平：自己要吹上天了，其实什么也不会 64 | 65 | 师生关系：为人奇葩，人见人烦 66 | 67 | 学生前途：毁人不倦 68 | 69 | 70 | 学术水平：学术水平低下，讲课很烂，计算机学院最zz的老师没有之一。 71 | 72 | 科研经费：相对充足。 73 | 74 | 师生关系：师生关系差，不建议选他当导师。 75 | 76 | 学生前途：学生前途较差 77 | 78 | 79 | 学术水平：这个不太清楚，但计网教的确实差。。 80 | 81 | 科研经费：不清楚，给两星 82 | 83 | 师生关系：据说对研究生还行，但是老师作风奇葩。。 84 | 85 | 学生前途：emmmmm。。。 86 | 87 | 88 | 学术水平：垃圾，不要报，什么都不会，计网都讲不明白 89 | 90 | 师生关系：唉，老师有点儿神经质，可能压力太大了 91 | -------------------------------------------------------------------------------- /doc/2016年网络协议分析实验考试的遭遇: -------------------------------------------------------------------------------- 1 | 说一个我室友的经历吧。 2 | 3 | 2016年网络协议分析实验的时候，他因为一些疏忽，忘记了身上携带了手机，到考试时间过半才发现。 4 | 5 | 因为这门课的考试是开卷考试，非常简单，而且考试已经开始了，所以他也就没有再去管手机的事情。 6 | 7 | 本来答题过程非常顺利，预计他提前半个小时就能交卷了。 8 | 9 | 之后初剑峰老师来巡视。一进门就表现的与其他老师不一样。有些同学身后会空出一排，他就站到同学身后，反复弯腰探头往别人抽屉看，已经影响了部分同学答题。 10 | 11 | 之后走到他旁边的时候，看到他裤兜有凸起，便要求他取出裤兜的东西。 12 | 13 | 当初老师发现是手机之后，就强制要求他交卷，并将他的试卷作废。同时拿了一张表格，说他违纪，强制让他签字。 14 | 15 | 我室友向他解释手机是无意带在身上的，而且他没有使用过，另外考试期间手机是静音模式，没有发出任何声响，没有干扰别的同学。 16 | 17 | 但是他以自己是这科主考官为由威胁他，必须签字，态度非常恶劣。 18 | 19 | 反倒是扭头找考场别的老师签字的时候笑容满面，态度极其和蔼，语气非常亲切。 20 | 21 | 短短几秒钟态度能变化这么大，我当时看的也很震惊。因为他是该科目主考官，试卷会经过他的手批阅，室友无能为力，所以只好签了字。 22 | 23 | 除他之外其实当时在另一个考场也有跟他遭遇类似的同学，但是因为没有得到这位同学的许可，就不单独提他了。 24 | 25 | 之后他们的处理结果是，试卷作废，并给他们记上了校级处分。 26 | 27 | 我室友本身的综合成绩很优秀，即便是在这一科记0分的情况下，大四上学期的综合排名依然达到了保研名次。但是因为挂科的原因，遗憾的与保研失之交臂，四年的辛苦努力泡汤了。 28 | 29 | 说出这段遭遇，不是想辩解什么，因为后期我们也了解到了，学校是有相关规定的。所以，对于处理结果没有什么好说的。但是我们想说的是： 30 | 31 | - 规定是死的，人是活的。学校制定的相关规定是为了端正考场纪律，是为了学生好，这样的出发点是好的。但是对于一门难度极低，开卷的考试，学生因为无意携带手机，并且没有抄袭，没有影响他人的情况下，不假思索的按照规定办事，是否有违了当初制定规定的初衷？如果所有老师都只是规则执行者，没有自己的思考，那他究竟是暴力机关人员还是教书育人的园丁呢？对于这种事关学生一辈子的事情，究竟是应该仔细思考了再办，还是简简单单地按照规定办？这样轻浮的决定，可能会毁了一个学生的一辈子。这件事学校和这位老师都应该好好思考。 32 | - 初剑峰老师与众不同的监考风格，确实影响了许多同学的考试，希望他日后能改正（比如反复弯腰探头观察考生）。而且，我们也因为这件事也跟相关的学长聊过，大家都认为，他的初衷并不像是教书育人，而只是泄一己之私欲。当然，这种事大家谁都不可能有证据，只有初老师自己清楚。这只能说是大家作为成年人，在与这位老师的接触中的感受。但是如果属实的话，他觉得这位老师确实违背了教师的职业道德。至少我们在与其他老师的接触中，从来没有这种感觉。 33 | 为了防止杠精，我再次声明一下，我室友没有作弊，考试过程中没有动过自己手机，手机也没有响过。我们大伙儿包括这位室友对处理结果没有什么需要辩解的，毕竟已经过去了两年了，只能说我们都确实感到寒心。现在看到有学弟学妹碰到了类似的、甚至更无理的情况，我们替他们感到不公平，也感到痛心，不想让他们重蹈覆辙。同时，这也是我们对于这一系列类似事件的一些想法。当然，对于抄袭肯定是零容忍。但是类似上文提到的事件以及近期发生的这种情况，还是希望老师本着为学生好的初衷，保持教育为主，惩罚为辅的原则来处理。 34 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # 初剑峰 2 | 本项目用于收集吉林大学计算机科学与技术学院初剑峰老师一切侵犯学生尊严、违背教师职业道德的证据 3 | 4 | ## 主要收录 5 | - 吉林大学学生对初剑峰的吐槽 6 | - 初剑峰黑历史的音频、视频和图片资料 7 | - 各个网络社区（QQ空间、朋友圈、知乎、贴吧）对初剑峰其人的讨论 8 | 9 | ## 帮助更新本项目的方式 10 | - 提交 PR 11 | - 邮箱 792400644@qq.com 12 | - 微信公众号 中关村男子图鉴 pod1024 13 | 14 | ## 目录 15 | 16 | #### 讨论帖 17 | - [如何看待吉林大学计算机学院初剑峰老师在监考和巡考时的夸张行为?]( https://www.zhihu.com/question/39425588) 18 | - [软件2015级考形策初剑峰"抓作弊"始末](http://tieba.baidu.com/p/5158100356?pid=108043827128&cid=0#108043827128) 19 | - [想考初剑峰的研究生](http://tieba.baidu.com/p/4054818068?pid=76117789020&cid=0#76117789020) 20 | - [导师评价网部分评价](https://mysupervisor.org/viewtopic.php?f=326&t=36391&sid=cf61efc8265a6824751e905229ac18d8 21 | ) 22 | 23 | #### 文章 24 | - [就2018年初剑峰巡考事件致吉林大学公开信](https://mp.weixin.qq.com/s/dR9Ngvv3PNTfby5_sMig5Q) 25 | 26 | #### 资源 27 | - [社交网络截图列表](https://github.com/chengyumeng/chujianfeng/tree/master/img) 28 | 29 | #### 匿名者 30 | ###### [置顶] 来自同窗一封邮件 31 | 32 | 亲爱的同学： 33 | 34 | 你好！我是吉林大学20XX级计算机学院网络安全专业的你的校友。 35 | 36 | 在阅读你呼吁大家批斗初剑峰的公众号文章时，说实话我的内心是汹涌澎湃的。 37 | 38 | 很高兴有同学愿意站出来去谈一谈这件事，而不是像我们当初逆来顺受，觉得忍过这几年就过去了的心态。 39 | 40 | 再次我谨代表我个人对你表示真挚的谢意。 41 | 42 | 但这个文章在我们当初的班群里传阅后，我的同学们说你这个里面有骂人的如“初剑峰滚出考场”字样的文化衫，说你这个行为成不了气候。 43 | 44 | 我看到我的同学因为有人真的愿意站出来而说风凉话的行为感到羞愧。 45 | 46 | 但在我仔细审视后，发现他们说的也不无道理，但我不想就这样让这件事就这样冷下去，毕竟初剑峰素行不良，确实愧为教师。 47 | 48 | 因此我谨以我个人向你提出几点小建议： 49 | 50 | 1.在搜集初剑峰的“黑历史”时，一定要有确凿的证据，可以实锤那种，我们需要有力的能对他造成影响的东西， 51 | 52 | 而不是各种谩骂或者不具有鲜明证据的言语，在这种事上我更坚信质量才是最重要的， 53 | 54 | 不要让一两个看起来不那么有说服力的流言蜚语而降低了你整个证据库的可信度。 55 | 56 | 2.我们要做正义的化身，或者说弱者的保护伞，但还是不要做键盘侠， 57 | 58 | 我希望我们做的不是以其人之道还治其人之身，那样我们最后也和初剑峰一样的水平， 59 | 60 | 我认为像这种吐槽级别的，或者类似于文化衫抗议的这种，这种行为还是有待商榷。 61 | 62 | 3.我希望在我们呼吁同学们“揭竿而起”时，能更考虑好学生们的利弊，希望能把对同学们的负面影响降到最低，要避免赔了夫人又折兵的现象。 63 | 64 | 以上是我个人看到文章后第一时间想的几个小点，不奢望被采纳，但是希望程同学能有所借鉴。兽人，永不为奴！ 65 | 66 | 此致 67 | 68 | 抱拳！ 69 | 70 | ###### 看到你的文章了，我想说一点发生在我身上的事。 71 | 72 | 当时是大一的学生，听说过了学长学姐们说过的初贱疯的“光辉事迹”，并没有引起我的担心，天真的以为这辈子都不会和他有交集. 73 | 74 | 没想到考试的时候，因为桌子上几个乱涂的草稿是“数字”，初贱疯就判定我在高数考试中作弊. 75 | 76 | 先不说高等数学这个科目，桌子上抄一个公式不会做题还是用不出来. 何况经过我的努力辨认，桌子上的那几个数字是别人随手打的草稿！ 77 | 78 | 就因为几个乱涂的草稿是“数字”，初贱疯就可以判定我在高数考试中作弊？ 79 | 80 | 年久失修的逸夫阶梯教室，干干净净的桌子很难找到，更不要说桌子皮撕起来写到木头上根本擦不掉. 81 | 82 | 当时我还是个大一刚入学的学生，这是我大学面临的第一个重要考试，我觉得没有作弊仅仅是个误会， 83 | 84 | 所以我积极和他解释，并且要求调取监控自证清白，但是初贱疯不同意，坚持要收走我的试卷与学生证身份证， 85 | 86 | 甚至在我努力解释的时候直接上手抢试卷. 他不走，也不让我正常答题， 87 | 88 | 当然可能他是知道几个毫无意义的数字对非背诵性的科目高数来说毫无意义的. 89 | 90 | 我当时被这个从没想到的意外砸的脑子乱哄哄的，已经忘了将近半小时的撕扯求了初贱疯多少，只记得现在回想起来还会痛苦万分的委屈和无助. 91 | 92 | 语文不好，这么久了我在尽量避免谈这件事，回想起来还是很难过，只能尽量还原出当时的场景。 93 | 94 | ###### 11 级吉大毕业生，不要公开我的姓名 95 | 96 | 我本科同学上他的实验课，上了个厕所，然后他正好点名，我室友不在，回来和他解释他不听，算了旷课没到 97 | 98 | ###### 对初剑峰的课堂评价 99 | 100 | 初监考，不由分说拿走多名学生试卷，而后对着桌子拍照，并没有给出任何说法，难道这也是正常监考范围的一部分？ 101 | 102 | 初的计算机网络，一根网线能干多少事儿想必上过他的课的人都有所耳闻吧，上课大部分时间在吹， 103 | 104 | 剩下时间里讲课质量极差，毫无逻辑，好多自己都搞不懂，反过来问学生，稀里糊涂就跳过。 105 | 106 | 上课最常说：你们不用来上课，肯定过不了。难道计算机学院就指望这样的人培养吉大的未来么？ 107 | -------------------------------------------------------------------------------- /doc/就2018年初剑峰巡考事件致吉林大学公开信: -------------------------------------------------------------------------------- 1 | 这封信的受众，包含吉林大学计算机学院学生、监考、教职人员、初剑峰在内所有“吉大人”。 2 | 3 | 4 | 5 | 关于初剑峰其人在巡考、教学阶段种种不尊重学生、有悖师德的行径，不是本文的重点，任何措辞都没有朋友圈和QQ空间那一张张照片具体形象，考场上其干扰学生正常作答，课堂迟到早退、不备课、吹牛逼等行为和他接触过的学生都有感受。 6 | 7 | 8 | 9 | 我是2013年入学吉林大学，当时听大三大四的学长说，等过两年，你们会接触到一个叫“初剑峰”的痞子。按照这个计算，至少在2010年，初剑峰就开始干扰正常的教学和考试秩序了。现在是2018年，8年过去了，抗战都打完了初剑峰还在祸害吉大计算机的学生！ 10 | 11 | 12 | 13 | 今天有吉大学生联系我提供可以制裁初剑峰的材料，我为这一届的吉大学生感到骄傲，他们终于知道要反抗了，终于知道不要逆来顺受了！相比而言，我们这一届，真怂。 14 | 15 | 那这样，我们不如索性把这件事搞大。 16 | 17 | 18 | 19 | 无论是李元元先生，还是魏晓辉先生，我也不知道你们能不能看到这篇文章，不过按照我在知乎写“吉大运动会强制大舞”的回答的影响力，起码很多导员能看到哈？我个人的诉求如下： 20 | 21 | 22 | 23 | 吉林大学计算机学院必须承诺停止今后初剑峰参与巡考和本科生教学 24 | 25 | 初剑峰必须在吉林大学官网上发帖道歉 26 | 27 | 28 | 29 | 这两点是我个人的诉求，我发表出来，也希望有和我相同诉求的学弟学妹，和我组成一个团体。不过呢，我想告诉大家，我根本不相信吉林大学能满足我的任何一点要求，所以下面的内容可能才是关键。 30 | 31 | 32 | 33 | 在上述两条要求得不到满足的前提下，我将组织志愿者在未来很多年坚持做下面的事情： 34 | 35 | 36 | 37 | 自2018年8月开始，无论从任何渠道得知初剑峰参与了考试巡考工作，将带着条幅、穿着印有标语的文化衫出现在初剑峰巡考考场外，并组织吉大反感初剑峰行为的学生团购印有“初剑峰滚出考场”字样的文化衫，在考试期间整齐划一的着装。 38 | 39 | 鼓励在职场有一定发展的人士承诺不与初剑峰及其实验室存在任何工作合作。 40 | 41 | 像本科生宣传拒绝填报初剑峰的研究生，选择其担任教学的课程。 42 | 43 | 鼓励一切和初剑峰有交集的教师和学生，同我匿名举报初剑峰参与社会商业运作（包括但不限于在社会企业内部挂职、收佣金等不符合国家相关管理规定的行为）的行为，并能提供音视频、合同等证据。 44 | 45 | 鼓励一切和初剑峰有交集的学生和教师，向我匿名举报初剑峰违规的科研经费报销的行为，并提供相关证据。 46 | 47 | 鼓励一切和初剑峰有交集的学生和教师，向我匿名举报初剑峰有学术不端的可能性的行为，我也将对初剑峰过去和将来的一切论文、专利等进行复盘，寻找瑕疵。 48 | 49 | 鼓励一切和初剑峰有交集的学生和教师，记录其课堂吹逼的音频和视频，例如，“自吹自擂攻进谷歌内网”这样的行为，我们将把相关音视频通过邮件的形式转发给相关企业的法务和境内媒体。 50 | 51 | …… 52 | 53 | 54 | 55 | 总而言之吧，我的目的不是置初剑峰于死地，我是觉得中国税负如此严重，教育和医疗那么缺钱，就不要把经费花在养着这种人渣的行为上了吧？当然，即使从此以后初剑峰夹着尾巴做人，我也不会觉得咬牙切齿，能够劝人放下屠刀，立地成佛，也是一件功德无量的事情。 56 | 57 | 58 | 59 | 对于上面的举措，作为同样厌倦初剑峰的你，可以做些什么呢？ 60 | 61 | 62 | 63 | 最简单的，像我经常通报初剑峰的不良行径，转发学生吐槽初剑峰的言论。 64 | 65 | 如果你懂法律，那么你可以参与评估我们已经掌握的证据可以对初剑峰制裁到什么程度。 66 | 67 | 如果你懂计算机，你可以帮忙审核初剑峰的论文和专利。 68 | 69 | 如果你懂设计，帮我想想“初剑峰滚出考场”几个字如何设计比较好。 70 | 71 | 如果你懂英语，你可以帮我想想“初剑峰滚出考场”怎么翻译，反正我只能想到“Chu Out”这种翻译啦。 72 | 73 | 如果你不幸和初剑峰在一个实验室，我当然希望你源源不断的像我提供初剑峰的黑料啦。 74 | 75 | 76 | 77 | 坦率的讲，做这些事并不耽误我任何时间，我茶余饭后就做了，如果你愿意做志愿者，我当然欢迎啦，哪怕你只是现在义愤填膺三分热度做了一两个月就抛到脑后，我也觉得很感谢你，不过这件事我肯定会坚持下去的。权当生活的乐趣即可。 78 | 79 | 80 | 81 | 关于一切与初剑峰有关的黑暗料理、评价，我将审核属实、非无脑黑之后，上传到 github 开源项目：https://github.com/chengyumeng/chujianfeng 也欢迎任何人提PR或者在本项目的基础上演绎，但是要注意，本项目的证书是 GPL 2.0，这是一个要求相对严格的证书，希望你遵守规范。 82 | 83 | 84 | 85 | 最后，我们探讨几个逻辑问题。 86 | 87 | 88 | 89 | 不论初老师这次处理适当与否（当事人适当舆论或反映都可以理解，但据我与监考老师了解：巡考没有过错），我们另外4个巡考和初老师应该不是一个作风，却无端被指责需要抓学生达标？ 90 | 91 | 92 | 93 | 这是我很尊重的一位吉大教师的原话，但是我不认同。这位老师想必是能感觉到初剑峰的作风是不妥的，那么你们同朝为官，就是在一条船上，没有监督好初剑峰不要滥用权力，在被舆论甚至谣言指责的时候，也就只能忍着。毕竟四大名捕是以初剑峰为首的，其表现出“带着任务来巡考”来，也就请不要因为牵连到自己而愤怒。 94 | 95 | 96 | 97 | 说实话，虽然初老师手段有点欠考虑，但是没有他的话，考试作弊就更猖獗了 98 | 99 | 100 | 101 | 这是很久以来就有的一种观点，初剑峰的存在，抑制了考试作弊。首先，我根本不认同初剑峰对于考试作弊有什么抑制作用。避免考试作弊的根本途径是让考试不要成为为了考试而考试，不要有各种“提分”，不要让一个四六级都过不了的太子期末考试成绩莫名比我们辛苦考试的学生高一截，老师尽职尽责教学，学生尽职尽责学习和考试。毕竟能考吉大的学生，恐怕高中期间很多人都有过“无监考期末考试”的待遇吧？那时候我们都不作弊，为什么现在作弊了呢？ 102 | 103 | 104 | 105 | 初剑峰一贯藐视考场纪律，甚至比某些作弊的学生还可恶，他并不是在抓作弊，而是在哗众取宠。没有任何数据支持标明初剑峰的存在降低了作弊率，这种言论请经过对照实验，计算两个西格玛置信区间和置信度之后在表达。 106 | 107 | 108 | 109 | 可不可以不抹黑母校？ 110 | 111 | 112 | 113 | 这种观点一直很有趣，今天也是七月七号，我看很多人在朋友圈发说“国耻”什么的。坦率的讲，日本侵略中国使我们中国的耻辱吗？我觉得不是，如果今天的北京，是旭日旗，中国的课堂上，教的是日语，我们中国人，低人一等，那我觉得是国耻。但是我们赶走了日本人啊，盟军赢得了与轴心国集团的战争，那场牺牲了三千五百万中国人的战争，其实是我们值得自豪的事情。 114 | 115 | 116 | 117 | 同样道理，关于抹黑母校。如果初剑峰之流毫无体面而言的角色还能大摇大摆的在吉林大学，我觉得这才是耻辱，这才是抹黑母校。面对不公平和不体面敢于站出来说“不”的人，永远都是母校的骄傲。这种观点不是我自创的，党和国家的教科书就这么教我的。课本上都是用129学生运动之类教育我们要做国家的脊梁，从小学到大学的语文课本的“北大精神”也是这么教育我们的。 118 | 119 | 120 | 121 | 因此说，我很自豪的参与消灭初剑峰的丑恶行为行动。重申一下，我们对初剑峰的不认可，表现在两个方面，一方面是干扰正常的考试秩序，另一方面是扰乱正常的教学秩序。这件事不会随着热度过去而停止的，也许下一次讨论这件事，我可能已经准备好递交给教育部和中纪委以及媒体的材料了吧，在这里致敬崔永元先生！ 122 | 123 | 124 | 125 | 最后呢，阅读原文就是积累初剑峰黑料的 github 仓库，加油吧，亲爱的少年！ 126 | 127 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 2, June 1991 3 | 4 | Copyright (C) 1989, 1991 Free Software Foundation, Inc., 5 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA 6 | Everyone is permitted to copy and distribute verbatim copies 7 | of this license document, but changing it is not allowed. 8 | 9 | Preamble 10 | 11 | The licenses for most software are designed to take away your 12 | freedom to share and change it. By contrast, the GNU General Public 13 | License is intended to guarantee your freedom to share and change free 14 | software--to make sure the software is free for all its users. This 15 | General Public License applies to most of the Free Software 16 | Foundation's software and to any other program whose authors commit to 17 | using it. (Some other Free Software Foundation software is covered by 18 | the GNU Lesser General Public License instead.) You can apply it to 19 | your programs, too. 20 | 21 | When we speak of free software, we are referring to freedom, not 22 | price. Our General Public Licenses are designed to make sure that you 23 | have the freedom to distribute copies of free software (and charge for 24 | this service if you wish), that you receive source code or can get it 25 | if you want it, that you can change the software or use pieces of it 26 | in new free programs; and that you know you can do these things. 27 | 28 | To protect your rights, we need to make restrictions that forbid 29 | anyone to deny you these rights or to ask you to surrender the rights. 30 | These restrictions translate to certain responsibilities for you if you 31 | distribute copies of the software, or if you modify it. 32 | 33 | For example, if you distribute copies of such a program, whether 34 | gratis or for a fee, you must give the recipients all the rights that 35 | you have. You must make sure that they, too, receive or can get the 36 | source code. And you must show them these terms so they know their 37 | rights. 38 | 39 | We protect your rights with two steps: (1) copyright the software, and 40 | (2) offer you this license which gives you legal permission to copy, 41 | distribute and/or modify the software. 42 | 43 | Also, for each author's protection and ours, we want to make certain 44 | that everyone understands that there is no warranty for this free 45 | software. If the software is modified by someone else and passed on, we 46 | want its recipients to know that what they have is not the original, so 47 | that any problems introduced by others will not reflect on the original 48 | authors' reputations. 49 | 50 | Finally, any free program is threatened constantly by software 51 | patents. We wish to avoid the danger that redistributors of a free 52 | program will individually obtain patent licenses, in effect making the 53 | program proprietary. To prevent this, we have made it clear that any 54 | patent must be licensed for everyone's free use or not licensed at all. 55 | 56 | The precise terms and conditions for copying, distribution and 57 | modification follow. 58 | 59 | GNU GENERAL PUBLIC LICENSE 60 | TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 61 | 62 | 0. This License applies to any program or other work which contains 63 | a notice placed by the copyright holder saying it may be distributed 64 | under the terms of this General Public License. The "Program", below, 65 | refers to any such program or work, and a "work based on the Program" 66 | means either the Program or any derivative work under copyright law: 67 | that is to say, a work containing the Program or a portion of it, 68 | either verbatim or with modifications and/or translated into another 69 | language. (Hereinafter, translation is included without limitation in 70 | the term "modification".) Each licensee is addressed as "you". 71 | 72 | Activities other than copying, distribution and modification are not 73 | covered by this License; they are outside its scope. The act of 74 | running the Program is not restricted, and the output from the Program 75 | is covered only if its contents constitute a work based on the 76 | Program (independent of having been made by running the Program). 77 | Whether that is true depends on what the Program does. 78 | 79 | 1. You may copy and distribute verbatim copies of the Program's 80 | source code as you receive it, in any medium, provided that you 81 | conspicuously and appropriately publish on each copy an appropriate 82 | copyright notice and disclaimer of warranty; keep intact all the 83 | notices that refer to this License and to the absence of any warranty; 84 | and give any other recipients of the Program a copy of this License 85 | along with the Program. 86 | 87 | You may charge a fee for the physical act of transferring a copy, and 88 | you may at your option offer warranty protection in exchange for a fee. 89 | 90 | 2. You may modify your copy or copies of the Program or any portion 91 | of it, thus forming a work based on the Program, and copy and 92 | distribute such modifications or work under the terms of Section 1 93 | above, provided that you also meet all of these conditions: 94 | 95 | a) You must cause the modified files to carry prominent notices 96 | stating that you changed the files and the date of any change. 97 | 98 | b) You must cause any work that you distribute or publish, that in 99 | whole or in part contains or is derived from the Program or any 100 | part thereof, to be licensed as a whole at no charge to all third 101 | parties under the terms of this License. 102 | 103 | c) If the modified program normally reads commands interactively 104 | when run, you must cause it, when started running for such 105 | interactive use in the most ordinary way, to print or display an 106 | announcement including an appropriate copyright notice and a 107 | notice that there is no warranty (or else, saying that you provide 108 | a warranty) and that users may redistribute the program under 109 | these conditions, and telling the user how to view a copy of this 110 | License. (Exception: if the Program itself is interactive but 111 | does not normally print such an announcement, your work based on 112 | the Program is not required to print an announcement.) 113 | 114 | These requirements apply to the modified work as a whole. If 115 | identifiable sections of that work are not derived from the Program, 116 | and can be reasonably considered independent and separate works in 117 | themselves, then this License, and its terms, do not apply to those 118 | sections when you distribute them as separate works. But when you 119 | distribute the same sections as part of a whole which is a work based 120 | on the Program, the distribution of the whole must be on the terms of 121 | this License, whose permissions for other licensees extend to the 122 | entire whole, and thus to each and every part regardless of who wrote it. 123 | 124 | Thus, it is not the intent of this section to claim rights or contest 125 | your rights to work written entirely by you; rather, the intent is to 126 | exercise the right to control the distribution of derivative or 127 | collective works based on the Program. 128 | 129 | In addition, mere aggregation of another work not based on the Program 130 | with the Program (or with a work based on the Program) on a volume of 131 | a storage or distribution medium does not bring the other work under 132 | the scope of this License. 133 | 134 | 3. You may copy and distribute the Program (or a work based on it, 135 | under Section 2) in object code or executable form under the terms of 136 | Sections 1 and 2 above provided that you also do one of the following: 137 | 138 | a) Accompany it with the complete corresponding machine-readable 139 | source code, which must be distributed under the terms of Sections 140 | 1 and 2 above on a medium customarily used for software interchange; or, 141 | 142 | b) Accompany it with a written offer, valid for at least three 143 | years, to give any third party, for a charge no more than your 144 | cost of physically performing source distribution, a complete 145 | machine-readable copy of the corresponding source code, to be 146 | distributed under the terms of Sections 1 and 2 above on a medium 147 | customarily used for software interchange; or, 148 | 149 | c) Accompany it with the information you received as to the offer 150 | to distribute corresponding source code. (This alternative is 151 | allowed only for noncommercial distribution and only if you 152 | received the program in object code or executable form with such 153 | an offer, in accord with Subsection b above.) 154 | 155 | The source code for a work means the preferred form of the work for 156 | making modifications to it. For an executable work, complete source 157 | code means all the source code for all modules it contains, plus any 158 | associated interface definition files, plus the scripts used to 159 | control compilation and installation of the executable. However, as a 160 | special exception, the source code distributed need not include 161 | anything that is normally distributed (in either source or binary 162 | form) with the major components (compiler, kernel, and so on) of the 163 | operating system on which the executable runs, unless that component 164 | itself accompanies the executable. 165 | 166 | If distribution of executable or object code is made by offering 167 | access to copy from a designated place, then offering equivalent 168 | access to copy the source code from the same place counts as 169 | distribution of the source code, even though third parties are not 170 | compelled to copy the source along with the object code. 171 | 172 | 4. You may not copy, modify, sublicense, or distribute the Program 173 | except as expressly provided under this License. Any attempt 174 | otherwise to copy, modify, sublicense or distribute the Program is 175 | void, and will automatically terminate your rights under this License. 176 | However, parties who have received copies, or rights, from you under 177 | this License will not have their licenses terminated so long as such 178 | parties remain in full compliance. 179 | 180 | 5. You are not required to accept this License, since you have not 181 | signed it. However, nothing else grants you permission to modify or 182 | distribute the Program or its derivative works. These actions are 183 | prohibited by law if you do not accept this License. Therefore, by 184 | modifying or distributing the Program (or any work based on the 185 | Program), you indicate your acceptance of this License to do so, and 186 | all its terms and conditions for copying, distributing or modifying 187 | the Program or works based on it. 188 | 189 | 6. Each time you redistribute the Program (or any work based on the 190 | Program), the recipient automatically receives a license from the 191 | original licensor to copy, distribute or modify the Program subject to 192 | these terms and conditions. You may not impose any further 193 | restrictions on the recipients' exercise of the rights granted herein. 194 | You are not responsible for enforcing compliance by third parties to 195 | this License. 196 | 197 | 7. If, as a consequence of a court judgment or allegation of patent 198 | infringement or for any other reason (not limited to patent issues), 199 | conditions are imposed on you (whether by court order, agreement or 200 | otherwise) that contradict the conditions of this License, they do not 201 | excuse you from the conditions of this License. If you cannot 202 | distribute so as to satisfy simultaneously your obligations under this 203 | License and any other pertinent obligations, then as a consequence you 204 | may not distribute the Program at all. For example, if a patent 205 | license would not permit royalty-free redistribution of the Program by 206 | all those who receive copies directly or indirectly through you, then 207 | the only way you could satisfy both it and this License would be to 208 | refrain entirely from distribution of the Program. 209 | 210 | If any portion of this section is held invalid or unenforceable under 211 | any particular circumstance, the balance of the section is intended to 212 | apply and the section as a whole is intended to apply in other 213 | circumstances. 214 | 215 | It is not the purpose of this section to induce you to infringe any 216 | patents or other property right claims or to contest validity of any 217 | such claims; this section has the sole purpose of protecting the 218 | integrity of the free software distribution system, which is 219 | implemented by public license practices. Many people have made 220 | generous contributions to the wide range of software distributed 221 | through that system in reliance on consistent application of that 222 | system; it is up to the author/donor to decide if he or she is willing 223 | to distribute software through any other system and a licensee cannot 224 | impose that choice. 225 | 226 | This section is intended to make thoroughly clear what is believed to 227 | be a consequence of the rest of this License. 228 | 229 | 8. If the distribution and/or use of the Program is restricted in 230 | certain countries either by patents or by copyrighted interfaces, the 231 | original copyright holder who places the Program under this License 232 | may add an explicit geographical distribution limitation excluding 233 | those countries, so that distribution is permitted only in or among 234 | countries not thus excluded. In such case, this License incorporates 235 | the limitation as if written in the body of this License. 236 | 237 | 9. The Free Software Foundation may publish revised and/or new versions 238 | of the General Public License from time to time. Such new versions will 239 | be similar in spirit to the present version, but may differ in detail to 240 | address new problems or concerns. 241 | 242 | Each version is given a distinguishing version number. If the Program 243 | specifies a version number of this License which applies to it and "any 244 | later version", you have the option of following the terms and conditions 245 | either of that version or of any later version published by the Free 246 | Software Foundation. If the Program does not specify a version number of 247 | this License, you may choose any version ever published by the Free Software 248 | Foundation. 249 | 250 | 10. If you wish to incorporate parts of the Program into other free 251 | programs whose distribution conditions are different, write to the author 252 | to ask for permission. For software which is copyrighted by the Free 253 | Software Foundation, write to the Free Software Foundation; we sometimes 254 | make exceptions for this. Our decision will be guided by the two goals 255 | of preserving the free status of all derivatives of our free software and 256 | of promoting the sharing and reuse of software generally. 257 | 258 | NO WARRANTY 259 | 260 | 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY 261 | FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN 262 | OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES 263 | PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED 264 | OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 265 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS 266 | TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE 267 | PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, 268 | REPAIR OR CORRECTION. 269 | 270 | 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 271 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR 272 | REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, 273 | INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING 274 | OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED 275 | TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY 276 | YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER 277 | PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE 278 | POSSIBILITY OF SUCH DAMAGES. 279 | 280 | END OF TERMS AND CONDITIONS 281 | 282 | How to Apply These Terms to Your New Programs 283 | 284 | If you develop a new program, and you want it to be of the greatest 285 | possible use to the public, the best way to achieve this is to make it 286 | free software which everyone can redistribute and change under these terms. 287 | 288 | To do so, attach the following notices to the program. It is safest 289 | to attach them to the start of each source file to most effectively 290 | convey the exclusion of warranty; and each file should have at least 291 | the "copyright" line and a pointer to where the full notice is found. 292 | 293 | 294 | Copyright (C) 295 | 296 | This program is free software; you can redistribute it and/or modify 297 | it under the terms of the GNU General Public License as published by 298 | the Free Software Foundation; either version 2 of the License, or 299 | (at your option) any later version. 300 | 301 | This program is distributed in the hope that it will be useful, 302 | but WITHOUT ANY WARRANTY; without even the implied warranty of 303 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 304 | GNU General Public License for more details. 305 | 306 | You should have received a copy of the GNU General Public License along 307 | with this program; if not, write to the Free Software Foundation, Inc., 308 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. 309 | 310 | Also add information on how to contact you by electronic and paper mail. 311 | 312 | If the program is interactive, make it output a short notice like this 313 | when it starts in an interactive mode: 314 | 315 | Gnomovision version 69, Copyright (C) year name of author 316 | Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 317 | This is free software, and you are welcome to redistribute it 318 | under certain conditions; type `show c' for details. 319 | 320 | The hypothetical commands `show w' and `show c' should show the appropriate 321 | parts of the General Public License. Of course, the commands you use may 322 | be called something other than `show w' and `show c'; they could even be 323 | mouse-clicks or menu items--whatever suits your program. 324 | 325 | You should also get your employer (if you work as a programmer) or your 326 | school, if any, to sign a "copyright disclaimer" for the program, if 327 | necessary. Here is a sample; alter the names: 328 | 329 | Yoyodyne, Inc., hereby disclaims all copyright interest in the program 330 | `Gnomovision' (which makes passes at compilers) written by James Hacker. 331 | 332 | , 1 April 1989 333 | Ty Coon, President of Vice 334 | 335 | This General Public License does not permit incorporating your program into 336 | proprietary programs. If your program is a subroutine library, you may 337 | consider it more useful to permit linking proprietary applications with the 338 | library. If this is what you want to do, use the GNU Lesser General 339 | Public License instead of this License. 340 | --------------------------------------------------------------------------------