Live data from Hacker News

Let's guess what Google requires in 14 days or they kill our extension

blog.pushbullet.com

711–720 of 811 posts

Re: Let's guess what Google requires in 14 days or they kill our extension

#711

Earlier quoted context omitted.

If you have a half-decent router or firewall, this won’t work from outside the network.

Huh? What kind of router would filter out 127.x responses by default? Also, this wouldn't work with DoH enabled which is where we're heading with browsers.

It’s about negating security mechanisms that rely on the request/target "origin".

Re: Let's guess what Google requires in 14 days or they kill our extension

#712

I think the interpretation that Google does this because it does not want to compromise the review process to malicious extension authors is a very generous one. As others pointed out, a motivated enough entity could very well be probing the system using multiple submissions (sure it gets your account banned, just use several accounts). No what is really going on is that Google wants the ability to reject an app for…

don't create extensions. create browser controllers. you can release them as binaries. anyone can download them. They instrument chrome using the remote devtools API. an oss example here: https://github.com/dosyago/22120 and an idea I have for a browse controllers store here. https://github.com/dosyago/browsercontrollers.store

hm, interesting, though I'd worry that running a server on localhost might be a little more than most people would bargain for

Re: Let's guess what Google requires in 14 days or they kill our extension

#713
I’m surprised Google et al. haven’t been forced to make more contractual disclosures at the time of a user submitting an extension or app.

Absent blaring warnings like “you understand that if you build any type of business on this platform we reserve the right to destroy it at any time for any reason”, it’s pretty hard to see how users had any ability to understand the implicit and explicit contracts they were entering into.

This isn’t much different than “Nathan for You” style hiding of onerous terms deep in hilariously small fine print, and judges tend not to look fondly on such games.

Re: Let's guess what Google requires in 14 days or they kill our extension

#714

This is a good extension but here is a cool hack I've discovered that let's you do this anywhere without any chrome extensions: - Create a new whatsgroupp called 'ping self' and add your friend to it. - Then kick your friend out from this group - Open web.whatsapp.com and now you can access your messages, files, photos across any device anywhere, anytime! (telegram also does this and allows file up to 1gb)

I've replaced Pushbullet with Telegram as I already use it for daily communication.

Telegram's built-in "Saved Messages" is where I share links, files, text snippets, photos, etc. for follow up and archiving; seamlessly between my devices and the Telegram desktop app.

Telegram also has an export feature, so I can backup all (thousands) of saved URLs, messages, media files, and so on for offline safe keeping; both in human and machine-readable formats.

Re: Let's guess what Google requires in 14 days or they kill our extension

#715
post #535

Earlier quoted context omitted.

Are you making a good faith suggestion that it's possible to build a business around a browser extension and not support Google Chrome? They have something like 70% market share dude...

Chrome’s market share would drop if extension authors moved to an alternative. As it is, it sounds like Google’s doing this itself by breaking popular extensions.

maybe what we're really seeing is an alternative - users don't care enough about the quality of the extensions ecosystem. Otherwise browsers should be racing to have the best extension ecosystem.

Re: Let's guess what Google requires in 14 days or they kill our extension

#716

Earlier quoted context omitted.

Zero chance this will happen without a much bigger party involved

Under the Clayton Act, the Sherman Act, or both? Is this a legal realism commentary on the comparative cost-benefit of civil antitrust litigation in modern America? Or are you just pretending you know things to feel good on the internet.

I was going to respond in earnest, but then I read the second paragraph. If you want a civil discussion you might hold the insults next time.

Re: Let's guess what Google requires in 14 days or they kill our extension

#717
post #677

Earlier quoted context omitted.

It's so difficult to imagine a) getting ahold of someone at Google who can actually help you, and b) having some sense of assurance that they will actually help you. "Google deleted my X" posts always rise to the top on HN because they elicit a strong emotional response from developers. I think it's worthwhile to reflect on why that happens. For me, it's because I absolutely despise seeing an algorithm have control o…

I don't understand how people work for these companies as developers and implement these policies and systems and aren't just as angry about it and don't stand up to their supervisors over it: if frankly makes me have a really low opinion of people who work for Google, Apple, etc. :/.

They get a few hundred thousand dollars a year to do it. If you're working for a global surveillance ad tech company, you're obviously not there for the good things they do, you want the money. And they give them the money.

Re: Let's guess what Google requires in 14 days or they kill our extension

#718

Earlier quoted context omitted.

don't create extensions. create browser controllers. you can release them as binaries. anyone can download them. They instrument chrome using the remote devtools API. an oss example here: https://github.com/dosyago/22120 and an idea I have for a browse controllers store here. https://github.com/dosyago/browsercontrollers.store

hm, interesting, though I'd worry that running a server on localhost might be a little more than most people would bargain for

server just for settings. you could do through a website, but just for ease I did it that way.

Re: Let's guess what Google requires in 14 days or they kill our extension

#719
post #673
post #518

Earlier quoted context omitted.

I can only assume that this isn't the result of a human flagging Pushbullet like this; I expect it's an automated system. And if that automated system can make a decision to flag the extension, it could also include in the email specifically what caused that flagging to happen. At this point I'm really starting to become unsympathetic to the idea that they can't tell you what you're doing wrong because it'll enable p…

I agree, and will go further in that I believe they actually should have such an obligation: it should be a consumer right to find out why you were denied access to a platform--or a restaurant, or a barber shop, or a wedding cake maker, or whatever else that someone is refusing you service due to, as a business operating in the public--and that whatever reason that is must be something that either 1) has nothing to d…

I was ready to get behind this line of reasoning, but then I thought about e.g. comment sections. Anyone who has moderated a forum will know that trolls find every possible way to walk right up to the line without technically crossing it.

If you say "personal attacks aren't allowed", they'll say "I wasn't attacking him personally, I just suggested that anyone who says [the thing he said] should consider getting evaluated by a doctor for mental retardation."

At some point you just have to say "I know what you're doing, you're clearly not acting in good faith, and I have to ban you." Are all of those people now potential lawsuits?

Re: Let's guess what Google requires in 14 days or they kill our extension

#720
I wonder why the cookies permission is requested. It's not needed to communicate with .pushbullet.com, as in that case the normal cookies which have been set by Pushbullet will be sent along in the extension's requests to .pushbullet.com. It is only needed to access 3rd party cookies.
Post reply on HN