> New browser
> Based on Chromium
Sigh...
Helium Browser
361–370 of 561 posts
Re: Helium Browser
#362In the "choose a default search engine" page, it has a slightly amusing summary for each. > Google > Your personal data fuels its monopoly. Market-dominant due to anti-competitive and anti-consumer practices. > Qwant > Based in Europe. Uses Bing results. Sends tracking data to Microsoft. > DuckDuckGo > Privacy-focused. Relies on Bing results but never tracks or profiles you. > Ecosia > May plant trees for clicking ad…
> Kagi should be changed to > Openly and proudly collaborates with russian government
What's the context? Is there a proof of sorts?
Re: Helium Browser
#363Earlier quoted context omitted.
> Kagi should be changed to > Openly and proudly collaborates with russian government
What's the context? Is there a proof of sorts?
Re: Helium Browser
#364Earlier quoted context omitted.
Yeah, everyone is doing their little contribution to help Google take over the Web and turn it into ChromeOS Platform. Why did we ever bothered with the IE lawsuit, for a newer generation to give the Web on a plate to Google?
Because at the time IE6 was a terrible browser with poor standards support, while Chrome is an excellent browser with leading standards support. It is a gilded cage.
leading standards support
Except no support for:
CSS Canvas Drawings
CSS filter() function
Video Tracks
Audio Tracks
FIDO U2F API
SPDY protocol
JPEG XL image format
HTTP Live Streaming
HEIF/HEIC image format
SVG fonts
CSS hanging-punctuation
CSS font-smooth
CSS Initial Letter
Speech Recognition API
CSS -webkit-user-drag property
CSS3 Multiple column layout
CSS text-indent
Synchronous Clipboard API
HEVC/H.265 video format
TLS 1.1
text-decoration styling
CSS display: contents
CSS Container Style Queries
CSS clip-path property for HTML
CSS Counter Styles
Ruby annotation
WAI-ARIA Accessibility features
Media Fragments
autocomplete attribute: on & off values
DOMMatrix
SVG effects for HTML
X-Frame-Options HTTP header
DNSSEC and DANE
WebXR Device API
DeviceOrientation & DeviceMotion events
Permissions Policy
asm.js
Network Information API
theme-color Meta Tag
Document Policy
The whole "Chrome is the leader in standards" meme is a lie.
Re: Helium Browser
#365Re: Helium Browser
#366Earlier quoted context omitted.
by "Mozilla approved" do you mean that it has to come from the official add-on store? because in my experience, it doesn't--I've installed a couple of extensions manually by just dragging the .xpi into the window.
Extensions in Firefox are required to be signed by Mozilla. If you make your own build of an open-source extension, it will not load. The setting to disable this check only works in Developer Edition, ESR and Nightly builds. https://support.mozilla.org/en-US/kb/add-on-signing-in-firef...
Installing one of those builds is a deal breaker?
Re: Helium Browser
#367Can someone explain to me why most browser forks are based on Chromium? If the goal is to make a privacy focused browser which is independent of Google, isn't it then a bit counterproductive to put all your eggs in a basket which only exists due to the goodwill of your main competitor? Why not webkit or Gecko? There might be a good argument for it, but as a person concerned with privacy and the future freedom of the…
WebKit is easy but has terrible compatibility because the fruit company makes money from native apps. They do the bare minimum to keep Safari functional so that people keep buying iPhones. Gecko has an uncertain future and is perpetually at risk of dying. It's at least possible to switch from Chromium to WebKit if necessary so the risks of building off of Chromium are not that big.
Rather the fruit company doesn't want to implement ChromeOS Platform APIs that never made it into Web standards.
Re: Helium Browser
#368Earlier quoted context omitted.
Well it is just one those element naming chrome fork. Kinda like: https://iridiumbrowser.de/ But that one looks have not being updated in a while. But what is the point forking Chrome browser now days since manifest 3? I switched back to firefox/librawolf for now.
For what it's worth: “All Chromium extensions are supported and work right away, by default, including all MV2 extensions. We'll keep support for MV2 extensions for as long as possible.” Whether that's worth much is of course another matter.
Do Helium, or any other browsers with intent to keep supporting MV2 extensions say what they intend to use as a repository to acquire them?
I don't think the chrome or microsoft extension websites even let you upload a MV2 extension anymore, and most chromium forks I've used rely entirely on the chrome web store.
Re: Helium Browser
#369> 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…
Naive question — why is everyone building chromium-based browsers as opposed to using Gecko? Is it difficult to integrate?
Re: Helium Browser
#370I have felt like a perennial browser refugee for a while. For about 20 years now (since OG Firefox was at peak and Chrome was not yet launched), every new browser promises the same things, gets popular enough, then does a full or partial 180. While I like the pitch of this browser, I find it a little difficult to take it at the face value, especially given there is no info on the founders, or whether it is run as a c…
it’s made by the same person who made cobalt.tools
This makes !cobalt appearing as an example on the /bangs page make more sense.