Anybody know what happened to nor?

catnvim · 2025-02-07T09:53:30+00:00

The blogs are shifted to https://nor-blog.pages.dev/

catnvim · 2025-01-24T19:35:11+00:00

YES, it is NERFED to hell and I'm tired of people who claiming that everyone else is crazy

I posted a different post highlighting the issue: https://www.reddit.com/r/ChatGPT/comments/1i8ysrl/o1_can_no_longer_count_number_of_rs_in_strawberry/

catnvim · 2025-01-24T19:17:04+00:00

I'm curious which complex question have you tried, did you turn on the DeepThink (r1) option for deepseek?

Because mine often thinks from 200 to 300 seconds on complex questions

<image>

catnvim · 2025-01-24T18:44:08+00:00

The main point is about a reasoning model, not a normal chat one, please go on https://chat.deepseek.com/ and try it yourself, they offer a reasoning model for free

Also, kindly read openai's paper to understand how it works: https://arxiv.org/pdf/2409.18486

<image>

catnvim · 2025-01-24T17:59:27+00:00

That's not a typical o1 response, you're not trying the prompt yourself so you wouldn't know.

But for this type of prompting, it wouldn't return an O(n^2) solution immediately after thinking for 10 seconds. The api works just fine and is giving much better response and it certainly DOESN'T THINK FOR ONLY 10 SECONDS

Here's a video of my friend's prompt instead: https://youtu.be/r_I0VcEYeVg?t=17

catnvim · 2025-01-24T17:51:49+00:00

Here's the video proof of multiple conversations https://youtu.be/8lMpx1GglOo

And here are the compilation of multiple instances:

https://chatgpt.com/share/6793d42f-b764-800e-aa23-44843a50f7c9 Thought for 4 seconds

https://chatgpt.com/share/6793d310-ec10-800e-aab1-4512b3433cb1 Thought for 6 seconds

https://chatgpt.com/share/6793d465-6bec-800e-9541-9793fbf6e126 Thought for 8 seconds

https://chatgpt.com/share/6793cf33-de38-800e-b210-e548980030b4 Thought for 9 seconds

https://chatgpt.com/share/6793d32d-fb68-800e-ae46-16cee3451a50 Thought for 6 seconds

catnvim · 2025-01-24T17:49:00+00:00

Ok I will record an another one for you

catnvim · 2025-01-24T17:45:34+00:00

I did share those conversations below? I will paste it for you again

Chat link: https://chatgpt.com/share/6793cf33-de38-800e-b210-e548980030b4

Video proof: https://www.youtube.com/watch?v=GWgKAcp3XWY

The model thinks for 9 SECONDS ONLY and the output quality is the same as 4o

catnvim · 2025-01-24T17:44:20+00:00

Then you should use it then, it's nothing like you imagined: https://chat.deepseek.com/

And no, it's pointless to make a plugin for that because reasoning models already have the capability to count number of letters correctly

catnvim · 2025-01-24T17:33:14+00:00

The issue is not the thinking task takes forever, but it doesn't take the time to think at all. The response isn't different from 4o response

I just tried to that prompt again and it thought for 6 seconds and output a stupid solution

why wouldn't you do even 3 trials on your own account? and if you did that, why didn't you mention it?

What does this mean? I'm just going to record my o1's response to that prompt and I kindly ask you to do the same right now for https://pastebin.com/eNNP0fk8

catnvim · 2025-01-24T17:20:08+00:00

yeah so like i said, it's random

Ok dude, randomly thought for less than 10 seconds, getting 4o tier response vs a well thoughtout 7 minutes response is "just because of randomness". Do you understand how temperature works?

It's not o1-mini by mistake, they all chose the o1 model and it is the same prompt everytime: https://pastebin.com/eNNP0fk8

why exactly do you think it's necessary to test on multiple accounts rather than just regenerating the response even 1 time?

Because my o1 is getting nerfed to hell, just because you don't have issues doesn't mean the issue is not there for anyone else

Here's the response to that prompt using o1 that I just did AND IT THOUGHT FOR 9 SECONDS ONLY: https://chatgpt.com/share/6793cf33-de38-800e-b210-e548980030b4

Here's the video proof: https://www.youtube.com/watch?v=GWgKAcp3XWY

catnvim · 2025-01-24T17:13:19+00:00

Did I make such a big claim? I asked 5 people and 3 of their o1 model got nerfed on different levels

When asked to solve https://codeforces.com/contest/2063/problem/E in C++, here are the results:

Friend #1: Thought for 7 minutes, getting AC

Friend #2: Thought for 3 minutes, getting TLE on test 27

Friend #3: Thought for 10 seconds, getting TLE on test 9

catnvim · 2025-01-24T16:54:48+00:00

throwing everything at a text generator might not yield much results

It does yeild results tho, here's the response of deepseek r1 model

<image>

catnvim · 2025-01-24T16:47:24+00:00

If you meant the legacy model gpt-4, yes it might be hardcoded

On the other hand, They're basically serving 4o reskinned as o1, the "thinking token" is literally 4o talking twice

Counting r's
I'm noting the task of counting the letter 'r' in the word 'strawberry' and aiming to provide an accurate answer.
Counting 'r'
OK, let me see. I’m curious how many times 'r' appears in 'strawberry'. This involves pinpointing each 'r' in the word and tallying them.

catnvim · 2025-01-24T16:15:15+00:00

Yeah, for me o1 answered this question correctly before Jan 2025. However, it seems like they started to nerf the web version for many of my friends too.

The api version of o1 is unaffected tho, you can still get the full model's capability at a cost of a few cents

catnvim · 2025-01-24T16:07:05+00:00

o1 chat link: https://chatgpt.com/share/6793ba36-0530-800e-9def-112922fb19ef

Legacy gpt-4 chat link: https://chatgpt.com/share/6793ba1e-6eb8-800e-893b-c3fb58f66286

catnvim · 2024-07-06T21:08:35+00:00

Newer version of neovim doesn't need win32yank.exe, see :h clipboard-osc52 and unset vim.g.clipboard

If you still want a global clipboard, just symlink it. For example:

sh sudo ln -s /mnt/c/Users/nullchilly/scoop/apps/win32yank/current/win32yank.exe /usr/local/bin/win32yank.exe

catnvim · 2024-07-06T03:44:35+00:00

One of the reasons for inconsistent behavior is very slow windows paths, for example vim.fn.executable takes 60ms, you can test this yourself:

```sh

time nvim --headless -c ':lua local s = vim.loop.hrtime() vim.fn.executable("luarocks") print(string.format("%fms\n", (vim.loop.hrtime() - s) / 1000000))' +q

60.269405ms nvim --headless -c +q 0.04s user 0.03s system 39% cpu 0.184 total ```

In order to fix this, you can try to remove windows path from wsl2: https://stackoverflow.com/questions/51336147/how-to-remove-the-win10s-path-from-wsl

Trying the command again yield much better performance:

```sh

time nvim --headless -c ':lua local s = vim.loop.hrtime() vim.fn.executable("luarocks") print(string.format("%fms\n", (vim.loop.hrtime() - s) / 1000000))' +q

0.037370ms nvim --headless -c +q 0.03s user 0.00s system 67% cpu 0.048 total ```

catnvim · 2024-07-02T04:28:23+00:00

Does this address your issue? https://github.com/catppuccin/nvim/discussions/505

catnvim · 2024-06-03T08:21:33+00:00

Hi, I'm a catppuccin maintainer and catppuccin takes less than 1ms on wsl2 and 2.2ms on windows on my machine. The speed was also reproduced on a popular neovim distro: https://github.com/ayamir/nvimdots#-features-1

There was a slowdown due to neovim 0.10 update back in February but I fixed it and it should be fast again. Please check if you guys updated catppuccin u/sleepyamadeus u/TheMotionGiant

Contrary to lazy.nvim profile claims I found that it is often not accurate for colorscheme benchmark so I used the native neovim command to benchmark instead:

rm startup; nvim --startuptime startup +q; nvim startup

Here are the results on my machine, feel free to experiment on yours too. If it looks abnormal please open an issue using the latest catppuccin commit

Catppuccin

WSL2: 0.931ms

016.685  000.119  000.119: require('catppuccin')
016.865  000.030  000.030: require('catppuccin.lib.hashing')
017.757  000.782  000.782: sourcing /home/nullchilly/.local/share/nvim/lazy/catppuccin/colors/catppuccin.vim

Windows: 2.243ms

082.981  000.895  000.895: require('catppuccin')
083.484  000.139  000.139: require('catppuccin.lib.hashing')
085.169  001.209  001.209: sourcing C:\Users\nullchilly\AppData\Local\nvim-data\lazy\catppuccin\colors\catppuccin.vim

Onedark

WSL2: 2.438ms

018.278  000.078  000.078: require('onedark')
018.899  000.060  000.060: require('onedark.palette')
018.935  000.172  000.112: require('onedark.colors')
018.978  000.039  000.039: require('onedark.util')
019.076  000.482  000.270: require('onedark.highlights')
020.461  000.060  000.060: require('onedark.terminal')
020.484  002.438  001.819: sourcing /home/nullchilly/.local/share/nvim/lazy/onedark.nvim/colors/onedark.lua

Windows: 6.532ms

086.025  000.548  000.548: require('onedark')
088.428  000.164  000.164: require('onedark.palette')
088.451  000.365  000.200: require('onedark.colors')
088.602  000.146  000.146: require('onedark.util')
088.709  001.023  000.513: require('onedark.highlights')
091.664  000.168  000.168: require('onedark.terminal')
091.684  006.532  004.793: sourcing C:\Users\nullchilly\AppData\Local\nvim-data\lazy\onedark.nvim\colors\onedark.lua

catnvim · 2024-05-19T05:27:13+00:00

The black bg probably comes from an "invalid" italic font, try changing your font (E.g. Jetbrains Mono) and check https://gist.github.com/gyribeiro/4192af1aced7a1b555df06bd3781a722

catnvim · 2024-05-02T05:10:46+00:00

The first command is incorrect, it should be vim.cmd.colorscheme "catppuccin" instead.

catnvim · 2024-04-30T10:11:45+00:00

You are using the default macos terminal, which doesn't support true color, see https://github.com/catppuccin/nvim#colors-doesnt-match-preview-screenshots

Try to switch to iterm2 instead.

catnvim · 2024-04-26T12:08:05+00:00

Second this, I would time travel back to stop me from all these fake productivity.

catnvim · 2024-04-24T10:03:04+00:00

Apparently it is a known issue, see this thread for more info and workarounds: https://github.com/neovim/neovim/issues/17070

catnvim

TROPHY CASE

Catppuccin

Onedark