Kevin

Took a while because I couldn't receive any mails with my namecheap email and Netlify DNS. Found out over an hour later that I was still using Vercel DNS and forgot to switch.

I was expecting this to be quicker but it took a lot of time to get into the Twitter API. Lots of confusion, my main account not being allowed to register for a dev account and so on. I'm glad I finally got this one to work and any adjustments are fairly easy from now on.

Running scheduled via Firebase and writing the data to Supabase.

I was asked on Twitter to answer a bunch of questions about Supabase (seemed very legit, given the person that asked) and was offered $100 as compensation. Now I'll have to figure out invoices for foreign countries

Man, the amount of paperwork you have to do in Germany to get a loan is madness.

This took way longer than expected. There's V1 and V2 (alpha). There's multiple tiers and each tier may be able to use different query parameters or even content within query parameters. The official Postman collection for V2 uses the old OAuth 1.0, while the API does support OAuth 2.0 and some endpoint work with OAuth 1.0, but only when you're using specific parameters, otherwise they only work with a bearer token. This frustrated me a lot more than it should have. Anyways, finally figured it out.

Still need to implement the backend function to actually signup