@forestjohnson doesn't really work cause the indexeddb order is not the same as (various different) timelines

@f0x Well it could be tho.. there's no reason why the keys in IndexedDB can't have the timestamp as the 1st part of the key.. Then different timelines are just different filters on the same sorted set 🤔

I predict that you'll end up de-normalizing the data at least a little bit or at very least having multiple "indexes" within the indexedDB in order to look things up in various different ways.. But I could be wrong lol, Ive never tried to make a fedi client

@forestjohnson it could sorta work, but timelines aren't actually chronological, they use the server received timestamp which I don't think is exposed

rn I just have arrays of timeline sections in redux/localStorage (with just id+uri), and indexeddb tables for toots and accounts, indexed by uri, and a toot links to the uri of the account, and boosted toot (if it is a boost)

@forestjohnson but also I only *just* tried out indexeddb and it's bedtime now, so we'll see