This Package Saved My SaaS

121,132
0
Published 2024-06-16

All Comments (21)
  • @WebDevCody
    The Twitter backend engineers while implementing that token param: “nobody’s gonna know. How would they know?”
  • @jugalgadhavi
    That one jira ticket will speed run itself from backlog to in-progress
  • @requestfx5585
    "it can break at any time" I think that that time was set when you uploaded this video for thousands of people to see
  • @FlorinPop
    I just read it as: "This packages saved my ass"
  • @Khari99
    Only Sid would post about a security vulnerability that is needed to make his application work lol
  • @Parajulibkrm
    yes Josh, you don't look like that guy, that guy looks like you instead.
  • @nickolaki
    Speedrun before twitter patch the underlying solution 😂
  • @megamind452
    Thanks for reporting this bug, it will be fixed in this current sprint - X engineer after watching this
  • @davisphem
    The creator of react-tweet must be an undercover spy at X 😅
  • @algobuddy
    Dude, this is like a game-changer for small developers and startups!
  • @hipdev_
    The creator of react-tweet is my brother, I'm so proud of him 🤗!
  • @dabbopabblo
    I theorize that how they generate the token probably changes regularly to combat this, but nothing stops you from scraping the code that generates it and extracting the new method on a whim.
  • @Nin_Cada
    This video was so informative that we got to see his twin brotha.
  • @0xPanda1
    Its interesting but the down side is Twitter may change something in thier thus the code would stop working
  • @LongBoy.0
    I'm still not clear on what's actually happening. why is a syndicate URL? did they just scrape and reverse engineer the database? or did they just figure out how to reverse engineer real twitter api keys that actually work?
  • @_gekyumeman4127
    I had this same problem earlier last year. So i spent some time reverse engineering the twitter embed API myself and worked like a charm.