nitter.net is back #1212
Replies: 6 comments 7 replies
-
Happy about it all. |
Beta Was this translation helpful? Give feedback.
-
Hell yeah! Gonna have to reconfig my LiberaPay later today. Altho curious to why rewrite in GoLang? Will that impact the previous small size and nim's javascript interop/compilation? |
Beta Was this translation helpful? Give feedback.
-
Nim is pretty much a dead language at this point, I've lost faith in it after having used it for 6 years. Go is a much better fit, and it's way more likely to attract future contributors. The nitter binary isn't particularly small, and with Go it'll at least be statically linked, making deployments a bit simpler. The name isn't changing. |
Beta Was this translation helpful? Give feedback.
-
Can you detail what makes it expensive? You need lots of servers to make requests from different IPs or something like that? |
Beta Was this translation helpful? Give feedback.
-
Any plans to support RSS feeds on it? Also I have a raspberry pi, please can you direct me in the right direction to getting a private instance setup on my Tailnet? I’ve tried before but got very lost :) |
Beta Was this translation helpful? Give feedback.
-
I feel like a ton of services that went go ultimately had performance problems and then went rust. Not to be the meme zealot but perhaps consider just starting with rust? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm happy to announce nitter.net is finally back, hopefully for good this time.
I've merged the authentication replacement PR #1210 (replaced #985) after a bunch of fixes and updates, so there's no longer a need to use a different branch or one of the many forks floating around.
Hosting an instance now is difficult and expensive, but not impossible. For a small/private instance you can do it for free quite easily, but a large public instance is a different story. See this page, and feel free to reach out to me on Matrix if you have any questions regarding this. I won't be discussing it in public.
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.
If you'd like to donate towards the future of Nitter (development and supporting new instances), please see the "Donations" section in the readme.
Beta Was this translation helpful? Give feedback.
All reactions