I also like the idea of the PinePhone, but it doesnât seem viable yet for actual usage. In my opinion the best option currently available is /e/OS, which is basically a de-Googled fork of LineageOS, so it runs on any device that LineageOS supports. There are also unofficial builds of /e/OS if you search around for them, just this week I installed one on my tablet and Iâm really liking it. It has serious advantages for privacy-conscious people while at the same time not giving up any functionality, as you can still install proprietary apps from the Play Store via a proxy store app they include, and those apps actually work because they pre-configure their own services that masquerade as Googleâs GMS Core. It even passes Googleâs âSafety Netâ test to allow things like bank apps to be installed. Normally a custom AOSP ROM without Googleâs proprietary framework add-ons (âGappsâ) is close to useless, and while you can install the OSS implementation of them (microG) it requires rooting most ROMs and then enabling signature spoofing; itâs really quite complex and confusing.
TL;DR is that /e/OS seems to me like the most pragmatic way of actually having a usable mobile OS while at the same time being open source and respecting user privacy.
Wow, permanent!
I wasnât expecting that. @sb56637 , I changed my mind.
If you could increase my âthanksâ too, that would be really awesome.
(I ran out of âthanksâ last night for the first time.)
@raccoon Please let me know if it happens again, but I tweaked the general âThanksâ limits a bit last night after you ran into the limitation and I think you should be good now.
That post says a great deal about the extreme measures corporations have taken to acquire and keep control over regular people, and the degree to which it has destroyed the entire concept of open-source, collaboration, and individual empowerment.
The only usable phones these days ship with entire suites of spyware preinstalled for the benefit of various corporations, and itâs extremely difficult to remove because theyâve basically DRMâd the entire software and firmware stack, all the way down to the bootloader and even some of the computing chips. Itâs a concrete realization of the classic âFritz chipâ concept⌠and billions of people are locked into it.
Now Google is trying to do the same thing with the web, adding DRM to ensure that only officially approved unmodified builds of corporate-supported web browsers will be able to access most of the internet. Not because the people need it, but because it further increases the power and profits of large corporations.
I hope I live to see the day when such practices are deemed illegal, enforcement is carried out to stop it, and the entire ecosystem moves back toward collaboration instead of exploitation.
Most of the content is loaded by javascript, or requires javascript to perform searches and stuff⌠so Dillo canât see it. Even if I navigate to a product page using some other search engine, most of the info is missing⌠just empty placeholder elements which havenât been populated because they require the browser to execute extra code locally and make additional API calls to get the actual content. Theyâve turned a simple browsing experience into an âapplicationâ, and in so doing, needlessly destroyed accessibility on their site.
Meanwhile, on old BLF it was possible to read, log in, and post comments in Dillo. And on new BLF itâs possible to read at least, though I havenât tried to log in and Iâm pretty sure it wouldnât be able to post any comments.
Not sure, I didnât try. The comment section on news sites tends to be terrible, full of just ⌠the worst people ⌠so I generally donât even look. Plus, it requires javascript on most sites so I doubt it would work.
Thereâs not much to see, since they donât work.
Usually though, most sites will work but not at 100% functionality. Anything interactive, anything lazy-loaded, anything animated, anything dynamic⌠those parts donât work.
For example, if I click on an actor at IMDB, it shows a lot of their info⌠but after maybe 20 titles theyâve been in, there is a button which says âSee allâ. This button doesnât work, because it requires javascript. IMDB used to work better in Dillo, but at some point they switched to lazy-loading anything past the first page, so that info is no longer accessible.
At Home Depot, I can see a productâs title, price, and short description⌠but there are no pictures, no info about remaining stock, no product details, no reviews, no related products, no cart, etc⌠because all of those things require javascript. On a related note, Home Depotâs site tends to balloon my mainstream browserâs RAM usage, and then crash those tabs if I leave them open for more than a few hours. But in Dillo, like with every other site, it barely uses any RAM and after initially loading, it uses zero CPU.
So, basically, it has some tradeoffs:
On the minus side, all that Web 2.0 stuff doesnât work.
On the plus side, all that Web 2.0 stuff doesnât work.
You should be able to get a rough idea how it looks by using a mainstream browser and an extension (or option) to completely turn off javascript. uBlock has a button for that.
Agreed. Genuinely been thinking for a while that Google and Apple probably need to be broken up.
Googleâs âattestationâ embrace/extend/extinguish even says in the RFC that itâs a privacy risk if a party controls more than one of the parts. Thatâs Google with chromeâŚ
Heh I have an IKEA lamp that just uses a single 7135 with 6 LEDs, in a 2S3P configuration. The whole circuit is on a single aluminium MCPCB and is pretty much as close to the reference design as possible, and I even reflowed some LH181B (Samsung CSP2323) onto it for better CRI and a ~4000K tintmix instead of 2700K.
Edit: forgot to mention itâs also powered by a 7V wall wart to simplify deisgn I guess.