Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Helium Browser

helium.computer

Post reply on HN
Print view View original

531–540 of 561 posts

Re: Helium Browser

#531

Post by yupyupyups »

fastball wrote: post #447
yupyupyups wrote: post #260

Earlier quoted context omitted.

Yes it has, unless they plan to do significant changes to how the relevant JS APIs function, which is usually prohibitively expensive to maintain. Standard Chromium allows websites to fetch a lot of fingerprintable bits, this is even true for Brave. Tracking protection on Chromium is a joke. Firefox on the other hand is better in this respect and even has a setting explicitly for resisting fingerprinting.

Last time I checked, Brave was actually the best-in-class for resisting fingerprinting.

Calling Brave "best-in-class for resisting fingerprinting" is quite bold. Especially when it's so easily disproven.

Try some good fingerprint testing sites on Brave and see what comes up (those results alone should chock you). Then try the same sites on Firefox with privacy.resistFingerprinting=true. Unless some truly revolutionary initiatives have been taken at Brave since last I checked, you will see Firefox do A LOT better than Brave.

Brave suck at resisting fingerprinting. It may be better than other Chromium-based browsers, but it's still pathetic.

Re: Helium Browser

#532

Post by blicsd »

godelski wrote: post #124

> Helium is based on Chromium > Best privacy by default Sorry, pass... Even with un-googled Chromium I do not think these statements are self-consistent. We need browsers that do not allow Google to control the ecosystem. We need legitimate competition. So what, our choices are Firefox (Gecko), Safari (WebKit), and Ladybird? Personally I go with Firefox on most devices and Orion (WebKit) on my iPhone and iPad. > Heli…

holy soy

Re: Helium Browser

#533

Post by tempaccount420 »

strus wrote: post #375
biotinker wrote: post #82

Earlier quoted context omitted.

You found the authors' screen names and some other things they've made. That's not finding who they are. No one has signed their names, like their real names, to this. Who are they? Intelligence agents? For which country? There's no way to know.

> For which country? At least one of the authors is Russian. They were giving away Helium stickers to “anyone who is in Moscow”, and not many non-Russians are traveling there nowadays.

I think that's wukko (either that or both authors are Russian)

Re: Helium Browser

#534

Post by ha1zum »

alpb wrote: post #139
MountDoom wrote: post #16

What makes me a bit uneasy about the project is that the website doesn't explain who is building it. For most open-source, I think that would be fine. But browsers auto-update, so their vendors essentially have the continued ability to run code on your machine. You want some confidence that they won't get owned and won't sell the access to bad actors down the line, so there is an element of personal trust. All the we…

Agreed, and my concern is not a "NSA is monitoring my activity" but more along the lines of whether they have enough funding to staff security research and response for this browser.

Exactly my concern as well

Re: Helium Browser

#536

Post by mikelpr »

input_sh wrote: post #264
pjmlp wrote: post #236

Earlier quoted context omitted.

They already did, Safari is the only one left standing, by the market share. Plus all the Electron crap that gets shoved as "native".

The only reason Safari has any market share is because it's the default on every iPhone. 4/5 top browsers by market share are there because they are preinstalled on millions of devices and none of them are terrible enough for an average person to look for an alternative.

not merely default but enforced.

Re: Helium Browser

#537

Post by presbyterian »

degosuke wrote: post #290
NetOpWibby wrote: post #156

Yeesh, tough crowd in these comments. And yet everyone's excited for new Gmail skins. Anyway. I hope more people take ungoogled-chromium and create new interfaces. It's a shame that Servo's in an unusable state, I'd love to see more tooling around that. I just want someone to give me Opera 12...I suppose that's Vivaldi though.

And Vivaldi also supports MV2 extensions - so uBlock origin still works without any issues.

Vivaldi doesn't intend to maintain MV2, from their website:

> We will keep Manifest v2 for as long as it’s still available in Chromium. We expect to drop support in June 2025, but we may maintain it longer or be forced to drop support for it sooner, depending on the precise nature of the changes to the code.

https://vivaldi.com/blog/manifest-v3-update-vivaldi-is-futur...

Re: Helium Browser

#538

Post by timschumi »

yoz-y wrote: post #184

I was excited for a new Helium browser release and it just turns out that people these days don’t even do a single google search before using a name that is already taken. https://slashlos.github.io/Helium/

Couldn't try to (together with Theo / t3) bully the Homebrew developers into a forced takeover of a package [1] if it were a conflict-free name.

[1] https://github.com/Homebrew/homebrew-cask/pull/229061

Re: Helium Browser

#539

Post by Jcampuzano2 »

davedx wrote: post #412

Unlike others, I like that it's Chromium because it means I get the devtools. Whenever I try to use other browsers I always get held back by how they work in other browsers, and I do a lot of front-end dev. I'm posting this comment from Helium and so far, so good! I would honestly say ignore the naysayers, everything is a trade off, including which browser engine you put under the hood.

Same, I wanted to like Zen browser for instance but I just could not keep using it because I cannot stand Firefox devtools. I'm too used to chromes.

If I could have a version of zen that looked exactly like it but had their devtools it'd probably be my main driver.

Re: Helium Browser

#540

Post by AlkalineDreams »

timschumi wrote: post #538
yoz-y wrote: post #184

I was excited for a new Helium browser release and it just turns out that people these days don’t even do a single google search before using a name that is already taken. https://slashlos.github.io/Helium/

Couldn't try to (together with Theo / t3) bully the Homebrew developers into a forced takeover of a package [1] if it were a conflict-free name. [1] https://github.com/Homebrew/homebrew-cask/pull/229061

The cask has not been majorly updated in almost 10 years years and is used to connect to a mobile app that hasn't been on the Play Store for almost 5 years, while easily underneath the minimum threshold of downloads for being removed. What's wrong with asking to expedite the removal process, considering the process is detailed in the guidelines?
Post reply on HN