{"id": 1429701072348647425, "user": {"value": 33521530, "label": "swyx"}, "created_at": "2021-08-23T07:04:32+00:00", "full_text": "@chantastic @alexandereardon @sveltejs (it actually does compile to JS under the hood, but the impedance mismatch is far lower\n\nits a joke-but-not-joke that the Svelte ecosystem is larger than React's because its a superset of HTML, the first language of the web, with the attendant teachability/compatibility benefits)", "retweeted_status": null, "quoted_status": null, "place": null, "source": {"value": "1f89d6a41b1505a3071169f8d0d028ba9ad6f952", "label": "Twitter Web App"}, "truncated": 0, "display_text_range": "[39, 319]", "in_reply_to_status_id": 1429699966444851202, "in_reply_to_user_id": 12745092, "in_reply_to_screen_name": "chantastic", "geo": null, "coordinates": null, "contributors": null, "is_quote_status": 0, "retweet_count": 0, "favorite_count": 6, "favorited": 0, "retweeted": 0, "possibly_sensitive": null, "lang": "en", "scopes": null}
{"id": 1429888354192019476, "user": {"value": 33521530, "label": "swyx"}, "created_at": "2021-08-23T19:28:44+00:00", "full_text": "\ud83c\udd95 Blog: Why Isn't Usage Based Billing A Bigger Category?\n\nhttps://dev.to/swyx/why-isn-t-usage-based-billing-a-bigger-category-m8b", "retweeted_status": null, "quoted_status": null, "place": null, "source": {"value": "1f89d6a41b1505a3071169f8d0d028ba9ad6f952", "label": "Twitter Web App"}, "truncated": 0, "display_text_range": "[0, 81]", "in_reply_to_status_id": null, "in_reply_to_user_id": null, "in_reply_to_screen_name": null, "geo": null, "coordinates": null, "contributors": null, "is_quote_status": 0, "retweet_count": 2, "favorite_count": 29, "favorited": 0, "retweeted": 0, "possibly_sensitive": 0, "lang": "en", "scopes": null}
{"id": 1429941443863347206, "user": {"value": 33521530, "label": "swyx"}, "created_at": "2021-08-23T22:59:41+00:00", "full_text": "@TomerAberbach np :) API design is a pet topic of mine. As I build up my career in the \"Developer Experience\" industry I hope to develop my own strong opinions on what an ideal API design (and design process) looks like.", "retweeted_status": null, "quoted_status": null, "place": null, "source": {"value": "1f89d6a41b1505a3071169f8d0d028ba9ad6f952", "label": "Twitter Web App"}, "truncated": 0, "display_text_range": "[15, 220]", "in_reply_to_status_id": 1429940285715460098, "in_reply_to_user_id": 708470652693565440, "in_reply_to_screen_name": "TomerAberbach", "geo": null, "coordinates": null, "contributors": null, "is_quote_status": 0, "retweet_count": 0, "favorite_count": 1, "favorited": 0, "retweeted": 0, "possibly_sensitive": null, "lang": "en", "scopes": null}