unsure if its a problem with the twitter library im using or an issues with my usage of the library..... a test

yeah i think its the library.

tried every different combination that the library supports (pathname, array of unsigned bytes, based64 encoded string) and all of them failed.

in fact. it wouldnt even ACCEPT the base64 string. which was a lot of fun since that one was the most fucking involved.

guess i can throw a quick line in there about "hey if the file extension is .mp4 dont crosspost"

Show thread
Sign in to participate in the conversation