Now to the reason why I am commenting here: there is no GPL violation for the patches used in their /e/ browser but I find it a bit disappointing that nowhere it is mentioned that the browser is a complete Bromite build, minus the logo and renamed to '/e/ Browser'.
Most users are assuming that it is a Chromium fork developed by /e/ and will never reach the Bromite open source project, which is basically the way the project is kept alive.
The AUTHORS file also mentions being a fork of Bromite, but doesn't list any authors that aren't part of the project: https://gitlab.e.foundation/e/apps/browser/blob/master/AUTHO...
It looks like your patches have been changed to renamed Bromite to Browser in user-facing code though. Have you already asked them to add a reference to Bromite somewhere in the about screen? Maybe create a pull request to make it easier for them to accept your request if the devs themselves are lazy. They obviously won't rename the browser shortcut, but adding a reference in the "About browser" section shouldn't be too much to ask for.
Unrelated: I understand your position on cloud providers, but I think /e/ is different from MS or Google in that it's possible to swap out most of the integrations with your own servers (it's all a bunch of glued-together open source services, after all).
Without cloud integration, I doubt /e/ would reach any sort of mainstream of non-technical cult status at all. You'd be left with an app store on top of a build of LineageOS. It's the services delivered with the system that a) distinguish the project from LineageOS without GApps and b) provide basic usability many normal users would miss otherwise.
I keep correct attribution of all patches as much as possible and I would feel more accomplished if also the work of other patches' authors (countless hours) is correctly referenced through Bromite.
> Have you already asked them to add a reference to Bromite somewhere in the about screen?
I have not; I was expecting it, given the amount of modifications from Bromite patches (which is zero, as far as I understood).
> I think /e/ is different from MS or Google in that it's possible to swap out most of the integrations with your own servers (it's all a bunch of glued-together open source services, after all).
It's that "most" that corrupts the intent.
> Without cloud integration, I doubt /e/ would reach any sort of mainstream or non-technical cult status at all.
Sorry, I will avoid discussing this, it has all the clues to become an endless and inconclusive talk :)
In short: yes, I agree with you, and still do not care about "mainstream or non-technical cult status" at all.
I won't lie, I would have expected the same if I were in your shoes. Thinking positively though, it's possible that the /e/ people don't care much about the attribution they themselves receive and don't realize what it means to others to be recognized for their personal hard work. Asking nicely might show them that other people in the open source community do care. The worst that can happen is that the people behind the project do indeed not care about you and are rude about it, but in that case nothing really changes anyway. Things can only improve from here, I'd say!
Based on the changes I've seen, they basically replaced all instances of "Bromite" and "Chrome" in the source code with "Browser". I don't see much /e/-specific code in there at all, aside from a project description and some links in the documentation. They did add a reference to the original project to the AUTHORS file, so I'd like to believe in a variation of Hanlon's razor: Never attribute to malice that which is adequately explained by laziness.
> Sorry, I will avoid discussing this, it has all the clues to become an endless and inconclusive talk :)
I completely agree :)
This would be all fine and agreeable if they had not contacted me first, see my first comment :) of course I can still do contact them pointing out the situation, but let me say that given the nice project manifesto (https://e.foundation/wp-content/uploads/e-manifesto.pdf ) and the large amount of open source projects being involved...there must be expectations of this type :)
I do not claim malice - but I feel like the exact bare minimum was done there, which is not that surprising given that I declined creating/maintaining the customised fork that then they created.
Error getting fdroid index file - > No mirrors available.
Note -- HN included the ) and ; in your link, so clicking it doesn't work properly.
I appreciate your cause and it'd help if it was easier to check it out
"ecchi" is Japanese for the English letter "H", standing for "hentai", which means perverted or strange.
So basically AOSP for less technical people interested in privacy. Seems harmless so far.
Edit: getting downvoted so for clarity this is the part of your comment I'm referring to: MicroG already distributes a fork of LineageOS that includes MicroG
It is very difficult to install Lineage OS, as it is completely unclear which phone one should buy to install it. There isn't a single viable answer online for the question:
"Which phone should I buy for Lineage OS".
I am dead serious!
The support is up to individuals able to produce ROMs, so for example a Galaxy A5 is supported, while A6 and A7 used to be, but are no longer (!) supported. So if you bought an A7 for Lineage OS, you are out of luck now.
Of course it is also difficult to install Lineage OS itself. For most of us, it is probably at least possible. But there is no chance rest of the 95% of the world will ever do this. Indeed, I would also feel at least anxious to attempt it (alas, for my current phone no Lineage OS is available).
So this is great. You can buy a Samsung phone and get it preinstalled with a good distro. I am not aware this is possible otherwise, let alone for less than 300 euro.
Everyone who doesn't understand why this is better than "just install Lineage OS with microG" has some serious disconnect going on.
I am fairly incompetent with computers, but I don't think I could fork my own Lineage OS for my phone of choice. Therefore, having something preinstalled and actually supported is a serious selling point for me!
Edit: Additionally, they will offer a service for you to send in your phone to flash it.
I really like this!
Check out https://wiki.lineageos.org/devices/
It doesn't answer the question which of these phones is a viable one to get now to have Lineage support. Clearly, its not better to get a newer one, it is best to get the one with most support. Which one that is, I do not know.
Still, individual research still required e.g. to find out that the fancy 48 MP camera mode is not supported in LineageOS.
I had not heard of Qwant before this. How does it compare to other privacy-focused search engines e.g. Duck Duck Go?
They were based on Bing, but it changed years ago now and have their own crawlers.
This is not to say that Qwant is horrible because of not having this (I just ran a couple of test queries and the results seem decent), just it would be nice if different "indie" search engines allowed navigation with keyboard.
You can get "very mouseless" with vim vixen add-on
On an unrelated note, hackernews has been blocked for at least a month or two. Probably due to lots of HK protest submissions in recent months.
Or maybe because they are subject, as an European company, to GDPR?
And isn't Google technically a EU company since they use the double irish with a dutch sandwich tax scheme?
Don't let perfect be an enemy of good.
EDIT: Maybe they just googled it and assumed the name was free after finding nothing....
If you buy one of the S7/S9 preloaded models, the camera quality is likely to be quite poor, especially under low light. This is the state of affairs under microG (/lineage), as Samsung ROMs use a proprietary camera library that doesn't carry over. Source: My main phone is an herolte (S7), as the Exynos variants are one of the few phones with separate baseband and application processors.
This should be prominently mentioned on the product page, as it's just going to cause disappointment, regret, and ultimately backlash. Really they should choose an additional model with good camera support to refurbish, and offer the choice as an explicit tradeoff (better quality photos vs better baseband security).
(And if I am completely wrong here because they've somehow fixed or sidestepped this, please correct me. It just doesn't seem likely)
Thanks Google, that's exactly what I was looking for.
I thought only Google did that, name things and projects for common dictionary words. You'd expect a search company to know better.
None at all.