The Weekly BAT Ep. 58 — Gemini Trading Widget now available in Brave v1.13 (desktop), Interview w/ Donny Dvorin (Brave Head of Sales), Enter using BAT for a chance to win Apple AirPods Pro (via TAP Network)

Announcement: Gemini trading widget now available in Brave v1.13 (desktop), making it easier for users to buy, sell, store, & earn crypto when using Brave. (Plus, upcoming payment for Creators using the new Gemini Creator Wallet.)

We are excited to announce that Gemini and Brave have partnered to make it easier for users to buy, sell, store, and earn crypto when using the Brave browser. This integration allows users of the Brave desktop browser (version 1.13) to engage with crypto via the new Gemini Trading Widget in a simple and secure manner. 

Starting today, Brave desktop users can access the Gemini Trading Widget (the “Gemini card”) from the Brave browser New Tab page to seamlessly trade any crypto asset listed on the Gemini Exchange, as well as view their Gemini account balances and access their deposit addresses – all without ever leaving the Brave browser ecosystem.

Read the full announcement here:

Official Brave blog: WebBundles Harmful to Content Blocking, Security Tools, and the Open Web (Standards Updates #2)

In a Nutshell…

Google is proposing a new standard called WebBundles. This standard allows websites to “bundle” resources together, and will make it impossible for browsers to reason about sub-resources by URL. This threatens to change the Web from a hyperlinked collection of resources (that can be audited, selectively fetched, or even replaced), to opaque all-or-nothing “blobs” (like PDFs or SWFs). Organizations, users, researchers and regulators who believe in an open, user-serving, transparent Web should oppose this standard.

While we appreciate the problems the WebBundles and related proposals aim to solve,[1] we believe there are other, better ways of achieving the same ends without compromising the open, transparent, user-first nature of the Web. One potential alternative is to use signed commitments over independently-fetched subresources. These alternatives would fill a separate post, and some have already been shared with spec authors.

Read the full post here:

Read More