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

Support / help / discussion forum for twitter bot
Post Reply
Emin
Posts: 492
Joined: Mon Apr 22, 2019 6:54 am

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

Post by Emin »

everything's broken again :( :( :( :( :( :( :( :( :( :( :? :? :? :? :? :? :? :? :? :?
logs 22162
User avatar
martin@rootjazz
Site Admin
Posts: 34712
Joined: Fri Jan 25, 2013 10:06 pm
Location: The Funk
Contact:

Re: accounts don't log in

Post by martin@rootjazz »

Seems like twitter changed something over night. Currently looking at this
Emin
Posts: 492
Joined: Mon Apr 22, 2019 6:54 am

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

Post by Emin »

no news yet Martin?
NOVA
Posts: 5
Joined: Mon Jan 18, 2016 6:58 pm

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

Post by NOVA »

Hi guys ! You have a 404 error too ?
Emin
Posts: 492
Joined: Mon Apr 22, 2019 6:54 am

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

Post by Emin »

yes
User avatar
martin@rootjazz
Site Admin
Posts: 34712
Joined: Fri Jan 25, 2013 10:06 pm
Location: The Funk
Contact:

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

Post 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
Emin
Posts: 492
Joined: Mon Apr 22, 2019 6:54 am

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

Post 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 )))
User avatar
martin@rootjazz
Site Admin
Posts: 34712
Joined: Fri Jan 25, 2013 10:06 pm
Location: The Funk
Contact:

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

Post 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
Emin
Posts: 492
Joined: Mon Apr 22, 2019 6:54 am

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

Post 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?
zoltan66
Posts: 168
Joined: Sat Nov 30, 2019 8:19 pm

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

Post 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?
Post Reply