https://github.com/PrivacyDevel/nitter/tree/pre_guest_accounts
I've been using this fork for months now, NSFW works and i don't get rate limited. The account was made with a throwaway email and it never required a phone number or similar, unsure if this changed now.
It runs on my local home server, but all traffic is proxied through mullvad VPN, so i still get all the privacy benefits and the superior frontend.

Would like to see this become an option. Public instances might be dead for now, but I'm sure lot of people, including myself, still prefer a local nitter instance over using twitter directly.

@polak14 I tried the pre_guest_accounts branch a few months ago but searching didn't work, I think some APIs have changed and this branch is not updated. Is it the same for you?

https://github.com/PrivacyDevel/nitter/tree/pre_guest_accounts I've been using this fork for months now, NSFW works and i don't get rate limited. The account was made with a throwaway email and it never required a phone number or similar, unsure if this changed now. It runs on my local home server, but all traffic is proxied through mullvad VPN, so i still get all the privacy benefits and the superior frontend.

Would like to see this become an option. Public instances might be dead for now, but I'm sure lot of people, including myself, still prefer a local nitter instance over using twitter directly.

I'm interested to try it as well though since I use my private instance for some light scraping I probably would need to use more than one account, but should be able to get by with a small handful. Not sure how much work it would be to make them work with a similar system to what's currently used with the rotating guest accounts or whether my throwaways would be at risk of getting banned eventually. Though I can understand if this isn't a high priority for implementation since it's not really very practical for public instances given the large number of accounts that would be required.

edit: I found #983 (comment) which seemed to work to generate a token for a throwaway account I made, so I guess I'll just try this method out and gradually migrate over to a small handful of accounts like this as my guest accounts expire if it seems to be working well.

How did you get it working? I get errors immediately, both with using pre_guest_accounts and with using that script to generate tokens i manually made

I figured it out, you need to disable the expiry check for the tokens bepvte@ca498f5

I figured it out, you need to disable the expiry check for the tokens bepvte@ca498f5

Is search working? It's not working for me on the pre_guest_accounts branch.

it's working for me but the account gets locked if you try to paginate more than a couple of pages in search

Given the demise of the public instances and wanting to be able to continue to follow the single poster I read on twitter I went ahead and created a twitter login with an otherwise unused email account. What a horrible experience after using Nitter for this purpose! It is extremely slow and clunky for this purpose compared to Nitter.

Could someone put together a public version of Nitter that would prompt when initially contacted for a Twitter login to use? I would imagine this data could be stored locally in an encrypted cookie such that the user would never need to provide it again.

I wonder if there is a way to do this with login credentials so it can be auto refreshed

A private Nitter instance can also be very useful for archiving tweets with wget, ArchiveBox or similar (currently, I think it's the only viable option).

@Danoloan10 There have been some updates on the PrivacyDevel fork, if that helps.

To anyone still trying to figure it out, I stumbled across this detailed self-hosting nitter guide:

https://github.com/sekai-soft/guide-nitter-self-hosting/

I decided to give this a try and am encountering problems following the directions. I am encountering:

$ nimble build -d:release Error: Could not read package info file in /opt/nitter/nitter.nimble; ... Reading as ini file failed with: ... Invalid section: . ... Evaluating as NimScript file failed with: ... /opt/nitter/config.nims(1, 2) Error: unknown warning: HoleEnumConv ... printPkgInfo() failed. $
What am I doing wrong?