imsteev

I could re-open and edit this issue accordingly if you want

With regard to "important" keywords, and to align with upstream mtree, 'flags' and 'nlink' (tar archive only) are keywords that should be looked at next.

yeah but for tar archives we would have to manually keep track of links

`nlink` keyword implemented for tar archives, although `nlink` for directory Entry's have not been implemented.

@brandongregoryscott yeah I followed the concept of that example in a Remix app -- the code is [here](https://github.com/imsteev/drip/blob/main/app/root.tsx) but you can see for yourself with these steps: 1. visit https://drip.fly.dev...

hmm, maybe grailed updated the selectors - their website has gone thru a lot of change since I first wrote this code

What do you mean by “algolia”? We can probably extract the item id - what would you be using this id for?

I am considering a rewrite for v2. will try to make the selectors as generic as possible, not having to rely on hardcoded constants.

Are these the only selectors that have changed? We should probably look into automation to test if “things work”