Add Cromite to Mobile Browsers #2381
Conversation
✅ Deploy Preview for privacyguides ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Discussion thread for this https://discuss.privacyguides.net/t/cromite-bromite-fork/13274 |
There was a problem hiding this comment.
Must receive engine updates in 0-1 days from upstream release.
0-1 days is a bit too strict for a one-person project. DivestOS claims it's "within a week," my personal observation is usually 1 day, occasionally up to 3. Maybe we can ask the maintainer for this
we also have to change the criteria at the bottom of this page if we add a recommendation which doesn't match them.
|
or should we ask the dev about their release schedule? since referring to the chromium release blog is not the best idea since not every version is an exact match |
|
This pull request has been mentioned on Privacy Guides. There might be relevant details there: https://discuss.privacyguides.net/t/cromite-bromite-fork/13274/47 |
There was a problem hiding this comment.
Hmm. Seems like it doesn't uses HTML admonitions that should now be used on the website. Of course, there's no rush for this but we will need to convert this page later on to the new admonitions.
Also, speaking of this PR, seems like the "homepage button" for Cromite isn't here! There's cromite.org available but it redirects to the GitHub page. So, what we could do here is : Display the "homepage" button that contains cromite.org or the GH page. Something like this should be added :
[:octicons-home-16: Homepage](https://cromite.org){ .md-button .md-button--primary }
|
Sorry to intrude. but, if it is possible, i would ask you to be patient with your publication, until issue uazo/cromite#710 is resolved. thank you for your consideration. another thing, and please excuse me, I don't think those recommendations are good as default for cromite, but I don't want to sound cheeky and I might be wrong after all. |
thanks for your patience, i'll let you know that i've solved at least for windows and android. linux is a bit more complex and for now it's a todo. |
|
if you want I can tell you what I think the defaults should be, actually I plan to include them when I try to put cromite on the google store, which I will only do after I have written the privacy policy (which are not easy to write because, it is true, unlike other browsers, I do not send myself any data, ever, but the browser collects a lot locally). |
|
the recommendations were copied from the ones used for Bromite which appears to be written some time (2+ years) ago personally i don't really agree with them either but eh |
jonaharagon
force-pushed
the
main
branch
12 times, most recently
from
0740c58
to
d1e1035
Compare
jonaharagon
force-pushed
the
main
branch
9 times, most recently
from
e124ecf
to
82ab189
Compare
jonaharagon
force-pushed
the
main
branch
10 times, most recently
from
0a94f3f
to
d80af39
Compare
|
This pull request has been mentioned on Privacy Guides. There might be relevant details there: https://discuss.privacyguides.net/t/revisiting-sandboxing-firefox-on-android/17840/33 |
I apologise, really! that point has been closed, the issue is only open for the linux version. I'm sorry I didn't tell you @jonaharagon |
|
@uazo I wasn't sure if you wanted to wait until that was resolved for Linux as well, or if you didn't want us to share it until it was on mainstream platforms like Google Play. But if you're happy with it then I'm happy with it 👍 |
Signed-off-by: Austin Huang <im@austinhuang.me>
unfortunately I still don't know how to solve it, that's the problem. the only way is to force the user to recompile ffmpeg, but that's a solution I don't like.
no, really, I forgot, sorry. |
|
i still think the recommended measures should be reviewed (I just copied whatever's written for Bromite before), particularly regarding whether one should always use incognito |
✅ Your preview is ready!
|
Signed-off-by: Austin Huang <im@austinhuang.me>
I agree, is one of the points I would like to address.
do you mean the always incognito? |
|
|
||
| { align=right } | ||
|
|
||
| **Cromite** is a Chromium-based browser with privacy and security enhancements, built-in ad blocking, and some fingerprinting randomization. It is the continuation of Bromite. |
There was a problem hiding this comment.
and some fingerprinting randomization.
some because I never detailed them, correct?
do you think it is right for me to do so, i.e. to detail what has been implemented and what I think is missing?
do you happen to have a list of those implemented in brave as a comparison?
There was a problem hiding this comment.
do you think it is right for me to do so, i.e. to detail what has been implemented and what I think is missing?
I would like that then I would directly link to it.
do you happen to have a list of those implemented in brave as a comparison?
There are various blog articles that I think one would have to go through. This however might be more relevant as it discusses what is randomized and what is blocked.
There was a problem hiding this comment.
Also I think has to do with testing at https://privacytests.org/android - where it seems to cover similar things to Brave but less than Mull. Not that I think Cromite should go as far as Mull does necessarily, to be clear. There are tradeoffs here, and I don't think Cromite intends to go as far as Firefox RFP?
There was a problem hiding this comment.
ah I didn't even know @arthuredelstein added cromite!
where it seems to cover similar things to Brave but less than Mull
let's talk about it if you want. the results of each test should be interpreted.
But I don't think cromite is necessarily better than others: what cromite lacks is testing (and spread :) and I am okay with the fact that there are excellent sites like that and the duck duck test site because I use them to check regressions.
too bad there is no site that compare the same browser on different devices, not so much on functionality, but on how it looks to the Web sites.
creepjs, my reference website, has something similar, but it is hidden very well in the code.
Not that I think Cromite should go as far as Mull does necessarily, to be clear.
Unfortunately, I don't know Mull so I can't answer that.
I don't think Cromite intends to go as far as Firefox RFP?
I don't know that one either.
I can tell you that my goal is to make all devices as similar as possible, as Tor does.
Changes proposed in this PR:
Criteria:
yes
0-1 days is a bit too strict for a one-person project. DivestOS claims it's "within a week," my personal observation is usually 1 day, occasionally up to 3. Maybe we can ask the maintainer for this
doesn't appear to
yes