Paul Frazee
Paul Frazee
> An alternative way to do this would be to have a known dat archive with a list of archive keys in it; a user would append to that list...
Immediately before or after, that's the plan. On Tue, Nov 29, 2016 at 11:25 AM, Julian Gruber wrote: > does that mean whenever you create a new checkpoint that afterwards...
Could we do something more free-form, but then slugify the value to act as the repo name?
Why do you think this is worth adding? Did you have a specific moment you felt like it would've helped out?
@da2x Right it makes sense, but I can't think of a specific feature that I'd implement around this. The "Go to HTTP/S version" badge appears when we auto-redirect you from...
Yeah
I think some people still rely on this. I'd like to deprecate in favor of https://github.com/beakerbrowser/dat-node but haven't had time to get that repo fully formed up. Im +1 to...
Looking good! A few requests: - Can we put the localPathTemplate on `DatArchive` instead of passing it into create? You'd set the template by attaching the function to the class...
Yeah, [not yet implemented](https://github.com/beakerbrowser/node-dat-archive#differences-from-browser-api). PRs accepted.