I don’t know the specifics behind why the limit is 72 bytes, but that might be slightly tricky. My understanding of bcrypt is that it generates 2^salt different possible hashes for the same password, and when you want to test an input you have to hash the password 2^salt times to see if any match. So computation times would get very big if you’re combining hashes

bcrypt has a maximum password length of 72 bytes.

https://en.wikipedia.org/wiki/Bcrypt#Maximum_password_length

I’m sure a lot of forks will pop up right around this time. I’ll be less skeptical of them once I see actual commits made to the codebase instead of things like just changing the readme

I hate to be that guy, but it doesn’t seem like there’s anything to this fork. At least a few links in the README don’t work, and the domain for the “email” is actively for sale. The owner of the repository doesn’t seem to have any real previous projects on their GitHub account.

I can understand that it’s a new fork, but in my mind you’d want to at least make sure the Readme is… passable before you spread the word and make a Patreon for the project.

EDIT: The Patreon link has been removed since I made this comment. I’m still incredibly skeptical of the project though

The brief explanation is that Nitter worked by creating “guest accounts”, which were a leftover from when you used to be able to use the Twitter mobile app without an account. After creation, these accounts lasted for a month. The time since the ability to create these accounts was removed is nearing (has reached?) a month

This guy goes by the name Skweezy Jibbs, and he’s actually a comedian! Look him up if you don’t know him, he’s done some pretty funny stuff. https://knowyourmeme.com/memes/people/skweezy-jibbs