After reading an article here on HN, I gave Brave a crack for a week but returned to my regular browser. The thrill of dopamine hits from earning a BAT oken for viewing a brave-blessed ad for the underprivileged wasn't worth changing a browser for.
A "drop in replacement for Chrome" just isn't my thing as a Firefox user - I just didn't love the browsing experience otherwise.
If the company were to expand their market for postive-ads and crypto coins by releasing a Firefox plugin as a "drop in replacement for uBlock Origin" it might tickle my fancy.
Yeah I never understood why Brave rewards only works in their own browser. Seems like they're kinda limiting their userbase with this all-or-nothing approach.
Their goal is to change the incentives around web browsing and privacy. It becomes much harder to do that if they help other browsers retain their marketshare.
Yes, to see what the fuss was about with respect to donating those coins to creators.
I didn't view sufficient ads to be rewarded with any crypto in the timeframe (monthly?) and none of the webpages I visit regularly seemed to be eligible for BAT donations. The latter seems a chicken and egg problem; it's an opt-in system for the website administrators who might already have alternative monetization (Google ads, patreon).
Looks like camera is open. I wonder if it possible to tweak software to get unholy quality out of sensors like Pixel phones do, or does one need to have high power/integrated GPU or TPU hardware for it.
The unholy quality on pixel phones is achieved through taking many pictures and combining them in smart ways (Google's computational photography wizard Marc Levoy has given a great series of lectures about the theory behind it: https://www.youtube.com/playlist?list=PL7ddpXYvFXspUN0N-gObF...) through a Qualcomm Hexagon processor, which has a special VLIW (Very Long Instruction Words) architecture. This co-processor is in every high-end Snapdragon (800 series) phone made in the last few years and you can relatively easily get the software to run on them through modded Google Camera versions commonly known as "Gcam ports".
My actual point is: You don't need special camera firmware to do this.
What you do need special (or open enough) firmware for is stuff like long exposures - the inability of which highly frustrated me on the phones, especially from Sony, I have owned so far. Doing weird stuff with the camera will probably be quite fun, but then again I don't believe the actual camera device will be that good.
Stories about killing Hitler and saving millions of lives are a staple of science fiction, and an interesting way to reason about time travel.
I created that thread as a creative exercise for others to partake in good, light-hearted fun. Despite the subject, there were absolutely no cases of misbehavior. That's what you get when you're in a heavily moderated community that takes being nice to each other very seriously.
Yes, I did. 'Light-hearted fun' perhaps but it strikes me as in very poor taste as someone whose parents lived through the 1940s. Okay, you went there - to its logical conclusion in which your time adventures messing around with the past inadvertently sees the Axis win the war and the 1000 year reign commences as forseen. And nobody wants that.
'a heavily moderated community that takes being nice to each other very seriously' would describe this forum, for the most part. Thus my reluctance to join another community comprised somewhat of HN invitees merely to discuss topics HN might find taboo such as time travelling assassination of historical figures.
For Android, they're proposing GKI module shims that a vendor can code against. So a vendor plugs a binary blob into, say a 5.4 GKI module, which is hopefully forward compatible with the interface to a 6.25 GKI module released sometime in 2026.
They are, but it is only post Android 10, so it will take years before it matters at all.
As an example, Vulkan was added in Android 7 as optional API, the adoption was so low, with so many buggy drivers that as of Android 10 it became a compulsory API.
On Android everything that Google leaves the OEMs free reign hardly gets done.
Understood but the point being made is that your OEM will build AOSP with some ancient, say 2017 or whenever your device was released, embedded version of chromium - susceptible to security flaws from that release date. Chrome overlays a replacement engine to ensure webapps don't get p@wned.
So yes, as a firefoxee, I never want to see the Chrome icon. However, purging Chrome is a security risk.
Here in Australia, the local council expects you to keep the nature strip, or verge, between the road and the pavement looking presentable but anything behind the front fence is your own creation.
And so the 'front lawn' is my vegie patch. Potatoes are dead easy to grow from eyes and pumpkins (winter squash) self-germinate from compost. This summer I'm experimenting with Jerusalem artichokes, which sprouted from 70¢ worth of store-bought tubers.
All you need is water and a spade - and no lawn police, I guess.
VSCode, say, as a slimmer download sans web runtime is a possible outcome.