New Update A new Chrome clone: Helium

0.12.3
Changelog

d14e214a revision: bump to 3 (#1682)
48eb96f4 helium/zen: fix zen vts not displaying on windows (#1681)
549f912f merge: update to chromium 148.0.7778.167 (#1679)
b304a82a patches: refresh for chromium 148.0.7778.167
4f53b3ce merge: update ungoogled-chromium to 148.0.7778.167
dca3530b Update to Chromium 148.0.7778.167
d195bfc9 Update to Chromium 148.0.7778.96

 
Hi

Just installed and spinning it.

One question.

Blocking of CSP reports and hyperlink auditing are no issue

How to write a rule to add to uBO to block API Beacon? In uBO lite for my Ungoogled Chromium I was shown last time to add under DEVELOP

Any one can help?

Thanks
 
Last edited:
Hi

Just installed and spinning it.

One question.

Blocking of CSP reports and hyperlink auditing are no issue

How to write a rule to add to uBO to block API Beacon? In uBO lite for my Ungoogled Chromium I was shown last time to add under DEVELOP

Any one can help?

Thanks

Answering my own question :rolleyes:

After some searching through Github discussions it seem it's not possible to write a rule to blanket block API Beacon

So only way now is for me to add the extension, Ping Blocker, which blocks API Beacon, CSP reports and hyperlink auditing and disabling the last two from uBO
 
0.12.4
Changelog

b4155a78 revision: bump to 4 (#1752)
75bb363f merge: update to chromium 148.0.7778.178 (#1751)
9b257a50 flags.gn: remove drumbrake enablement
64322bef patches: refresh for chromium 148.0.7778.178
56a15e4d merge: update ungoogled-chromium to 148.0.7778.178
7c07c452 Update to Chromium 148.0.7778.178
5e207628 Fallback string enum for older python
c44f96e1 helium/kb-shortcuts: don't modify close tab/window actions (#1736)
65369b1a Added OpenBSD package (#3783)
d99402c6 Check hide tab close buttons on vertical tabs (#3782)
0ca51e8b Add patch for disabling JIT (#3775)

 
Found one issue. The installed uBO is v1.70.0 but the latest is v1.71.0. Cannot update. Already enabled Developer mode

1779593410707.png


When I dropped the new uBO crx file it creates another one with the new version. The default one cannot be removed

1779593683136.png



Anyway to update the default uBO otherwise I'll need to disable the default and use the new one?
 
0.12.5.1

Changelog

a14223c4 revision: bump to 5 (#1814)<br>4112ae96 merge: update to chromium 148.0.7778.215 (#1811)<br>f67a06c4 merge: update chromium to 148.0.7778.215<br>70f4b07e helium/ui/toast: anchor to web content, update visual style (#1806)<br>672b6b28 helium/zen: rephrase toast pref toggle in a11y settings (#1810)<br>f0509326 i18n: add new strings (#1672)<br>b879674d upstream-fixes: fix black flash on tab when leaving split view (#1809)<br>d1ecca12 helium/settings/clear-data: remove google link, always expand (#1792)<br>e2ab1b45 helium/zen: don't reveal top chrome for toasts (#1790)<br>3f49fa53 helium/zen: don't show new tab toast when tabs are visible (#1789)<br>a7b5ed5b helium/ui/pdf-viewer: apply sidenav width only if open (#1774)

Download

 
It does need an auto update & the ability to delete history on exit or a private mode to become fully acceptable at least for myself all other issues I can live with, both these can be done manually but, other than that its about perfect.

Helium has an Incognito (Private) mode and for clearing history I use Chrome History Cleaner and set history cleaning to every minute

 
I've used history remove extensions, I'm not sure which I trust though, one of my personal concerns is how much of our data is lost through extensions, IMO is a rather large elephant in the room as we trust people without knowing much about them??
 
What is the point of privacy/security in clearing the history when the browser starts up using an extension that likely has access to that same history?:unsure:

Mah !!

Wouldn't it be better to clear the history when exiting the browser, and,for those who know how,to prevent the history from being saved via a policy?
 
I've used history remove extensions, I'm not sure which I trust though, one of my personal concerns is how much of our data is lost through extensions, IMO is a rather large elephant in the room as we trust people without knowing much about them??

Look at what the extension developer says at Chrome Web Store. Frankly, if the extension has been reported as rouge Google would have removed it and, if haven't, would sooner remove it

No choice unless one uses a browser which don't support extensions
 
Last edited:
I've used history remove extensions, I'm not sure which I trust though, one of my personal concerns is how much of our data is lost through extensions, IMO is a rather large elephant in the room as we trust people without knowing much about them??
I was using "History Cleaner" because it was recommended by Mozilla add-ons, and it is open-source software and does not collect any data:
 
@lokamoka820 Does it delete on exit ?? That's really all I need/

IMO i don't think its really about an extension even being rouge, we spend a lot of time on this site as regards privacy, then potentially give all our browsing history to an unknown person who does who knows what with it, & then relying on Google or Mozilla to make sure its OK which again IMHO is a huge potential mistake which is why I am very careful with extensions, & have two running on both browsers :)
 
Last edited:
0.13.1.1 released

e13ddd4 update: helium 0.13.1.1 (#285)
77ee94b helium/windows: winsparkle updater (#286)
e501e98 helium/windows: refresh updater patches for m149
008faee helium/win: move versioning patches to separate file
e114701 helium/updater: implement system install update notifications
c9e3cda helium/winsparkle: verboser errors
b8f787c helium/windows: more version migrations
cd376ed ci: sign update helper with different description
5d2383a build: wire up winsparkle envs
3ff28ff helium/updater: init
ca58f6f helium/change-branding: use helium version in more internal places
75b2625 .gitignore: add resources/generated
abe78f2 downloads: add winsparkle dep
4ed4429 build: build mini_installer again
fabf8e9 update: helium 0.13.1.1

helium-chromium​

5bf45fed merge: update to chromium 149.0.7827.53 (#1857)
3bbe6a3c revision: reset to 1
e3525bb6 helium/zen: reorder patch hunks
d48bc496 deps: update ublock to 1.71.0 (#1875)
d4e58802 helium/ui: redesign infobar, optimize and rename zen (#1868)
c20175cf helium/ui/infobar: redesign, draw proper borders, fix webview relations
e8a1bfc1 helium/zen: rename Zen to Frameless in UI, remove feature gates
bf560c6a helium/layout: optimize zen top reveal, move out of experiment dir
34ef5f26 patches/brave/chrome-importer: remove os_crypt-related dead code
99cef46c helium/ui: clean up patches, fix accidental string OS gates
5b7dd06c devutils/i18n: add clean command (#1869)
7a32267e helium/updater: add win scaffolding, tighten arch conditions (#1866)
d856d800 ci: complete cirrus port to github actions (#1867)
c362740d patches: update for chromium 149.0.7827.53
b8a66095 merge: update ungoogled-chromium to 149.0.7827.53
a3a5471d Update to Chromium 149.0.7827.53
c6a41202 helium/updates: decouple update url from helium services + reformat (#1827)
94344c47 Update to Chromium 148.0.7778.215
95f6fe1c Port CirrusCI jobs to github actions (#3776)



One thing to note is that uBO is updated to v1.71.0 ie. with a new version of Helium

and is this the auto updater we're expecting or just a notification? Have to wait for next build/version to test it out

e114701 helium/updater: implement system install update notifications
 
Last edited: