darinf

Appreciate the work the WebKit team is doing, but would love to see more support for WKWebView devs. The WKPreference updates are nice, but such a small step. As a browser developer targeting iOS (where one is forced to use WKWebView), it is shocking how many hacks are required to build table stakes features on top of WKWebView. Of course, I can imagine the Safari team would have little motivation to help in this regard since it is about enabling competition.

There's another approach.

How about greater transparency around the trustworthiness of sources? Maybe that would be a better way than censorship to slow the rampant spread of misinformation across the internet?

Full disclosure, I work for Neeva. Our search engine is different. With Neeva, we give you more information about the source and you get to decide which news sources you trust. You are in charge of deciding what is right for you -- not global tech companies making decisions in private rooms.

Because over a decade ago the Apple devs poo-poo’d all over the premise of this API when it was first proposed. I’m referring to its earlier incantation that we added to WebKit and shipped in Chrome but could never get Apple devs to support. I’m delighted to see it supported now. I just think of all the lost time for the web and what could have been.

Better late than never?

This gets to the heart of of why we created Neeva.

A product that fundamentally breaks the misaligned incentives between serving results for you and serving advertisers. I have been at this for a long time and the freedom to innovate that comes out of removing ad-revenue is liberating.

Our team is constantly creating new and better features to push what can/should be expected in search such as FastTap that gets you results without sending you to a SERP, or enabling you to search across third party apps like Dropbox, or more useful info about the page you are on.

We recently launched a free and paid premium version with the goal of making it available for anyone to try it.

Are we at parity yet with Google? On some things I would say yes, on others no, but is anyone else? What I can say since joining is that the product and deeper query results get better everyday.

Barely six months out of beta and we are running fast, feeling like the old days when building Chrome...

Check out Neeva. Ad free search. We have an iOS browser at the moment and desktop browser extensions. Both apply tracking protections.

Disclaimer: I work for Neeva :)

If you are looking for an alternative, try Neeva. Being ad free means we aren’t beholden to advertisers, and unlike the other alternatives such as DDG, Neeva isn’t just a wrapper around Bing results. Hope you enjoy it.

Give Neeva a try. We have improved ranking and some nice features around tech queries.

Thanks for trying Neeva! We’d of course love any feedback thru the in app support feature.

Yes, you can get around the geo restriction using a VPN. Note of course that the experience will not be optimized for your locale if you are outside the US (e.g., local searches for restaurants and such will not work well).

Neeva has a full featured free tier by the way. Glad you are enjoying it. Agree it sucks that Apple doesn’t let you choose Neeva as a default for Safari. The Neeva extensions on macOS and iOS provide a workaround that still lets you search from the URL bar.

You are in complete control.

See the FAQ for more details (https://neeva.com/faq), but the main takeaway is data saved by Neeva is only to improve the product for you and you have the option to clear or disable such functionality. Neeva is just really transparent about that.

Neeva is a tool for you and no one else. Products that show you ads can’t make such claims.

Neeva is another option for privacy minded folks. Plus it is ad free, and Neeva is also much more than just a wrapper around Bing results.

Disclaimer: I work on Neeva :)

You might confirm that your video driver is up-to-date.

One of the coolest features in this release:

""" When content changes above the viewport, Chrome now automatically adjusts the scroll position to keep content in the viewport fixed unless the CSS overflow-anchor property is set. """

This is just reverting a change that was found to be bad. Returning to a known good state makes sense.

It is unfortunate that Apple does not allow us to bring all of Chromium--our full rendering stack (Blink, etc.)--to iOS. If they did, we could build a much better browser for iOS. Instead, we are forced to use their provided WebView, and that means living with its limitations and bugs.