Google's Carlo sort of does that. It uses your system's already-installed Chrome instead of packaging another one.

https://github.com/GoogleChromeLabs/carlo

While we've started with outbound fetch/HTTP, we certainly plan on adding additional functionality over time.

Hi there! I'm one of Osgood's authors.

To clarify a few things:

1. Any tool that reduces the privileges of your application code, such as Osgood or Deno, is doing so because application code cannot necessarily be trusted, since you're pulling in external dependencies that can have vulnerabilities or malicious code, and even one's own code may have unknown vulnerabilities that may cause unexpected IO behaviour to happen.

2. The policies you can set with Osgood are defined in a JavaScript file that is run separately from your application code (i.e. the worker files), and it only runs once to build up the policy data structures in native code. This V8 Isolate is then discarded. This means that application code cannot modify its own policies.

I hate to nitpick but this is definitely a North American Dialect Map, rather than just an American Dialect Map.

Thanks! I hadn't seen share.js before. I'll have to look into it.

In my case, I was denied entry due to a paperwork error in Toronto and so had to stay at a hotel to catch a flight the next day. It would have been nice had everything been arranged and applied for ahead of time.

Hmm, I don't want to be spammy, but this could be a good idea. Anyone else have thoughts on this?

People sign up to your list because they are interested in content you provide. No one will mind, and it will certainly improve your sales once you do launch.

I did this with my book. 0 unsubscribes.

It wont seem spammy if it is well executed. Just make it easy to unsubscribe from the tips without unsubscribing from the book notification. Also, make it clear in the first email that the recipients only signed up to get notified about the book but that you thought it would have been useful to send periodic tips. Also be sure that the tips have are posted on the web, so they can be shared and viewed without having to reference an email.

Much like others have said, when people sign up for content giving them content isn't spammy. Do include an unsubscribe link. Also include a subscribe link, include content worth forwarding, and sell more books.

Edited to add: Might want to have a "just tell me when the book is ready, no more o' these" just in case. But really, if people aren't interested in content similar to what's in the book, why are they buying the book?

Actually it's a pretty good idea, maybe even better than the book itself. I'd be glad to receive vim tips everyday in my e-mail.

You could also take the approach the Django Book originally did. Posting the book online while you write, with editing help from the community and a print version available once complete. I would definitely buy the print version as well as use the web reference.

I agree to the daily or maybe have an option for a weekly thing, but I am not sure how this will match up with the model/book you have planned out so far.

I think it's a great idea, especially if the tips are concise and easy to absorb.

send the emails with an unsubscribe link. you'll be fine.

Yes please.

I would not view that as spammy at all.

Will add that soon!

Just an ebook to start. If there's enough interest, I'll see about doing a print edition.

Thanks!