Does "Export" included cookies?
Posted: Sat Feb 19, 2022 3:32 am
The EXPORT from TD is for TD to import it again. Not to be used on other systems, hence it's a custom format.
yes, I also wondered why cant I use cookies from twitterdub on other browsers.martin@rootjazz wrote: ↑Tue Jan 10, 2023 12:56 pmThe EXPORT from TD is for TD to import it again. Not to be used on other systems, hence it's a custom format.
Unsure how browser would read them, I "guess" JSON format, but it's just a guess.
When time permits, I can check it out and add support for external cookie import and export in various formats. But for now, I'll have to add it to the suggestions list:
The suggestion has been noted and added to the feature suggestions list. Depending on the demand for the change / feature will alter how quickly it gets implemented.
As others have asked for the option to prioritise their feature, I'm just letting you know (it's by no means compulsory) if the feature is very important to you, we do offer the chance to sponsor the feature to get it developed ASAP. If interested write in with your budget (it's simple, the more you pay bigger the priority will be for further discussion: support[at]rootjazz[dot]com
darude wrote: ↑Mon Jan 23, 2023 1:25 amyes, I also wondered why cant I use cookies from twitterdub on other browsers.martin@rootjazz wrote: ↑Tue Jan 10, 2023 12:56 pmThe EXPORT from TD is for TD to import it again. Not to be used on other systems, hence it's a custom format.
Unsure how browser would read them, I "guess" JSON format, but it's just a guess.
When time permits, I can check it out and add support for external cookie import and export in various formats. But for now, I'll have to add it to the suggestions list:
The suggestion has been noted and added to the feature suggestions list. Depending on the demand for the change / feature will alter how quickly it gets implemented.
As others have asked for the option to prioritise their feature, I'm just letting you know (it's by no means compulsory) if the feature is very important to you, we do offer the chance to sponsor the feature to get it developed ASAP. If interested write in with your budget (it's simple, the more you pay bigger the priority will be for further discussion: support[at]rootjazz[dot]com
but it is easy to use cookies from a browser into twitterdub.
so it comes out in base64 json format?martin@rootjazz wrote: ↑Mon Jan 23, 2023 10:33 pmdarude wrote: ↑Mon Jan 23, 2023 1:25 amyes, I also wondered why cant I use cookies from twitterdub on other browsers.martin@rootjazz wrote: ↑Tue Jan 10, 2023 12:56 pm
The EXPORT from TD is for TD to import it again. Not to be used on other systems, hence it's a custom format.
Unsure how browser would read them, I "guess" JSON format, but it's just a guess.
When time permits, I can check it out and add support for external cookie import and export in various formats. But for now, I'll have to add it to the suggestions list:
The suggestion has been noted and added to the feature suggestions list. Depending on the demand for the change / feature will alter how quickly it gets implemented.
As others have asked for the option to prioritise their feature, I'm just letting you know (it's by no means compulsory) if the feature is very important to you, we do offer the chance to sponsor the feature to get it developed ASAP. If interested write in with your budget (it's simple, the more you pay bigger the priority will be for further discussion: support[at]rootjazz[dot]com
but it is easy to use cookies from a browser into twitterdub.
I think I added CUSTOM EXPORT to the right click menu recently. It will export a base64 JSON cookie representation.
Doubt browsers take a base64 cookie string though, but you could decode it and use that (maybe)
Yes, it's sort of normal for EXPORT / IMPORT files to base64 long lines of text, otherwise the text could contain , or \t or other charactors breaking the CSV. So with base64 encoding it comes out as just numbers and lettersdarude wrote: ↑Mon Jan 23, 2023 11:18 pmso it comes out in base64 json format?martin@rootjazz wrote: ↑Mon Jan 23, 2023 10:33 pm
I think I added CUSTOM EXPORT to the right click menu recently. It will export a base64 JSON cookie representation.
Doubt browsers take a base64 cookie string though, but you could decode it and use that (maybe)
Depends on browser, I guess JSON representationand into what format do I have to format it to be able to work in browsers?
(im using dolphin antidetect browser)
nice, thank you.martin@rootjazz wrote: ↑Tue Jan 24, 2023 5:24 pmYes, it's sort of normal for EXPORT / IMPORT files to base64 long lines of text, otherwise the text could contain , or \t or other charactors breaking the CSV. So with base64 encoding it comes out as just numbers and lettersdarude wrote: ↑Mon Jan 23, 2023 11:18 pmso it comes out in base64 json format?martin@rootjazz wrote: ↑Mon Jan 23, 2023 10:33 pm
I think I added CUSTOM EXPORT to the right click menu recently. It will export a base64 JSON cookie representation.
Doubt browsers take a base64 cookie string though, but you could decode it and use that (maybe)
Depends on browser, I guess JSON representationand into what format do I have to format it to be able to work in browsers?
(im using dolphin antidetect browser)
https://www.base64decode.org/
will encode / decode for youS