Live data from Hacker News

Viewing profile — dotproto

dotproto

HN member
Joined
Sat, Oct 12, 2019, 11:00 PM UTC
HN karma
90
Public activity
48 items

About dotproto

https://dotproto.com https://github.com/dotproto https://www.linkedin.com/in/simeonv/

Recent public activity

  1. comment
    Comment #48592340

    Ctrl+Click / Cmd+Click also opens in a new tab.

  2. comment
    Comment #48416924

    As someone involved in the WebExtensions Community Group who has been (slowly) trying to figure out what, if anything, we should do at the platform level around these use cases, I …

  3. comment
    Comment #48416624

    Oh, this is interesting! I assume most of the heavy lifting to identify and filter content is being performed by the content script. In practice have you see any issues with models…

  4. comment
    Comment #48299381

    Do you mean Firefox on iOS? If so, that would require the firefox-ios project to adopt BrowserEngineKit, which is relatively new. Firefox for iOS WebExtension support is being trac…

  5. comment
    Comment #45034234

    Also pretty easy with Firefox's new profile manager https://support.mozilla.org/kb/profile-management

  6. comment
    Comment #45033828

    Just took a quick glance at your extension and observed that it's currently using the "debugger" permission. What features necessitated using this API rather than leveraging conten…

  7. comment
    Comment #41736253

    Simeon from the Firefox Add-ons team here. Sorry about the rocky experience. I realize this is a bit late for your situation, but earlier this year the source code submission docs …

  8. comment
    Comment #41172969

    Asking as a browser contributor, what do you feel is missing from MV3?

  9. comment
    Comment #40725770

    I was about to say "concurrent writes shouldn't be a problem because localStorage is synchronous and JS is single-threaded," but then I started thinking about multiple tabs, WebWor…

  10. comment
    Comment #40225076

    Would love to hear your thoughts on how to improve it ;)

  11. comment
    Comment #40225013

    Can you share more about what you find frustrating or confusing about this process?

  12. comment
    Comment #40224996

    Chrome extensions are published on Chrome Web Store ( https://chromewebstore.google.com ), not on Google Play.

  13. comment
    Comment #40224653

    I don't know exactly what the the person you're replying to had in mind, but support for different parts of the manifest varies (especially in Manifest V3). While it's possible to …

  14. comment
    Comment #39630371

    To my knowledge no browser supports transferring an extension's user base from one extension to another. If you want your users to switch, the only think you can do is show them a …

  15. comment
    Comment #39630354

    Both CWS (Chrome) and AMO (Firefox) supports this. It's part of Chrome's One Stop Support[1] form and Forefox's developer hub UI. At the moment I don't believe any browser has feat…

  16. comment
    Comment #39630296

    > The extension ID is derived from a private key that the developer uploads with the first upload to the app store While what you described is possible, this process isn't required…

  17. comment
    Comment #39137741

    Sounds like literal rent seeking behavior.

  18. comment
    Comment #38576767

    > If the idea is that these DNR rules require non-fast-trackable thorough reviews, but dynamically updating them will bypass those thorough reviews, than I am at a lost to understa…

  19. comment
    Comment #37407090

    No one does at the moment. The deprecation is on hold, but Chrome has stated that they "will provide at least 6 months between a timeline announcement and any experiments deprecati…

  20. comment
    Comment #37298365

    > I wonder if the main obstacle to (actual) cross-browser extensions isn't so much technical but rather political. Normally when browser folk talk about "cross-browser extensions,"…

  21. comment
    Comment #37264478

    > the extension APIs are standardised enough that this is actually possible a lot of the time A bit off topic, but as a co-chair of the WebExtensions Community Group[1] (WECG) I'm …

  22. comment
    Comment #37263904

    > The biggest problem I found is that Chrome Manifest V3 requires background.service_worker (they removed background.scripts), while Firefox Manifest V3 requires background.scripts…

  23. comment
    Comment #33029137

    This was a mistake and has been corrected.

  24. comment
    Comment #32955426

    > Absent security issues, what's the value of the last N releases of Chrome? How far do you have to go to get something of value that changed? IMO something of value changes with e…

  25. comment
    Comment #32906531

    A couple hours ago I added a comment to the bug to describe our current plans[1]. TL:DR; you'll be able to use webRequest.onAuthRequired in MV3. [1]: https://bugs.chromium.org/p/ch…