harvard-lil
Determine if Perma capture has changed
When we index a link we should hash its essence.
When someone visits a Linky link, we should go out to the original url and grab its essence and hash it. If the hash looks the same as our stored version, we indicate that to the user. If it's changed, we indicate that to the user.
Essence might be thought of as the Instapaper/Readability capture.
We might want to cache this so we don't hit the original source every time. A TTL of a day or two or a week might be close.
decided not to do this for now. (I think ingrid's code for solving this is still in, but commented out.)
Would it make sense to tag stuff like this "future" (or some other roadmap-type tag, like "roadmap_2.0", "roadmap_future") so we can pull up a list of enhancements that are closed for now but still might be good to look at one day?
That sounds like a good idea. What's the best way to do this using GitHub issues? We can create a milestone called "future" or "roadmap_future" or "wouldnt_it_be_nice", or we can apply a label. I kind of like the milestone approach. Thoughts?
Oh -- I hadn't used milestones before. Interesting.
Milestones look like the right tool for the job, but it might be slightly annoying that the default Github view doesn't show what milestone an issue belongs to. So maybe use a wouldnt_it_be_nice milestone, but keep the issues in it closed until they're resuscitated so they don't clutter up the default view?
Either would work, but I think labels are a better fit than milestones. For instance, you could create a "wishlist" label and use that as a sort parameter on the issues page. This has two advantages: (1) you don't have to assign a due date for the whole collection of wishlist items, and (2) you can assign wishlist items to different milestones.
Yes, maybe labels are more flexible for this. I like that we can indicate that it's a "wishlist" type feature and not have to go track down what milestone it's in or should be in. We already use the "enhancement" label and this logically feels very similar.
Oh, dang it! I thought I could create a freeform label (one called "wishlist"), but I don't think GitHub supports freeform label creation. So, maybe a milestone?
Sorry for the spam. Just realized that I had to go to the main issues page in order create new labels.