Live data from Hacker News

Our Chrome Extension Is Safe

blog.pushbullet.com

61–70 of 206 posts

Re: Our Chrome Extension Is Safe

#61
post #7

> All of that attention resulted in our issue being resolved. This is good for us. It is not yet clear if the attention will help other developers that are struggling with similar vague rejections. I think it's been made abundantly clear that Google will not, in fact, improve anything from experiences like this. They happen over and over and every single time it's the same; if it gets publicity, someone helps resolve…

Have a look at this https://twitter.com/ArtemR/status/1261159338170658816 and the surrounding discussion. This is basically the only person at Google who can make things happen if there's a problem with Chrome extensions.

Or the pm whoever that is now

Re: Our Chrome Extension Is Safe

#62
post #56

Earlier quoted context omitted.

It might be difficult to impossible to currently implement, but perhaps if you have access to :// /* you should lose access to pretty much every other permission.

That wouldn't help much. For example, with read/write access to your banking website a malicious extension could inject a script tag that exfiltrated data to their server.

I know, that's why I say it's difficult to impossible to implement at the current time. I do think it is an interesting goal.

Re: Our Chrome Extension Is Safe

#63
post #57
post #13

Earlier quoted context omitted.

Always has been for 10+ years now. As a former Call Center Director, it's pretty amazing to me how much bad-will these massive companies are willing to foment by not running their support correctly. It's not that hard / expensive guys... you can hire great support employees for $20 / hour all across America.

Are these great $20/hr support engineers the kind I often deal with over email or phone, who usually employ canned responses, can’t solve off-script problems, tend to repeat the same unhelpful responses, and are sometimes indistinguishable from bots?

Those are $9.25 an hour support agents who are paid mostly to get you off the phone and take 70 calls a day.

Or their $10.25 an hour tier 3 "supervisors" who you might escalate the call to.

Re: Our Chrome Extension Is Safe

#64
I'm less qualified to opine on Google than most of the people here, but in hindsight, what Google products remind me of is the way that black walnut trees slowly poison the soil so that the seedlings from other species of tree cannot grow nearby. The good intentions that poured energy into all the 20% products are no longer the point. Somewhere along the way, someone figured out how to use them strategically. The free products are good, good enough to use, until you realize that there is no path for continued growth or investment of resources, and run into seemingly arbitrary disappointments and limitations; it as if at some point, someone stopped the projects from adding cool utility to the product, and started making sure that hindered, crippled versions of the feature were offered instead. I experience this most acutely with the languishing "Google My Maps" product. It feels as if the target is not just potential competition, but the imagination and demand of the market itself.

I don't actually know the story of Google Reader and RSS feeds, but I remember how integral RSS feeds were to the golden era of blogging, and how abruptly that era seems to have ended with Google Reader's apparent death. And to me, that has a similar feeling. The idea is that the target is not potential competition wherever it might spring up; the idea is to sap the demand that might nourish competition, to suck the air out of the room, and stifle the imagination of the market itself.

It isn't Google alone who is responsible for this feeling, to be fair. There is watching the growth of the walled garden of Facebook, watching the collapse of the old chat services which allowed independent clients, watching successful startup after successful startup turn new ideas into content for a routine process wherein we see the exact same sheen of gloss on the promises, the same dance steps towards the pirouette, the attempt to pivot gracefully and effortlessly towards monetization in a maneuver that is in fact a mating dance desirous of acquisition.

All of it really sucks. It's not like there's an easy alternative. People like free things, and with computer-based resources there is often so much opportunity to scale the value of a thing that free things can be sustainable; a project can succeed and be useful to thousands of people merely on the basis of the labour that some are willing to commit to to sustain it. Again, I'm less qualified to describe this than most of you are. But that's what open source is like.

It doesn't work with services. Code that runs of different platforms can be replicated/adopted for infinitesimal cost, and the underlying costs of running it are naturally distributed. Services are different. The replication/adoption and the creation of value both involve on a massive rush of the many to the one. That relationship pretty much sums up the whole story. If capital accrued to capital by a square law, attention would accrue to attention by a cube law. In idiosyncratic niches that cannot be satisfied by the mass service, alternatives are actually viable and flourish. But anything that would be beneficial to us all encounters this problem of needing to absorb the real costs of operation while seeming to be as free as possible, or else the users will flit away to a different flower.

There's no good solution to this, but the way in which Google has graciously assumed responsibility for directing our attention does not make it better. All the improvements to search results over time seem to focus attention more and more to what an archetype of user is likely to be satisfied with. I would not be surprised if the energy costs per search had gone down. As many have noted, esoteric results are increasingly invisible.

Anyways, this is what we have done with the new universe of human communication that has opened up in the last few decades, which we imagined we would leverage into new systems of effortless communication and collaboration. And we have, to a lesser extent. Second best or third best. But we've discovered this really intractable problem with the distribution of costs.

Re: Our Chrome Extension Is Safe

#65
post #52

Earlier quoted context omitted.

Wow. That's pretty lame of them. I don't agree with their logic, but I do agree with following the user base. I will continue to use the version I have. I could probably find a way to share the .app if anyone needs it. Found pushover.net which seems like a decent (paid) alternative. We need an open-source version of this kind of functionality, maybe using ActivityPub? Self-hosted option with Google integration for a…

Not so sure about lame of PushBullet. It feels more lame of all of the major tech players to be essentially fighting over how much they can extort out of developers using their monopoly powers. Facebook seems to say, you have 1 week to update your sign-in integration code to the latest version (or I guess they get cut off from Facebook API or something?). Apple says you must support Apple sign-in, or you won't be all…

Well microsoft now owns Github, NPM, VS Code, TypeScript, I wonder how that can go wrong...

BTW, between them and facebook (React, GraphQL) that pretty much sums up my stack/tools of choice

Re: Our Chrome Extension Is Safe

#66
post #23

Earlier quoted context omitted.

Is it really hard to understand? The answer is always money.

Are there any examples of free services that don't directly make a company money that include great support? I am struggling to think of any.

Since when are G Suite and Pixel phones free products?

Re: Our Chrome Extension Is Safe

#68

Can someone from Google use a throwaway to explain why the hell their support is garbage. From the Chrome store, to G-Suite, to Pixel Support. It's just awful.

I know from an associate that their experience with GCP makes it seem like they aren’t able to handle the edge cases for customers. My associate tells me that GCP sales team will talk up all the capabilities, but when it comes time to move from a competing provider, it’s like a new road for them. Unforeseen outages because something that scaled well in AWS/Azure is not scaling as it should in GCP. Chalk it up to new learnings for the team, but having to reach out to GCP to fix or allow something that AWS/Azure already makes easy to do shouldn’t be difficult, or a surprise.

Re: Our Chrome Extension Is Safe

#69
The problems with the Chrome store are likely not over. What good is it if you have to stir up half the internet to get through their process?

It's not as if developers can go to other platforms since Chrome has 70% of the market. Most of us in tech are in it to innovate and disrupt but hard to do that if everything is a Google or Amazon monopoly.

If Chrome is broken then the browser market is broken. Devs should organize to solve this since Google doesn't seem to be paying attention.

We need to collect and organize feedback from those experiencing problems which is everyone. Get it to antitrust folks in the EU and DOJ to start an investigation (to add to their other investigations). If Google knows the EU and Feds are watching, they might start behaving.

Re: Our Chrome Extension Is Safe

#70

You know this wouldn't be so much of an issue if Chrome didn't disable the ability to install extensions outside of the web store. As an extension developer its absolutely infuriating to realize that: 1. There is no way to install extensions outside the web store 2. Google won't approve anything to the web store. 3. The vast majority of people use Chrome vs other browsers. ------ I get it, Chrome is Google's browser…

Maybe just maybe, you will consider Firefox.

1. Same or better performance

2. Open source for real not just (pretending to be) Open Source

3. More transparent process

4. No business conflicts

Support Firefox if you care about the open web

Post reply on HN