Thanks for the feedback everyone, still tossing this around in my head atm.
But here's the rough plan.
I'm keeping it all within the profile pages, for me to access last posts on the fly means I need to hit the sub forums page (not cool). I have no guarantee that the user has laded on that page for linkify to read, thus I'm keeping everything in the profile page. Basically I'm avoiding extra http requests to find info.
So this means every time a profile page is viewed I take a snap shot of the last posted dates + the thread qfc. I then compare with previous snap shot. If the dates differ, there's new posts thus highlight the thread.
The thing is I can't save the new snap shot right away. This is because if you were to refresh the page all threads would appear to have no new posts, essentially comparing the data to itself.
So, if you go to a thread that's listed in your profile then I'll update the part of the snapshot that applies, next time you visit your profile that thread will no longer be highlighted but others will unaffected. Upside is this will work when viewing any profile that shares some of the same threads.
As for a link to where you last left off, that's something Rowley and I worked out and it's do-able. Since I'll already be taking snapshots of timestamps and Quick find codes I might as well include that feature. There is a little more too it, but it's something I should build in rather than add on later.
As for storage, linkify uses local storage (no cookies). This is for three reasons, cookies can't hold all the data I need. For example a friends list + clan list could exceed the capacity of a cookie. The other reason is speed, chrome.storage is fast and doesn't require a http request. And best thing is chrome.storage can hold objects rather than just text!
I still have lots to do and lots to test, but I believe having a more dynamic profile could make it a very useful tool.
Edit: grrr character limit :/
06-Sep-2015 06:35:42
- Last edited on
06-Sep-2015 06:57:26
by
Indecent Act