Hi, unfortunately I can’t leave Instagram completely to stay in touch with my social circle overseas. After reading around the forum, seems like PWA is the way to go. I’m a GOS user and used to have Instagram app installed.
After giving it a try for a few days, one big difference I noticed is how quick my phone gets warm when browsing through Instagram via PWA vs the app.
I’m wondering if this is normal or it’s just Meta’s way of driving people to use their app? Also, how much “wins” do you actually get from using their PWA vs the app?
Vanadium. My phone is P7P and everything is up to date. If this keeps up, I tend to want to return to using the app, but also curious if it’s a lot more harmful than using the PWA
It might be a browser issue due to lack of content blocking, I plan to try replacing Vanadium with Brave for PWAs (I always use Mull, now Ironfox for daily browsing).
Yeah that would be my last resort. Atm, I have all apps under the same profile, closed source or not. I’m trying to keep things as simple as possible, weighing the effort and the benefit.
My thinking is, most of the legworks is already done by having Graphene, so at the very least, I reached my personal threshold of limiting what data I give to big tech companies
Thanks. There are 4 instagram.com, 2 of which are http. These two I can enable JS JIT, but somehow the other two, it kept being turned off after I turn it on? This is on Vanadium, haven’t tried Brave yet.
I just tried to import all my content blocklist from UBO to Brave browser, the time used to open a PWA is more than 10 fold (took a full minute to open a PWA, page load is okay though)
Not sure if it is caused by incompatibility of some blocklists, but if it is simply caused by the size of blocklist, then it is not good.
It is quite strange because opening Brave Browser App itself is fine, but when opening the PWA, it takes ages
