Kancolle Kensho Bu Part 1-3 summary

Kancolle Kensho Bu Part 1-3 summaries:

Members of the club:
Noiji (Leader)
Biikame (Researcher)
Fate (Kancolle DB administrator)
Marlowe (Public Relations)
Nanjou Tadashi (Freelance writer)
Yo- (?)

I had been ignoring this whole thing ever got tired of Noisy BS some time ago. I looked into it and from how I understood this is what happened:

    (timing is spring event this year)
    -A source within kenshou-bu, later to be confirmed as https://twitter.com/nanjyo_tadashi claims the reason why the quality of KC (6-4, event fuckups) is because Tanaka Kensuke is no longer within the devteam and a new Mr A is leading the team
    ->kenshou-bu people believe this and create a change.org petition with the goal of trying to pressure Mr A out of the dev team
    ->shortly after petition is created nanjyo_tadashi claims that there are going to be changes within KC dev team and that the petition no longer serves any purpose -> petition withdrawn
    -Shortly after or during this it is found out that the information leaked by nanjyo_tadashi has been leaked out to an outsider
    ->nanjyo_tadashi claims leaking this info to an outsider will weaken his own trust with his sources also translating into monetary loss for him
    ->Two people have spoken about this information to an outsider: Noisy and Biikame. Noisy says "sorry" and is forgiven. Rest of the kenshou-bu members here lead by Noisy force or try to force Biikame into signing a contract that makes him pay 1 million yen if the person who he spoke about the leak leaks the information
    ->the information is leaked and it turns into big infight with kenshou-bu and Biikame
    -during this infighting lots of information about the untrustworthiness of kenshou-bu spreads out, including the possibility of kenshou-bu obtaining user payment data through their client
    -at some point DMM gets involved and requests the termination of kenshou-bu because of various violations
    -This request strictly prohibits sharing the request to any third parties->Noisy still manages to share it to outsiders
    -conversations about kenshou-bu member interactions leak (vid related) and it's found out that kenshou-bu lead by Noisy used very Yakuza like methods to try and blackmail Biikame
    -Sometime after this nanjyo_tadashi comes out and confesses that he made everything up and that Tanaka Kensuke is still leading KC devteam. Basically everything happened because he was BS'ing all along

May 3 - Kancolle Spring Event starts. However, gimmick increasing damage against boss was not working properly. Not a single clear even after 23 hours have passed.
May 4 - Kancolle Staff announces bug and fixes it with an emergency maintenance
Kancolle Kensho is a group that "researches" various aspects of the game and announces them on Twitter. However, this is done with a dedicated browser and database using tools.
Kancolle is played on dedicated browser -> Pulled data is sent to DB -> Accumulated information is researched
[Noisy - Kancolle Kensho's Leader. Created database, created dedicated browser, gathered Researchers and formed Kancolle Kensho]
May 5 - Kancolle Kensho announces a bug that a third U-511 and I-401 won't drop if you owned 2 or more copies of either
May 6 - Kancolle Staff announces that said bug is confirmed and fixed. Kancolle Kensho's recognition and voice increases.
May 7 - Kankolle Kensho's followers have rised to 20,000
May 8 - Kancolle Kensho makes an announcement regarding E6's gimmick, which involves getting a S victory in E6's AGL nodes and having defeated E5's boss after the maintenance. Spreads information that needing to defeat E5's boss is odd and most likely a bug as there are cases where defeating E5's boss doesn't activate the gimmick.
May 10 - Kancolle Staff that in order to activate the gimmick, getting a S in E6's AGL nodes or E5's I node is necessary. Kancolle Kensho makes no corrections or apologies on their twitter account.
Noisy: To be honest, I believe I'm in a position where I can instigate Admirals who've incurred a loss due to bugs to ask for a refund. The only reason I don't is because I like Kancolle.
Many Admirals have already cleared the event now that the gimmick's requirement have been affirmed
May 11 - Images on Kancolle Kensho's Twitter have been removed by copyright holder
Noisy phones DMM and receives response that it has been removed on Kancolle Staff's request.
This marks the end of the prologue

May 24 - Noisy: Despite there being a fatal bug that made the event unclearable until the emergency maintenance, it's unreasonable that there has been no reimbursements for RTAers and other pioneers. I'm planning on starting a petition requesting refunds for the money spent during that time.
May 27 - Petition by Noisy and Biikame begins, however this is listed as a personal action and has no relation with Kancolle Kensho
[Biikame - Kancolle Kensho member. Joined as a representative of Researchers, manager of Research Wiki and NND's Research Circle community at that time.]
~100 signatures were gathered in 7 hours, however there were quite a few criticisms regarding it as well
May 28 - The petition is taken down for now as there were many unclear details. Petition is rewritten from scratch with Biikame in charge.
May 29 - Draft of second petition is revealed. However, the part involving requesting a refund has been removed.
May 31 - Biikame announces that petition is discontinued, as notoriety was spreading to Kancolle Kenshou despite being unrelated. Biikame announces that he's leaving Kancolle Kenshou
June 1 - Other Researchers CC, Orical, Manaka is my Waifu leave as well. This was supposed to mark the end of the entire incident, however...
June 2 - On Research Circle's notices Biikame writes that "As I'm being threatened by Kancolle Kenshou, I Biikame am stopping all activity involving Research Circle and Research Wiki". At the same time, Biikame's Twitter account is deleted.
Why is he being threatened despite the petition having nothing to do with Kancolle Kenshou? Why did he suddenly delete his Twitter account? Biikame disappears leaving many mysteries behind.

Noisy explains the situation.
Even before the petition Biikame was leaking information to a third party. At worst this may even lead to monetary loss.
Kenshou-bu asks Biikame to sign a non-disclosure agreement, but Biikame ran off in the middle of the conversation and posted that he's being threatened on his community.

New mysteries surface.
What is this 'monetary loss'? What relation does it have with the information Biikame leaked? What were the contents of the threat? What were the details of the contract Noisy was trying to get Biikame to sign? A 'contract' that would be received as a threat and make someone try to disappear?
[Fate - Database creator]: I'll leave it to you to decide who to believe in. I'll just say that I'm disappointed in Biikame.
[Yama - RTA support]: (To Biikame) Amazing, you're sure saying things to suit your purpose
[Marou - PR/Announcer]: I'll say this first, what Biikame did was the worst betrayal. Most believe that he's monitoring Noisy, but the truth is the exact opposite. Biikame is the one who went out of control.
[Koshian - Hoppo Alpha's Creator]: Even if you hate Bii-shi, please don't hate B-cups
Noisy apologizes regarding the petitions. What he says is more or less the same as what Biikame said, but he adds that there were plans to calculate how much users spent using the Database. What was supposed to explain the situation did nothing but deepen the mystery further.
However...

Yo-: I'm keeping silent, but I'll have you pay for any inexpediency that happens
Yo-: I know everything.
Yo-: I'll reveal everything if there are too many lies.
Yo-: This is the final warning. Shut up.
Yo-: Why do I know? I was in the middle of a phone call with Biikame when he was threatened.
Yo-: I'm the one who the information was leaked to. The ones who leaked information were Biikame and Noisy. The reason behind the leak and the contents of the leak itself is a secret. Notice that the only one Kenshou-buu is condemning is Biikame
Yo-: Regarding the petition, I used Biikame and Noisy in order to create an uproar
Yo-: If antis flame at Kenshou-bu the issue will naturally grow larger and the staff would be forced to face this problem.
Yo- posts screenshot of Skype logs with him requesting Biikame and Noisy to start the petition
Yo-: They've already received warnings from DMM, so they have to make this incident happen no matter what, even if they'll get flamed

To summarize:
Information was leaked to Yo-
The one who leaked information was Noisy and Biikame
The one who requested Noisy and Biikame to start the petition was Yo-
Kenshou-bu has received some sort of warning from DMM

Yo-: Finally... My thoughts regarding this incident. Don't have anything to do with Kenshou-bu. Even if it's indirectly through a friend. And to Noisy and the rest of Kenshou-bu, don't have anything to do with us anymore, if you don't I'll just disappear with this information.

June 2 - A new manager for the Research Circle Biikame managed was decided
June 3 - He receives a message from Biikame stating "For everyone's personal safety I'd recommend you stop sending data to the database". When asking for confirmation, he received a reply stating "The database has received a protest requesting dismissal from DMM. As a result there is fear that the information sent to the database would be leaked to DMM, there isn't anyone left in Kenshou-bu who can stop it."
There was 10k users reported back during the Spring Event. Could there possibly be a mass ban for all of them?

While the persons related were apologizing and exposing each other, volunteers were researching how the research database actually works
[ktgohan - Engineer. Throughly investigated 浦賀船渠ノ航跡 incident.]
According to him, Kancolle's API all have an Access Token but some browsers do not delete it completely, which could even lead to accounts getting stolen.
Someone points out that they should stop data should stop being sent to the database until it's safety can be confirmed.
Marou: It's open source, are you an idiot?
ktgohan: I'm saying this after having read the code. Kenshou-bu's side claims that Access Tokens aren't collected, but the truth is that the one who's sending data has to mask their API Token. There's no way to know what the receiving side does and whether they go through the process to mask it.
Marou: Read the receiving side's source as well
ktgohan: Where is that code? And there is no way to confirm whether it's actually running
Marou: You haven't read the code right? Come back after you have
ktgohan: github.com/KancolleVerifi... I've been reading this. The data sent is simply written into Azure Table Storage, there isn't any defensive measures concerning authentication tokens.
ktgohan: I'll ask again, are there any other public released codes from Kenshou-bu's side?
Marou remained silent after that

Yo-: I wasn't planning on saying anything more, but Marou ignored my warning
Yo-: The information source is Nanjou
[Nanjou Tadashi - Freelance writer who took part in Battleship Girl, Chinjufu Seikatsu no Susume, Muv-Luv Alternative Integral Works. Suspected to have received leaks from Kancolle Staff as he figured out solutions to '13 Fall and '14 Summer's events early on]

Marou gives explanations to questions.
Biikame and Noisy started petition unrelated to Kenshou-bu -> Opposition from members as they discovered plans to calculate money spent using the database and information leaks -> Petition stopped, Biikame leaves -> Request Biikame to ask Yo- not to leak information any further -> Yo- tries to get inside information through Biikame -> Kenshou-bu asks Biikame to suppress Yo- -> Yo refuses to answer negotiations -> Biikame disappears
[Kenshou-bu Surveillance - Watched over this incident since May 12 before it came to light]
Kenshou-bu Surveillance sends an open letter to Marou regarding his explanations
Marou remains silent

June 4 - Noisy once again apologizes regarding the petition and links a PDF answering questions
Regarding the information leak. When Noisy began the petition, he heard from Biikame that he told Yo- everything, he thought that this meant everything concerning the petition.
Regarding the 'threat'. Noisy requests Biikame to ask Yo- not to leak information, Yo- asks for inside information as a condition, Kenshou-bu refuses and tries to negotiate through Biikame, Biikame disappears in the middle of the conversation.

Tweet that when they asked DMM again about images getting removed on May 30 they received a reply saying that it was removed on DMM's decision and not Kancolle Staff's.
According to Noisy. Received a mail from DMM on May 27 asking them not to publish false information -> Ask what they meant by false information -> Reply on 30th saying images getting removed was DMM's instruction

The email DMM sent is provided by someone and posted by Kenshou-bu Surveillance
DMM confirms a violation to their terms of service and sends Noisy a warning. Access in an unauthorized manner, publishing their response to inquiries without authorization and publishing false, incorrect or misleading information.
And despite being forbidden from revealing it to a third party without authorization, he immediately reveals it in their group's Skype.
Noisy only mentioned the warning regarding false information and kept the other two a secret, only revealing what worked to his benefit.
The credibility of Surveillance's post was suspicious as the information provider was a secret, but 15 minutes later Kenshou-bu's system engineer reported Surveillance to DMM for revealing the email to a third party without authorization
In the following exchange between Noisy and Surveillance, Noisy himself confirms that the email is authentic

June 7 - Andante, Type 74 Electric Observer's creator, and kanahiron, Kancolle List Maker's creator, leave
June 10 - Marou finally replies to ktgohan. "Ah, sorry, that source is still the old version, tehe". He apologizes for his lack of knowledge regarding the database but does not answer anything.
The research database is running on a source different from what is open to public.
Fate announces that the database is stopped temporarily for maintenance

June 18 - Database's maintenance finishes and restarts service, completely ignoring DMM's warning.
June 19 - Biikame, who deleted his account and disappeared under Kenshou-bu's threat, returns
Biikame: Kenshou-bu's database has already received a dismissal warning from DMM, yet despite this they still continue using it. This causes harm not just to Kenshou-bu, but the entire Kancolle cluster. As such, I, Biikame, request it's immediate dismissal.

What Marou said about him taking data is a lie.
Monetary loss refers to the monetary loss resulting from Nanjou's loss of credence due to information leaking to outsiders.
He received a warning regarding the database's dismissal, but the only one who can do that is Fate, the server's manager.
Kenshou-bu had been receiving information regarding personnel from Nanjou for quite a while. On May 28 they received information from Nanjou that things have changed for the better which is what led to the end of the first petition.
Biikame posts a Skype chat log dated May 30 showing that Kenshou-bu had understood that the "Access in an unauthorized manner" was referring to the database
The threat was done over chat. Those present were Noisy, Koshian, Fate, Marou, Yama and Nanjou. Biikame was told to sign a contract, Biikame deleted his Twitter before it was sent.
Skype chat logs dated June 1 showing the 'threat' scene was posted. Biikame couldn't stop Yo- from leaking information further, and is asked to sign a contract reimbursing any monetary loss that may stem from it. It's mentioned that Noisy also leaked information to Yo-, but that's looked over with just a single apology and he joins in the ganking. In the end Biikame can't come to an agreement with Yo- and escapes, which leads to the notice saying he was threatened.
Kenshou-bu threatened to push all the responsibilities onto him if he didn't sign the contract. This could cause dire problems to Researchers and his community, which is why he deleted his account.

Biikame posts a PDF dating the entire incident chronologically
May 22 - Yo- approaches Biikame saying the users voices are necessary in order for the administration to change, Biikame responds with a part of Nanjou's information. Yo- proposes a petition and suggests asking for Noisy's assistance. Biikame tells Noisy that he told Yo- a part of Nanjou's information, Noisy gives consent. Yo- asks if he can tell cooperators Nanjou's information, Noisy gives consent. Noisy explains the petition to other members and that it's unrelated to Kenshou-bu.
May 27 - First petition completed. Yo- thinks of the contents, Biikame writes them down and Noisy is in charge. Noisy receives warning from DMM to cease Kenshou-bu's activities. Noisy shares warning with Kenshou-bu and Yo-. Noisy says he intends to continue Kenshou-bu, Yo- tells Noisy that they have to make use of the petition to have the staff for forget about everything.
May 28 - Receive information from Nanjou that administration has changed for the better. First petition stopped.
May 29 - Biikame focuses on second petition and announces that he's planning on leaving because of DMM's warning
May 30 - New information from Nanjou, second petition halted.
May 31 - Biikame leaves
June 1 - Noisy claims he hasn't heard that Biikame told Yo- Nanjou's information and that Yo- is mad, which leads to the threat
However

June 21
Noisy: There are several lies in Biikame's statements. If he agrees I can upload chat logs and voice files as evidence.
Biikame: If you desist the database and break up Kenshou-bu then I'll agree.
Noisy: If I cannot prove that you have lied then I'll break up Kenshou-bu.
Biikame: What are these lies you're referring to specifically?
Noisy(16:55): Point 1. Biikame said that Yo- did not ask for Kenshou-bu's information, but Biikame had stated multiple times that Yo- said that "If you don't want me to say anything hand over your information". Point 2. Biikame claims that he was threatened to sign the contract, but that is false. Biikame had agreed to sign the contract, he did not refuse even once. The two points above.
Biikame(17:27): Just for confirmation. Am I correct to believe that you'll desist the database and break up Kenshou-bu if you can't prove that the above two points are lies?
Noisy(23:44): If I can't prove that Point 1 and 2 are false, I'll desist the database and break up Kenshou-bu. If you have no objections, I'll upload the voice file and chat logs and make them public. If you have anything to add I'll wait until 24:00.
Biikame(23:46~55): I have no objections to the terms above, but there are several additional points I'd like to confirm. The time to prove that they are lies is until June 22 23:59. If it cannot be proven then you have until June 23 23:59 to desist the database and break up Kenshou-bu. In addition, this includes the removal of all data obtained including those in the other members' local memory and that a similar organization will not be set up by the involved members in the future. Do you have any objections?
Noisy doesn't respond and posts a PDF including the chat log and voice files at 24:00
Noisy: I'd like to assert the following '3' points.

Skype logs dated June 1 regarding Point 1
Yo- agreed not to speak of information that would point to Nanjou, but asked that they'd allow him to consider whether to speak about the rest.
Noisy asks that he promises not to speak of it.
Yo- requested that in return to limiting it to those who cooperated he wished to tell them the outcome of the entire affair.
Noisy requests Biikame do his best to not let Yo- leak the information any further.
Biikame fails to convince Yo- and asks Noisy to apologize to Yo-, Biikame tells Yo- that Noisy apologized to him.
Noisy suspects that Biikame is plotting with Yo- in order to escape blame and Yo- being mad was just an act.
Noisy explains the situation to other members.
Noisy's assertion is that "Yo- asking for Kenshou-bu's information is a fact."

Voice files between Noisy, Biikame and Nanjou dated June 1 regarding Point 2
08:00~
Nanjou: The whole thing between Noisy, Biikame and Yo- doesn't really have anything to do with me
Nanjou: I don't understand
Nanjou: Well, if revealing everything is your stance
Biikame: Yo-'s you mean
Nanjou: Ah, Yo's stance, revealing everything
Biikame: Yes
Nanjou: Well, then I have to say I'll be taking corresponding measures
Biikame: Yes, I understand
Nanjou: I have no idea what I'll do
Biikame: I understand, I've understood
14:30~
Noisy: Well, then all that's left is who'll take responsibility
Biikame: You mean I will? Yes
Noisy: Can you write it down on contract? Not to leak information and what should we do regarding Yo-
Noisy: I'll have to make something regarding that
Noisy: And Yo-, you can tell him this, but I'm not apologizing
Noisy: I'm taking back my previous apology and say it was Biikame's instruction. Ah, what I'm going to say now is just an example
Noisy: For example, if Yo- is furious because of that and does something, then the responsibility would be on Biikame's shoulders
Noisy: Please be aware of that
Biikame: Yes, I understand, I'm aware, yes.
Noisy: As such, we must make a painful decision, really
Biikame: Yes
Noisy: Biikame should also do his best to stop Yo-
Biikame: Well, regarding that... I feel the same. I really wish he'll stop.
Biikame: But if it gets to that... Well, I'll try my best
Noisy: At the moment, there may be a monetary loss if the information leaks
Noisy: In that case, as you know, I have a lawyer on my side
Noisy: As such, I'm already taking issuing a lawsuit into consideration
Noisy: I think it's unforgivable
Biikame: I understand
Noisy: Yeah, well, I'd like the target to include Yo-, but since it's the net... So you know
Noisy: I'll have you sign the contract and write down your address. I have no way to confirm whether it's real
Noisy: You don't have to hand it to me, but promise that you'll submit it to Nanjou.
Biikame: I understand...
23:00~
Biikame: Well, finally I guess I'll go try convince Yo- again
Noisy: Please do so
Biikame: It'll take a bit of time. Do you mind if I go take some time to try and persuade him?
Noisy: Should we?
Nanjou: Ah, Biikame, I understand that it's relatively stressful mentally to sign a contract like this
Nanjou: If you can settle it, if you can settle this issue, if you can suppress Yo-
Nanjou: Then it's fine even if you don't sign this contract. Ah it's fine even if you don't sign it
Fate: Rather, you'll sign it once, and we'll promise to scrap it afterwards
Biikame: I understand
Fate: That is, if it's settled completely
Noisy: If, later on, that is, in the future
Noisy: This time's contract's that. That is, the fine... We'll be imposing one
Noisy: We wish to impose a corresponding cost if there are any issues
Noisy: I'm the one saying this, but it'll be a good idea to confirm what's written
Noisy: Well, this is really just an example, but you may have to pay one million yen
Noisy: We'll be including something like that. Is that alright?
Nanjou: Eh, is this addressing me? Or Biikame?
Noisy: Well, both sides I guess. This is a contract between the two of you.
Marou: Well, it'll at least cover the costs if you end up cut off by Kadokawa
Noisy: Yeah, a guarantee in case of an employment loss, that'll probably be what it'll be written as
Nanjou: Eh, sorry, this is directed towards Noisy, Biikame and everyone
Nanjou: Regarding this... I think signing a contract like this is heavily stressful mentally to Biikame
Nanjou: It'll extremely maybe work out, well, for now let's have Noisy prepare the contract
Nanjou: And well that sign, we'll leave it until after Biikame has tried convincing Yo-
Noisy: I understand, if that's what Nanjou says. I'll just prepare it for now
Nanjou: This may be an exaggeration, this may be an exaggeration, if you can't settle the matter I'll just use whatever means it'll take
Noisy: I understand. Well, I deeply wish it won't come to a point where this contract has to be signed.
Noisy: The contents would be, well, let's just say I haven't written or said anything like a one million yen fine
Noisy: The contents would be something confirmed and agreed on by Biikame
Biikame: I understand
Which leads to the Skype chat mentioned on >>15632191 and the threat notice

Point 1 is just Yo- asking to disclose information he knows to cooperators and does not involve additional information regarding Kenshou-bu. The conspiracy is entirely inside Noisy's head
Point 2 can be clearly seen as a lynch and a situation where Biikame cannot refuse
Biikame states that "This does not prove that what I've said is a lie"
June 23 - Biikame requests the database's desist and the Kenshou-bu's break up as the two points have not been proven to be a lie
In response, Noisy states that Nanjou tried to settle matters peacefully when Biikame left, signing the contract was unnecessary if he can persuade Yo-, currently Nanjou is hospitalized due to mental fatigue and coronary heart disease, Noisy has been given charge over Nanjou's Twitter, Skype and DM accounts, Biikame threatened to send chat logs to DMM and Kadokawa if he didn't help convince Noisy to desist the server and break up on June 21, Noisy stops the database temporarily as he considers it's usage dangerous at this rate, that he's cutting off all relations with Biikame and adamant on taking action against Biikame upon Nanjou's recovery
Biikame states that he had already made his claims before Noisy cut off relations, Noisy doesn't respond
Noisy only stopped the database temporarily and did not hold his end of the promise

Kenshou-bu Surveillance had been negotiating through various channels and received a request from one of the related parties asking Kenshou-bu members to stop spreading information any further and that there'll be some sort of report at the beginning of next week
June 27 - Nanjou finally appears publicly, apologizes on Twitter and explains everything
1. How Nanjou joined Kenshou-bu. He was originally an acquaintance of Noisy's and was asked to assist in research concerning historical facts. The truth is that he hasn't been working on Kancolle related jobs for over two years and doesn't actually have many chances to inquire about internal affairs. Pleased by the other members' expectations, he made up a bunch of stories around '16 Spring's event.
2. Regarding the stories he made up in Kenshou-bu's chat. "The changing of the person in charge of Kancolle's administration is the cause of the drop in the recent event's quality, there has been another change in personnel in response to this and as such the administration should change for the better from here on." This is a complete lie, and because he didn't want his lying to spread outside, he told Biikame that he'll request compensation.
3. Regarding Noisy having charge over Nanjou's accounts. Nanjou has been hospitalized from June 6 to June 18 due to coronary heart disease. He received the message from Biikame on June 21 and asked Noisy to publicize it with his account
4. He once again apologizes
5. Finally, he states that he's stopping all commercial and doujin activities indefinitely

June 27 - ktgohan tracks down Nanjou and makes an appointment with him in the real world. He confirms that the apology is authentic and that Nanjou is in no condition to talk extendedly
Biikame apologizes to Nanjou for pressuring him
With this, the incident between Biikame and Nanjou has been settled.
However, Noisy remains silent regarding this matter and Kenshou-bu continues operation.
This marks the end of Chapter 1

Next Episode Preview:
Biikame takes action towards Kenshou-bu's destruction
The true state of affairs inside Kenshou-bu is continuously exposed
However, Kenshou-bu continues resistance
It was then that Biikame receives a lawsuit involving 1.1 million
Voices hoping for Kenshou-bu's destruction gather
The true battle engulfing even DMM begins