Why would you have AI generate your content for you? What possible benefit is there in that for anyone (other than helping to fill the internet with more AI generated junk)?
Also, is 'Coppiotkit on Githhub' the same as 'CopilotKit on Github'? π
π± π± π± π± π± sounds like someone doesn't want to 10x their posts on twitter π± π± π± π± π±
Do you not even AI bro ?
π€π π€ π Here's 3 projects I'm working on to help speed up productivity π€π YOU WONT BELIEVE NUMBER 2 (im shoving open AI coppiotkit straight up my ass) π€ππ€π π€ π
I'm torn... This was actually a really good article... but the goal and title, not so much. Why on earth would you want to 10x your posts with crap AI content? That's part of the whole problem with how AI is being used right now.
Systems engineer and Open Source contributor/maintainer. Has his head in the clouds, CI, virtualization, containerization, orchestration. Loves those ations....
I think this is a great walkthrough on how to setup and integrate a project with Twitter API and their OAuth 2.
I do have a few comments though.
In the npx create-next-app social-media-scheduler step for Would you like to use /src directory? question you show Yes. Throughout the rest of the example steps this is never used or suggested the user move into src before following additional steps, maybe that was not used in your setup as multiple steps later don't seem to account for a ./src directory. For example:
During section The Dashboard Page the user would still inside social-media-scheduler directory:
cd app
mkdir dashboard && cd dashboard
touch page.tsx
During section Authenticating users via X it also leaves out the ./src directory. However, the user's terminal would still be inside ./src/app/dashboard from prior step of making page.tsx, no step moved back to social-media-scheduler and the start of this section does not suggest starting a terminal from the project root again.
cd app
mkdir api && cd api
mkdir twitter && cd twitter
touch route.ts
During section The Dashboard Page the user is instructed to create a utils file, not a util.ts file:
src/app/dashboard/page.tsx: import { availableSchedule } from "../util";
src/app/components/App.tsx: import { formatTime, tableHeadings } from "@/app/util";
src/app/page.tsx: import { getTwitterOauthUrl } from "@/app/util";
Naming it either utils, or util leads to errors in npm run dev causing the site to not work and no Sign in with Twitter button to be accessible.
I think resolving these very small oversights would allow a complete novice to follow your post, remove any confusions about paths, and any compilation errors they would otherwise run into.
Even with these minor issues I still think its a worthwhile read and a good walk through. Thanks for the article!
Software developer and tech enthusiast with a passion for creating innovative solutions. Proficient in various programming languages and experienced in developing API's.
Genuine questions:
Why would you have AI generate your content for you? What possible benefit is there in that for anyone (other than helping to fill the internet with more AI generated junk)?
Also, is 'Coppiotkit on Githhub' the same as 'CopilotKit on Github'? π

π± π± π± π± π± sounds like someone doesn't want to 10x their posts on twitter π± π± π± π± π±
Do you not even AI bro ?
π€π π€ π Here's 3 projects I'm working on to help speed up productivity π€π YOU WONT BELIEVE NUMBER 2 (im shoving open AI coppiotkit straight up my ass) π€ππ€π π€ π
π
I'm torn... This was actually a really good article... but the goal and title, not so much. Why on earth would you want to 10x your posts with crap AI content? That's part of the whole problem with how AI is being used right now.
I think this is a great walkthrough on how to setup and integrate a project with Twitter API and their OAuth 2.
I do have a few comments though.
In the
npx create-next-app social-media-schedulerstep for Would you like to use/srcdirectory? question you show Yes. Throughout the rest of the example steps this is never used or suggested the user move intosrcbefore following additional steps, maybe that was not used in your setup as multiple steps later don't seem to account for a./srcdirectory. For example:social-media-schedulerdirectory:During section Authenticating users via X it also leaves out the
./srcdirectory. However, the user's terminal would still be inside./src/app/dashboardfrom prior step of makingpage.tsx, no step moved back tosocial-media-schedulerand the start of this section does not suggest starting a terminal from the project root again.utilsfile, not autil.tsfile:import { availableSchedule } from "../util";import { formatTime, tableHeadings } from "@/app/util";import { getTwitterOauthUrl } from "@/app/util";Naming it either
utils, orutilleads to errors innpm run devcausing the site to not work and no Sign in with Twitter button to be accessible.I think resolving these very small oversights would allow a complete novice to follow your post, remove any confusions about paths, and any compilation errors they would otherwise run into.
Even with these minor issues I still think its a worthwhile read and a good walk through. Thanks for the article!
This is awesome, man!!!
π₯π₯π₯
Nice one Nevo!
How did you create that cover image?
Really nice tutorial, but don't love the title.
Great One!
Great article Nevo!
Cool, more AI spam on the internets. Good job