Page 1 of 20

***WARNING*** accounts don't log in - UPDATE feb 27th FIXED?

Posted: Fri Feb 23, 2024 3:18 pm
by Emin
everything's broken again :( :( :( :( :( :( :( :( :( :( :? :? :? :? :? :? :? :? :? :?
logs 22162

Re: accounts don't log in

Posted: Fri Feb 23, 2024 4:10 pm
by martin@rootjazz
Seems like twitter changed something over night. Currently looking at this

Re: ***WARNING*** accounts don't log in - feb 23rd 2024

Posted: Sat Feb 24, 2024 5:40 am
by Emin
no news yet Martin?

Re: ***WARNING*** accounts don't log in - feb 23rd 2024

Posted: Sun Feb 25, 2024 1:20 pm
by NOVA
Hi guys ! You have a 404 error too ?

Re: ***WARNING*** accounts don't log in - feb 23rd 2024

Posted: Sun Feb 25, 2024 1:37 pm
by Emin
yes

Re: ***WARNING*** accounts don't log in - feb 23rd 2024

Posted: Sun Feb 25, 2024 7:13 pm
by martin@rootjazz
Not looking good. Unlikely to be a quick and easy solution.


Seems there is a TLS finger print identifying not whitelisted TLS cipher libraries. Looking at solutions / work arounds....

Sorry

Re: ***WARNING*** accounts don't log in - feb 23rd 2024

Posted: Sun Feb 25, 2024 7:46 pm
by Emin
martin@rootjazz wrote: Sun Feb 25, 2024 7:13 pm Not looking good. Unlikely to be a quick and easy solution.


Seems there is a TLS finger print identifying not whitelisted TLS cipher libraries. Looking at solutions / work arounds....

Sorry

all accounts log in normally in jarvee
then I export cookies from Jarvee, import them into TD and everything works )))

Re: ***WARNING*** accounts don't log in - feb 23rd 2024

Posted: Mon Feb 26, 2024 3:17 pm
by martin@rootjazz
Emin wrote: Sun Feb 25, 2024 7:46 pm
martin@rootjazz wrote: Sun Feb 25, 2024 7:13 pm Not looking good. Unlikely to be a quick and easy solution.


Seems there is a TLS finger print identifying not whitelisted TLS cipher libraries. Looking at solutions / work arounds....

Sorry

all accounts log in normally in jarvee
then I export cookies from Jarvee, import them into TD and everything works )))
jarvee uses a browser, so will use the browser TLS library, which cannot be blacklisted

Re: ***WARNING*** accounts don't log in - feb 23rd 2024

Posted: Mon Feb 26, 2024 3:28 pm
by Emin
martin@rootjazz wrote: Mon Feb 26, 2024 3:17 pm
Emin wrote: Sun Feb 25, 2024 7:46 pm
martin@rootjazz wrote: Sun Feb 25, 2024 7:13 pm Not looking good. Unlikely to be a quick and easy solution.


Seems there is a TLS finger print identifying not whitelisted TLS cipher libraries. Looking at solutions / work arounds....

Sorry

all accounts log in normally in jarvee
then I export cookies from Jarvee, import them into TD and everything works )))
jarvee uses a browser, so will use the browser TLS library, which cannot be blacklisted
Yes, I understand (((
I said this just for information, I thought it would help you
when can we expect news from you, dear Martin?

Re: ***WARNING*** accounts don't log in - feb 23rd 2024

Posted: Mon Feb 26, 2024 3:30 pm
by zoltan66
martin@rootjazz wrote: Mon Feb 26, 2024 3:17 pm
Emin wrote: Sun Feb 25, 2024 7:46 pm
martin@rootjazz wrote: Sun Feb 25, 2024 7:13 pm Not looking good. Unlikely to be a quick and easy solution.


Seems there is a TLS finger print identifying not whitelisted TLS cipher libraries. Looking at solutions / work arounds....

Sorry

all accounts log in normally in jarvee
then I export cookies from Jarvee, import them into TD and everything works )))
jarvee uses a browser, so will use the browser TLS library, which cannot be blacklisted
Are there downsides from using a browser like in Jarvee? Like increased ban/ detection rate or more CPU power?