News for hackers. Stuff that matters.
Re:Anonymous Source Shared Leaked Google Search API Documents by ilrwbwrkhv on Tuesday May 28, 2024 @01:21AM (#40497563)
And that's why if a developer doesn't use Firefox and uses Chrome, they are just helping a monopoly take over everything and make a mess.
Re:Anonymous Source Shared Leaked Google Search API Documents by dgellow on Tuesday May 28, 2024 @01:30AM (#40497601)
Any user, not just developers
Re:Anonymous Source Shared Leaked Google Search API Documents by olliej on Tuesday May 28, 2024 @03:01AM (#40498131)
Developers just replaced IE as the only thing they develop for with chrome, users then _have_ to use chrome because of web developers who only develop for chrome and consider any behaviour other than "it works in chrome" as a bug in other browsers, just as they did with IE.

Then there's the relentless parade of "alternative browsers" that are just chrome skins - a period IE also went through - that intentionally try to trick people into believing they're not just using chrome but with less security engineering, and more scams.

Re:Anonymous Source Shared Leaked Google Search API Documents by dgellow on Tuesday May 28, 2024 @06:39AM (#40499293)
You’re conflating lots of unrelated things. IE was a horrible browser to support because Microsoft deliberately implemented their own incompatible version of web standards, or refused to implement modern standards. The push to deprecate IE was because it was creating a massive burden, I personally dealt with IE6 support in corporate world and can attest it’s depreciation was necessary.

What you call chrome skins isn’t a thing, people are building softwares on top of Blink, the rendering engine used by Chrome. The issue here is the risk of ending with a single rendering engine for the majority of the browser market, a diversity of engine ensure a good respect of web standards, that has nothing to do with privacy or security.

When you say “they just replaced IE”, that was >10 years ago…

Re:Anonymous Source Shared Leaked Google Search API Documents by jiggawatts on Tuesday May 28, 2024 @05:56PM (#40506037)
You’re responding to someone complaining about an overly authoritative government by saying that you don’t see the problem, it’s just that the local police force tortures people with downright medieval techniques.
Re:Anonymous Source Shared Leaked Google Search API Documents by dgellow on Wednesday May 29, 2024 @06:51AM (#40510522)
What
Re:Anonymous Source Shared Leaked Google Search API Documents by olliej on Wednesday May 29, 2024 @02:41PM (#40515288)
While I obviously disagree with your prior comment, I feel "What" is a pretty much perfect comment here. +1.

What.

Re:Anonymous Source Shared Leaked Google Search API Documents by jiggawatts on Wednesday May 29, 2024 @06:39PM (#40517918)
It seems like my analogy was too difficult to follow.

The point is that the fundamental problem is a company in a monopoly position throwing their weight around and/or keeping their product stagnant “because they can”, which is also a function of power. This is the “authoritarian government”.

The police part is referring to people thinking of specific IE6 technical issues “as the problem”, when it’s just a symptom of a larger problem.

Microsoft treated web developers badly because they could. Google will abuse the whole world in the same way now that Chromium has achieved near total dominance.

Re:Anonymous Source Shared Leaked Google Search API Documents by barbariangrunge on Wednesday May 29, 2024 @08:59PM (#40518982)
It became trendy recently to break compatibility with Firefox. Blogs almost bragging about how they boldly made the choice. Very embarrassing stuff
Re:Anonymous Source Shared Leaked Google Search API Documents by pseudalopex on Wednesday May 29, 2024 @11:30PM (#40519806)
Do you have examples? I would like to see how they talked about it.
Re:Anonymous Source Shared Leaked Google Search API Documents by barbariangrunge on Friday May 31, 2024 @10:40AM (#40535825)
It’s on hn here or there, or in random blog posts shared in here. Just keep your eyes open for a bit and you’ll see something pop up
Re:Anonymous Source Shared Leaked Google Search API Documents by metadigm on Tuesday May 28, 2024 @12:00PM (#40502105)
As soon as they add the ability to configure shortcuts, I'd more than happy to. After several years of requests, we're finally seeing some movement on their end.
Re:Anonymous Source Shared Leaked Google Search API Documents by HeatrayEnjoyer on Tuesday May 28, 2024 @03:11PM (#40504368)
Shortcuts? Like bookmarks?
Re:Anonymous Source Shared Leaked Google Search API Documents by cpeterso on Tuesday May 28, 2024 @07:07PM (#40506542)
Or search engine keywords in the address bar? https://support.mozilla.org/en-US/kb/how-search-from-address...

Or adding “top site” shortcuts on the Firefox New Tab page? https://support.mozilla.org/en-US/kb/customize-items-on-fire...

Re:Anonymous Source Shared Leaked Google Search API Documents by ilrwbwrkhv on Thursday May 30, 2024 @11:35AM (#40524941)
I hear you. But at the same time our duty on this planet as developers is to take one for the team when it comes to minor issues like this, which I am assuming this is for you. Otherwise the world will be consumed in the flame of the monopoly which others do not care about who do not understand browser engines.