Live data from Hacker News

Temptations of an open-source Chrome extension developer (2021)

github.com

371–374 of 374 posts

Re: Temptations of an open-source Chrome extension developer (2021)

#371

The root problem here is that there's no legitimate way to monetize browser extensions. Extensions are meant to be simple, so it's hard to sell premium features. Extensions usually don't "own" any space to embed ads in.

There used to be. https://developer.chrome.com/docs/webstore/money/ "The web has come a long way in the 11 years since we launched the Chrome Web Store. Back then, we wanted to provide a way for developers to monetize their Web Store items. But in the years since, the ecosystem has grown and developers now have many payment-handling options available to them."

Just want to put a plug in for https://extensionpay.com/ - I've used it in extensions in the past. It takes away the headache of setting up a backend for payment. They do take an extra 5%, but it's worth it especially. for smaller projects

Re: Temptations of an open-source Chrome extension developer (2021)

#372
If anyone's around here and isn't adverse to actually being paid for developing extensions in a non-shitty way, I built https://github.com/dougwithseismic/monetize-this and use it in my own extensions.

I get that it's noble to hold a position of 'no way, I will never monetize, I am a shining white knight' but lets be real, we all gotta eat. If you choose not to then that's great, Im glad but please; monetization !== shady shit.

There's just an overlap.

Re: Temptations of an open-source Chrome extension developer (2021)

#373

Earlier quoted context omitted.

What does that mean in reality? Pretty sure Chrome Web Store extensions are reviewed, but since they're all minified and obfuscated garbage, I wonder how easily malicious code could slip through. I'm surprised there hasn't been a mass cookie stealing attack yet.

CWS doesn't review every extension submission, at best they do some % of them along with anything that sets off red flags. Out of hundreds of times I pushed updates to my extension (~100k monthly users by the end) it was delayed for human review maybe... twice?

maybe its time for a LLM based security review open source framework. this could be adapted for extensions to see what information they'd be sending over.

Re: Temptations of an open-source Chrome extension developer (2021)

#374
post #221

Earlier quoted context omitted.

Couldn't you do the same with tv shows and ads?

At least on iOS, not without hacking the operating system. Siri’s ability to listen for a wakeword without an microphone indicator requires privileges that normal apps don’t get. On Android, as far as I can tell, the same is true, except that some phones ship with preinstalled third-party apps which can then get extra privileges.

It runs on a specific coprocessor, even.
Post reply on HN