Comment by elcritch

16 hours ago

Cool to see such a notable Nim based project continue! It's unfortunate that X tries to block Nitter so often, but zedeus always seems to find a path around technical or now legal issues.

The code looks surprisingly easy to hack on: https://github.com/zedeus/nitter/blob/master/src/nitter.nim

5 comments

elcritch

Reply
Polizeiposaune  15 hours ago

Nitter's author has suggested at least once that due to problems with Nim, a rewrite in Go is in the works:

"The long-term plan is to rewrite the source code in Go, as I'm no longer interested in using Nim. This isn't a small task, but building more features with the current state of things is painful. Before doing that I'll fix some feature parity issues, and work on some conveniences for instance operators. Stay tuned."

https://github.com/zedeus/nitter/discussions/1212

  • elcritch  10 hours ago

    Interesting, well too bad. Personally I find Nim more useful and productive than ever with LLMs.

    Nitter uses Jester which seems dead for sure, but doing static binaries is easy. Personally I just forked Mummy to continue as MummyNG since I prefer threaded servers so things like JSON parsing doesn’t cause latency issues.

    Though that being written over a year ago it’s either not a high priority or harder than it seems. I’ll be curious to see which. LLMs make it easier than ever for others to contribute or to fix up deps.

  • dom96  14 hours ago

    Honestly seems like a good move. It also isn't likely to be very difficult with the help of LLMs.