I get that there might be some complexity involved with flushing data, but after using IndexDB in production I don’t understand why it isn’t more popular. Doing complex queries, storing large amounts of data, consolidation, it’s all so clean and efficient. Way more than doing it in memory. (Assuming you’re using something like Dexie.js)

#DexieJS #javascript #webdev #webdevelopment

Good morning. It looks like rain!

Instead of giving you the digest of me reading the accumulated traffic from overnight. There was stuff like quote boosts displayed via browser extension. I'm going to say that I'm surprised about a few things how Buffalo has turned out.

• First, it's basically what I wrote because implementing something Mastodon API like seemed limiting and hard when I wrote bovine. It's a React based Single Page ActivityPub Client. It currently assumes one is authenticated via cookies.
• Second, due to me using dexie.js because IndexedDB seemed complicated, and dexie.js not supporting filtering + ordering, I don't have a chronological feed. I barely notice.
• Third, displaying a conversation + swiping left to dismiss it: is fantastic navigation. By combining this with collapsing "seen" posts, I have probably a unique FediVerse navigation experience.

Anyway, that's it for me padding myself on my own back. This is also to say: I'm approaching 0 idea what people are talking about when complaining on how the FediVerse works. My experience is becoming VERY distinct.