opensearch VS Fenix

Or just right-click the input field, and if the browser recognizes it as a search field (they're good at it by default, but you can implement https://github.com/dewitt/opensearch to make extra sure), you'll get an option to create a search from it, with a keyword of your choosing (haven't tried Safari).

https://github.com/public-apis/public-apis https://data.gov.sg/developer http://opendatacommunities.org/ https://www.data.gov/developers/apis https://data.sfgov.org/browse?limitTo=datasets&utf8=? https://mashupaustralia.org/open-access-to-psi/ https://catalogue.data.govt.nz/dataset https://rapidapi.com/ https://www.programmableweb.com/apis https://rapidapi.com/collection/list-of-free-apis https://any-api.com/ https://compassioninpolitics.wordpress.com/2009/06/03/best-free-apis-for-web-developers/ https://rapidapi.com/pozzad/api/email-validator-1 https://public-apis.xyz/ https://developers.facebook.com/ https://dev.twitter.com https://www.programmableweb.com/news/5-weather-apis-weatherbug-to-weather-channel/2009/04/15 https://duckduckgo.com/api https://openweathermap.org/api https://github.com/dewitt/opensearch http://www.atomenabled.org/ https://openid.net/developers/ http://developer.foodessentials.com/ https://postcoder.com/docs/address-lookup https://github.com/public-apis/public-apis https://www.data.gov/developers/apis https://rapidapi.com/ https://www.programmableweb.com/apis https://rapidapi.com/collection/list-of-free-apis https://any-api.com/ https://compassioninpolitics.wordpress.com/2009/06/03/best-free-apis-for-web-developers/ https://rapidapi.com/pozzad/api/email-validator-1 https://public-apis.xyz/ https://www.programmableweb.com/news/5-weather-apis-weatherbug-to-weather-channel/2009/04/15 https://duckduckgo.com/api https://openweathermap.org/api https://postcoder.com/docs/address-lookup https://postcoder.com/docs/address-lookup http://vendapin.com/cecb46.html https://my-json-server.typicode.com/ https://jsonplaceholder.typicode.com/ https://reqres.in/ https://my-json-server.typicode.com/ https://randomapi.com/pricing https://randomuser.me/ https://reqres.in/ https://randomapi.com/pricing http://www.mindit-bookmarking.com/ https://theroadtodelphi.com/2010/08/07/using-the-google-maps-api-v3-from-delphi-part-i-basic-functionality/ https://theroadtodelphi.com/2010/08/07/using-the-google-maps-api-v3-from-delphi-part-i-basic-functionality/ https://www.geoapify.com/map-marker-icons-generator-create-beautiful-icons-for-your-map https://elevation-api.io/ https://open-elevation.com/ https://www.thoughtco.com/save-a-web-page-as-html-or-mht-1058361 https://theroadtodelphi.com/2010/08/07/using-the-google-maps-api-v3-from-delphi-part-i-basic-functionality/ https://www.programmableweb.com/apis/directory https://www.sitepoint.com/10-html5-apis-worth-looking/ http://www.99lime.com/elements/ https://docs.angularjs.org/api https://docs.angularjs.org/api/ng/service/$http https://docs.angularjs.org/api/ngMock/service/$httpBackend https://developers.google.com/earth/ http://www.worldwindcentral.com/wiki/Google_Earth_comparison https://theroadtodelphi.com/2010/08/07/using-the-google-maps-api-v3-from-delphi-part-i-basic-functionality/ https://jasontpenny.com/blog/2009/01/11/google-maps-in-a-twebbrowser-from-delphi-directions/ https://geochalkboard.wordpress.com/2009/03/11/density-mapping-in-google-maps-with-heatmapapi/ https://www.ixxat.com/products/products-industrial/protocol-sw-and-apis https://docs.microsoft.com/en-us/dotnet/api/system.componentmodel.backgroundworker?redirectedfrom=MSDN&view=netframework-4.7.2 http://custforum.axis.com/viewtopic.php?t=1963&sid=7990ea009d57544606efd627f3a40541 https://stackoverflow.com/questions/5137717/seeking-simple-coding-example-for-axis-webcam-using-vapix

I still quite like the idea of having a number of independent search engines each indexing their own specialist subjects, and one or more federated search front-ends which can pull these together.

Doing it with APIs is a little tricky to make work in a usable way though. There have been various attempts at standardised APIs, e.g. OpenSearch[0], and metasearch engines like searX[1] have what are essentially pluggable scrapers, but there are still fundamental issues like getting different results at different times and having different ranking mechanisms.

Integrating at the index level could make a more usable search, but there are lots of other issues with this approach, e.g. those with Apache Solr's Cross Data Centre Replication[2]. And yes, the volumes of data may also be an issue, given a search index will typically be slightly larger than the compressed data size, e.g. the 16M wikipedia docs are approx 32Gb compressed and approx 40.75Gb in a search index.

[0] https://github.com/dewitt/opensearch , unrelated to Amazon's Elasticsearch fork

[1] https://github.com/searx/searx

[2] https://solr.apache.org/guide/8_11/cross-data-center-replica...

GitHub

There is already an open source project called OpenSearch which used to be located on the same domain. The original project is a specification for how to share search results with a common API.

It's been that way for years: https://github.com/mozilla-mobile/fenix/issues/20351

I lost hope it and other issues would be fixed and moved to Chromium on Android.

Firefox for Android was rewritten pretty much from scratch circa 2020. Collections are one of its many unfinished and poorly-thought-out features, and they never got around to implementing the ability to sync Collections to desktop. It was a known problem in 2019, while the rewrite was being worked on, and Mozilla doesn't appear to have given it any attention in the years since.

People have been asking for this for over a year via Mozilla's current feedback channels, and for two years on the previous issue-reporting venue, to no avail. It was automatically moved from the old venue to Bugzilla ostensibly because Bugzilla makes it easier to track and work on issue reports, but they haven't actually worked on that issue report at all.

Known issue, not a new issue, and unlikely to be fixed any time soon, unfortunately. I had this before I stopped using the Android version a year ago. It was reported as a bug at least a year ago on their old issue tracker, and later moved to the current one, where last activity on the issue report was three months ago. No apparent progress toward any fix.

Since Fenix's first release they've been saying that the absurd limitations on add-ons support were only temporary, and they would have quickly increased the number of supported ones.

And instead absolutely nothing changed for three years.

Furthermore the insane bugs from which Fenix suffers from its release (https://github.com/mozilla-mobile/fenix/issues/12731) (making it unbearable) have been left hanging, focusing the few resources on dumb ui experiments.

So everything suggested that Mozilla did not care of its Android browser, or actually that they were deliberately sabotaging it.

This news instead represents a huge improvement, hence my bewilderment.

I don't know what people who downvoted my message thought I meant.

https://github.com/mozilla-mobile/fenix/issues/20012 and https://bugzilla.mozilla.org/show_bug.cgi?id=101865

This was sadly deprecated on Android: https://github.com/mozilla-mobile/fenix/issues/12099

It was such a huge loss for me that for at least a year I used the outdated pre-Fenix. Now they still work on Desktop but they just stopped working on Android (althouth the bookmarks itself are synced-up)