posobin

https://sphnx.dev

It actually works pretty well, but we're having trouble getting users (some sign up but don't end up doing even a single interview?!).

We're thinking whether we could sell a version of this to companies to do their technical screens in, perhaps with problems that are more similar to the actual software engineering work (e.g. debug existing piece of code, write tests, and extend it).

We're generous with interview credits if you give us good feedback =)

I do collect some telemetry statistics (right now the number of times you have seen the sidebar + the number of times you clicked/scrolled/closed it), aggregated hourly.

Would love to hear about your experience if you do use it!

But as I said elsewhere, in my experience I rarely use it myself since that requires a bit of effort to click and with an unknown reward it rarely seems worth the click.

I have actually seen your extension when I was trying to figure out how to get started with making one in cljs. I've used shadow-cljs though instead of figwheel.

You can see the actual permissions that ampie needs here: https://github.com/posobin/ampie/blob/master/build/manifest....

webNavigation together with tabs is needed to detect page URL changes correctly and update the sidebar (I don't remember exactly, but I think the main problem were pages that use history api to update the URL), storage is for localStorage to store extension settings, cookies to read/change cookies (limited to "https://ampie.s3.amazonaws.com/", "https://hacker-news.firebaseio.com/", "https://*.ampie.app/", to be able to get your auth token for ampie not to log in twice), unlimitedStorage was used previously because the caches of links stored were much more than the 5mb that is the default indexedDB limit. The caches are not used anymore, but I kept the permission so far because I am thinking of adding functionality for storing and visualizing your browsing history.

I am not sure what you would want to disable here.

If an extension includes content script that runs on all websites, then it can't avoid having the "read and change all your data on all websites": content script is JS code from an extension that runs on web pages, it can access the DOM and send requests. Ampie needs to run the content script on all pages to be able to add the sidebar. The other option is to run the content script on clicking the extension icon: as I mentioned elsewhere, while this approach might sound appealing in theory, the extension turns out to be much less useful this way as you simply forget/don't bother to click it and miss out on some interesting discussions.