I'm running a little backend API that requests pages from the Dreamwidth servers on your behalf using your login cookies, which lets the server get info from pages you have access to. This is why I need the cookie info.
Then it does a bunch of slicing and dicing to determine where threads start and end and filters it to the ones you participated in. Yay!
To both make things faster on the user side and less resource-intensive on the server-side, some data is cached so it can be re-used for multiple requests. The older a post, the longer the cache is kept, since those are unlikely to get new comments that would affect your counts.
If you really really really really need to, you can expire the cache with your request by ticking the box that says to expire the cache. Please try to do this sparingly, though!
Nope! The data passes through the server, gets passed to you, and all the processing and storage is done in the browser window. This means no one can get at private post information except people who are authorized to see it.
(If you want to see a little bit of how it works, go to the Web Inspector panel in your browser, go to the Application tab, and check the IndexedDb section. Did you know that your browser has been able to run a little key/value store database natively since 2015? I didn't until like. This project.)
nope because I do this for my own enrichment and love of the game. what's the point of having something solve my fun puzzle game for me
Sure! I have a repository on codeberg for it. If you find any bugs or want to suggest a feature (no promises!) you can also file issues there.
Email me at carly@veryroundbird.house with your idea and your budget and we can talk! Unfortunately I only do free stuff if I get a dwarf fortress fey mood but my rates for RPers are pretty reasonable.