mitch292

I'm honestly not sure.

Definitely agree, not a fan of the permissions.

The broad permissions were required from a usability standpoint. Granting permission on every site for this extension would just be a 1 to 1 replacement of clicking reject on the banner or pop up for every site.

I would hope that before Chrome approves an extension to be added to the store that they are auditing the content of package.

Added some additional details under another reply in the same thread!

They had this in the reply

> How to rectify: Ensure your privacy policy contains details about user data collection, handling, storage and sharing. Omission of any section is not allowed.

So I added a section for each. I could make the "Information We Collect" section less verbose for sure.

This is 100% a fair point of view and you’re right to be skeptical. With the blog post I was just trying to convey that cursor + auto select model was not great at this task. It gave me a project structure, but besides that everything had to be refactored.

Agree! Unfortunately, that one was rejected by chrome.

Wrote with typescript across a number of different serverless services...long story haha. Wanted to use it as a learning opportunity as well on some new technologies.

- DB is Fauna which is pretty awesome and has a native GraphQL API - definitely worth checking out.

- The scheduler to kick off the process is hosted on a CloudFlare worker. Was very easy to set a cron to kick off a process. Surprised I hadn't run across similar functionality at other cloud providers before.

- The majority of the business logic is run with Deno on Deno deploy. While the package ecosystem isn't there yet, the sensible defaults for TS, built in linter and formatter and deployment product were great. Seems like it has a nice foundation for the future.

Overall I'm game for any product that lets me not maintain or think about servers and is not AWS...