Does "Export" included cookies?

[papamax]

Just saw this and tried... While the custom export does export the cookies in BASE64, upon conversion to JSON they look exactly the same as the version from 'export cookies' button... which means they DO NOT work on any other browsers and are only good for TD

[martin@rootjazz]

Just saw this and tried... While the custom export does export the cookies in BASE64, upon conversion to JSON they look exactly the same as the version from 'export cookies' button... which means they DO NOT work on any other browsers and are only good for TD

does your browser not take JSON cookies? Do you know what format it does take?

[papamax]

Just saw this and tried... While the custom export does export the cookies in BASE64, upon conversion to JSON they look exactly the same as the version from 'export cookies' button... which means they DO NOT work on any other browsers and are only good for TD

does your browser not take JSON cookies? Do you know what format it does take?

It is not my browser, it is any browser! If you try to import the exported cookies into chrome using an extension that takes JSON, like EditThisCookie it does not work. I tried multiple of those extensions for chrome, none accept the format from TD. IF you install one of those and export cookies you will see what format is required by chrome to accept it.

It is something like this below -- I have used https://jsonformatter.org/ to beautify it to an entry per line for easier visibility here

[
{
"domain": ".twitter.com",
"expirationDate": 1687719785.921086,
"httpOnly": false,
"name": "d_prefs",
"path": "/",
"secure": true,
"session": false,
"value": "MToxLGNvbnNlbnRfdmVyc2lvbjoyLHRleHRfdmVyc2lvbjoxMDAw",
"sameSite": "unspecified"
},
{
"domain": ".twitter.com",
"expirationDate": 1706382186.810116,
"httpOnly": false,
"name": "guest_id_ads",
"path": "/",
"secure": true,
"session": false,
"value": "v1%3A167216816195603414",
"sameSite": "no_restriction"
},
{
"domain": ".twitter.com",
"expirationDate": 1706382186.810176,
"httpOnly": false,
"name": "guest_id_marketing",
"path": "/",
"secure": true,
"session": false,
"value": "v1%3A167216816195603414",
"sameSite": "no_restriction"
},
{
"domain": ".twitter.com",
"expirationDate": 1706382186.810199,
"httpOnly": false,
"name": "personalization_id",
"path": "/",
"secure": true,
"session": false,
"value": "\"v1_28OjQGtBBJUNfVj2UwC+Zw==\"",
"sameSite": "no_restriction"
},
{
"domain": ".twitter.com",
"expirationDate": 1706382240.321766,
"httpOnly": true,
"name": "kdt",
"path": "/",
"secure": true,
"session": false,
"value": "BHhF0LAf1kINoaKs4FuiLf8c9dGcSx9sHBddq0yR",
"sameSite": "unspecified"
},
{
"domain": ".twitter.com",
"expirationDate": 1706382319.274504,
"httpOnly": true,
"name": "auth_token",
"path": "/",
"secure": true,
"session": false,
"value": "f861a3aad822a0084256b8f0e78d6550993bcca2",
"sameSite": "no_restriction"
}
]

[papamax]

This is what TD outputs... there are some differences between that 2 formats that causes it not to be accepted by the browsers

[
{
"Comment": "",
"CommentUri": null,
"HttpOnly": false,
"Discard": false,
"Domain": ".twitter.com",
"Expired": false,
"Expires": "0001-01-01T00:00:00",
"Name": "guest_id",
"Path": "/",
"Port": "",
"Secure": false,
"TimeStamp": "2022-12-15T19:15:39.7498045+02:00",
"Value": "v1%3A167102685942635642",
"Version": 0
},
{
"Comment": "",
"CommentUri": null,
"HttpOnly": false,
"Discard": false,
"Domain": ".twitter.com",
"Expired": false,
"Expires": "0001-01-01T00:00:00",
"Name": "gt",
"Path": "/",
"Port": "",
"Secure": false,
"TimeStamp": "2022-12-15T19:15:39.7498045+02:00",
"Value": "1603033160186580992",
"Version": 0
}]

[martin@rootjazz]

Ok, must be a microsoft cookie difference to browsers. Really only
name
value
domain
path

are required, but capitilisation is the issue. I don't know


For now you can open the account in the SESSION BROWSER, then export from the chrome instance which I guess will be formatted how you need into whatever browser you are wanting to use. Not ideal I admit, but only solution for now