Read proposal 9 and you will see that Robert gave credit for the idea to @King_Valhalla05 in the bobdotfun chat group on Telegram.
Here is the specific message that persuaded Robert as linked by another member of the community here.

Alice DAO was proposed 2025-01-07T19:07:02.203Z
Your response is 2h 16m later 2025-01-07T21:23:36.594Z
That post has 6 edits, so hopefully you are looking at the right edit when presenting your observations. I think you are doing some funny analysis on your times, but whatever, it’s not worth getting into the minutia with you. I wanted to make sure the edit that shows the CodeGov ALICE neuron information was in one of the early posts in the thread for better visibility. We had already been talking about starting a CodeGov ALICE known neuron for the community because the first proposal 134701 had already failed for known reasons and it seemed like there would be a second proposal 134769 that DFINITY would not block (no NF contribution, BOB canisters added to the SNS control, etc.). This was all easily predictable if you were following the conversations on the forum.

On top of that, offering users to follow your neuron.
This is very consistent with my history of trying to help advance decentralization by offering a reliable and credible known neurons for people to follow if they value decentralization. Most people tend to follow the dev team, yet a common goal of a DAO is to achieve a decentralized distribution of voting power. I believe that we need more known neurons to step up (NNS and SNS) to fill this role. This is what I helped do back when we started the Synapse neuron and now what I do with the CodeGov neurons. I decided to pursue a CodeGov ALICE neuron because there were people asking me to do it who wanted to see options for the community.

And now being against fixing it..
There is nothing to fix at this time. The SNS parameters are exactly where they need to be. All we have right now is Adam trying to take it over with no specific plans in mind except apparently a vendetta against me personally. Hence, he is trying to change the SNS parameters and create these new narratives through people like you in order to help give himself an advantage. In the end, the proposals will execute according to whichever side gets more votes. He is welcome to try to take over ALICE, but I’m not seeing anything wrong with it at this time and he is not giving the majority of the voting power in the SNS any good reason to follow his lead yet.

A ‘dot fun’ project should have a max 6-month lock time, 25% age bonus, and a max dissolve delay of 100%.
ALICE is not a ‘dot fun’ token. It is an SNS that owns responsibility for the BOB canisters. I suspect Robert proposed an 8 year lock time because it is consistent with the NNS lock period. Every neuron created at SNS launch had a 0 or 1 day dissolve delay in order to ensure the tokens were as liquid as possible, so increasing the max dissolve delay required a max age bonus of 400% and a max dissolve delay bonus of 900% in order to incentivize the most committed ALICE governance participants to quickly max lock some of their tokens. It was effective enough to convince enough people to increase their dissolve delay. Personally, I saw it as a risk and started commenting about it on the forum to raise awareness. Here is an example, but there are several more.
I strongly recommend that the DAO Community Settings topic should also be critical. It is very easy for the dev team to push changes that have profound impact on the SNS community without the community having sufficient input or time to respond. Examples of proposals that had this effect are listed below for two SNS projects that I follow. Most of these proposals were a net positive for the respective SNS, but list illustrates that there are many examples of big changes that were not discussed publicly in advance and most people were following others before they realized the implications of the proposed change. Some of these changes in the ALICE SNS happened almost instantly when the dev voted due to follow patterns in the very early stages of the SNS. I think it would be much better to hold changes like this to higher standards by making them critical.
Follow that discussion thread and you will see that DFINITY indicated that they don’t want to make this change for now, but that was before all of this SNS takeover that Adam has been doing. It will be interesting to see if that remains their stance.

Not to mention, during the last month, you have been trying to defend all that is wrong in the ecosystem, employing spam and confusion to make sure nobody has the time to read about these problems. [Proposal to upgrade WaterNeuron voting system]
Ah yes, the real reason why you felt the need to cast shade in my direction on this topic. I disagreed with you about your idea and tried to present my opinion about a better solution to the problem, but instead of having a productive conversation it just devolved into talking past each other. Reasonable people can disagree and still remain civilized. We don’t have to get offended and start taking cheap shots. I’m happy to revisit that conversation any time, but I do still think there is a bigger problem that can be solved with lower hanging fruit that would be more impactful to WTN voting power distribution and should be pursued first. I’m sorry my opposition to your idea turned you off.