-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Here's another one I had today: https://duckduckgo.com/?t=ffab&q=maan+leo&ia=web
Maan Leo is a Dutch author. DDG gives me a few bad results about Maan Leo, a few bullshit links about horoscopes ("Make a Leo man chase you"), and finally the Wikipedia page for Low Earth Orbit (LEO).
The Google search gives me results about, well, Maan Leo (in spite of using Indonesian search by the way – this GeoIP stuff Google does is so annoying). For this particular term, DDG is basically useless.
The Brave search results also seem a lot better by the way. Certainly loads better than DDG.
I haven't used Google for many years, so I can't speak to whether it shows personalized results today. But, I recently switched to Whoogle Search (https://github.com/benbusby/whoogle-search) which shows Google results but without the tracking. I am happy with it, that I have completely ditched DuckDuckGo in favor of it.
We do indeed use Chromium, though patched for security and privacy reasons (see https://github.com/brave/brave-browser/wiki/Deviations-from-...). I don't see how that's an ethical or technical mark against us, however. Early on we did tests with Gecko, but soon found that if we were to build a compatible (with the Web as it is) browser, we'd need to do so with Chromium.
Your claim that Brave collected donations on behalf of others is quite misleading. There was a bit of confusing UI in our early tips interface (called 'Payments' at the time). We clearly marked verified creators as such, but gave no special marking for unverified creators (our approach resembled that of Twitter's blue checkmarks).
Regarding the "donations" themselves, we allowed Brave users to direct BAT from our user-growth pool (that is, Brave's own tokens) to creators. If those tokens were not claimed by the intended recipient after 1 year, they (Brave's tokens) would be recycled back into the system. As Wikipedia records, there were major UI/UX changes made about 48 hours later which dramatically improved the feature, IMHO.
If you're using uBlock, you can one-click block remote font loading in the badge popup menu (or write custom rules using the no-remote-fonts: or *$font syntax). This will force a fallback to system fonts, which should be viable.
(This hardly the "best" solution, but, everyone has uBlock installed, and it's a 5-second hack).
https://github.com/gorhill/uBlock/wiki/Per-site-switches#no-...
https://felvin.com/ is trying to build "Search profiles", but it's still quite early.
Related posts
-
What do you use for site search? Custom built solution? Meilisearch? Algolia?
-
MiniSearch – fuzzy match search in TypeScript
-
Minisearch: Tiny, powerful JavaScript full-text search engine for browser, Node
-
Lyra: Fast, in-memory, typo-tolerant, full-text search engine in TypeScript
-
Your Search Engine On Adrenaline