eejdoowad

Gave it a spin and it feels really polished!

Since you offered... I'm curious about the rendering technology behind it. I'm working on a web app with a spreadsheet interface, and I'm using a standard canvas-rendered grid.

You obviously have different design constraints, so it would be interesting to see how they shaped your solution.

Cool idea and onboarding experience. I spun up Chrome to demo it, and although its got the rough edges of a prototype, the potential is there.

I created a rule to remove thumbnails and shorts from YouTube, and after a few failed attempts, it succeeded! But there were massive tracts of empty space where the images were before. With polish and an accessible way to find and apply vetted addons so that you don't have to (fail at) making your own, I would consider using it.

My daily driver is Firefox, where I've set up custom uBlock Origin cosmetic rules to personalize YouTube by removing thumbnails, short, comments, images, grayscaling everything except the video, etc. My setup works great for me, but I can't easily share it with other people who would find it useful.

Love the concept and design.

Where are repositories stored and do you use any sort of backup or replication?

It works well and I like the overall design. Why'd you make it?

The default keyboard shortcuts are a little awkward; using tab or the up/down arrows to navigate the list would be more intuitive. Also, it would be easier to distinguish tabs if the title were displayed before the hostname.

It's really cool to see the applications made possible by the high quality, reasonably priced, and fairly licensed text-to-speech APIs offered by AWS, Azure, and Google Cloud.

The most fleshed out service of this type that I've found is narro.co, which offers web/pdf/epub/video/rss/email/text to audio conversions.

Keylogging is just the beginning. Any (and many) browser extensions have the ability to record everything you do on every page you visit. All it takes is specifying the <all_urls> permission in the extension’s manifest and adding some event listeners.

It has to work this way or browsers wouldn’t be truly extensible. Be mindful of which extensions you install.

Great work. It’s a pleasure to use. A few questions:

1. Have you heard of Narro (narro.co)? It does the same thing, but it’s been around longer and has many integrations.

2. Can you share the tech stack currently powering your voice synthesis? Since it’s called PollyPodcast, are you currently using AWS Polly for TTS?

3. Is this something you intend to monetize?

4. It seems like you offer unlimited readings for free. Do you have an abuse prevention strategy? This could become a hole in your wallet if you’re paying for a charged-per-character TTS service.

5. Creating custom voices is a great differentiator. What are some problems you have to solve to create them and how is this effort progressing? Do you have quality and performance goals?

Looking forward to this update.

I wonder if it will be possible to load scripts into the reader view document. Currently, it isn’t, so keybinding extensions, which rely on inserting Keyboard event listeners, don’t work in reader view. I had been prototyping a custom reader view in Saka Key using Mozilla’s Readability library to work around this issue.

The Content Security Policy fix is a lifesaver. Saka Key attaches hint elements to the DOM and attaches a script tag to load common styles/fonts. Sites with the policy style-src: self (like crates.io) block script tags, which breaks hint styling and positioning.

My understanding is that if they do implement an API, they want it to be better than the status quo, not the same.

What happens when two extensions try to place a widget in the same location? Chaos. Not that the status quo is any better.

Interestingly, Firefox's sidebar API only allows a single sidebar to be shown.

An extension overlay API would have saved me so much pain when building Saka (saka.io). There are two options for injecting UI today:

1. Inject UI directly into the document

2. Inject an iframe containing the UI into the document

Both rely on manipulating the document, which can be used to fingerprint users. Most developers opt for 1 because it requires no setup and lets the content script synchronously access the UI. 2 is needed when the injected UI containing sensitive information.

I'd like an extension overlay API that lets you inject: 1. UI local to the tab 2. UI that persists across all tabs

In a brief #webextensions IRC discussion, I was told an overlay API isn't viable for a number of reasons, one of which is multiple extensions may conflict.

Just wanted to mention, one of the unique features of Saka Key is that it lets you define keybinding profiles that are easy to switch between, and there are multiple profiles built in, including one that mimics Vimium.

The address bar autofocusing is annoying. Best advice I have is to replace your new tab page with a URL or a custom new tab extension.

Also, I devised the default keybindings with three goals in mind.

1. Common keys should be easy to reach.

2. Users unintentionally trigger dangerous commands (like close the current tab). To prevent this, I bind dangerous commands to 2 key sequences.

3. Users not being able to remember keybindings. To help users remember, I try to associate commands with an intuitive key, e.g. Zooming is mapped to z.

Saka key author