#[snarfed]early experience with Twitter v2 API: it has cleaned up and simplified a _ton_ of data model cruft that had accumulated over the years to handle Twitter-the-product's accumulated cruft:
#[snarfed]@-reply canoe prefixes to tweet text, t.co URL suffixes for attached photos and videos, retweets and quote tweets, id_str, text vs full_text vs display_text_range vs truncated, etc
#[snarfed]also conversation_id is a game changer, I can finally stop doing crazy complicated @-mention searches and manually building reply threads based on in_reply_to_screen_name in_reply_to_status_id
#[snarfed]likes too, I can finally stop scraping the internal API's favorites page HTML and JSON
#[snarfed](of course, all of this conditional on whether the 2M tweets per month cap is enough for Bridgy. there's a very good chance it's not. but they're planning to open up higher quota tiers soon)
#[snarfed]still TBD whether API v2 is actually good. but it's definitely not slowly-boiled-frog-bad like 1.1 was, so I'll take it
#[tw2113_Slack_]it's been years since I really did anything with the Twitter API and even then it would jut be cached latest X tweet for a client site
#[snarfed]heh. Bridgy's usage is obviously pretty involved
angelo, [jgarber] and petermolnar joined the channel
#[KevinMarks]That's encouraging [snarfed] - do you want to write it up publicly so we can help lobby for limit increases, or are you saving that for when you have done a full update?
mro, cybi, tetov-irc, gRegor, totertats and jacky joined the channel
#[snarfed][KevinMarks] maybe eventually! I'm not worried, they're very clearly and loudly planning higher tiers
jacky, cybi and therussbain joined the channel
#therussbainQuick "survey" - did you build your own "Notes" app for cross-posting or did you use a canned CMS?