• 0 Posts
  • 11 Comments
Joined 8M ago
cake
Cake day: Mar 12, 2024

help-circle
rss

Salient demonstration, but if image proxying were to come to Lemmy I’d hope it was made optional, as it could overburden smaller instances, especially one-person instances (like mine). We also need a simple integrated way of configuring object storage.



If you’re able and willing to self-host, I’ve developed a pretty great system that automates my entire process. The app I’m using on mobile is also available on iOS

https://zemmy.cc/post/25500


I welcome any alternatives to the current situation, but unfortunately that’s where we are right now.

The only solution would be a massive effort that requires decades of engineering hours and a few million dollars.


Firefox is actually a bit faster and lighter than Chrome these days. Worth checking out it or it’s forks over Chrome



People should be attacking your idea, not their perception of you based on your choice in browser.

My objection with Brave, Vivaldi, and other other browser that is just Chrome with a different skin of paint is they are all signalling an acceptance of Google’s monopoly over the web standards ecosystem.

Mozilla is a shit organization run by a shit CEO, but they’re the only alternative we have to the megalith that is the advertising company known as Google. It really shouldn’t be a hard argument to understand that putting an advertising company at the head of the web standards process is a really bad idea if you care about anything other than Google’s revenue streams, ie a free and open web.

Chromium only exists as a way for Google to keep antitrust regulators from coming after them like they did to Microsoft when IE had a monopoly. It’s source-available, not open source, they don’t accept commits from non-Googlers. The moment they feel safe closing down the Chromium repos without having to lose too much money in fines or blowback, they absolutely will.

We’re literally watching this happen right now with Android, another formally open source project from Google that is slowly having all of its open source components clawed back so that they can maintain their control over the ecosystem and protect the revenue stream that is their data collection and app store.

When Google inevitably decides to pull the plug on Chromium the collective of forked browser developers is not going to be able to keep up with the massive engineering effort required to keep a modern browser going. Especially when a corporation like Google can and will push forward complex and difficult to implement standards expressly for the purpose of making those forks obsolete. They have the manpower, capital, and control over massive web properties to effectively push out anyone they don’t want.

All it takes is them making a change to Youtube that hinders alternative browsers and that will be the death of that open source ecosystem. They’ve literally pulled this exact move before with Youtube by hindering Firefox’s performance by pushing through the implementation of shadow DOM.

All of this has happened before and all of this will happen again. Trusting an advertising company with control of the open web is the nerd equivalent of leopards ate my face


I surely deserve death for using a browser you don’t like.

I’m not sure how you managed to come to that conclusion. You claimed Firefox is a poor choice, I’m demonstrating why I believe your alternative choice is worse. Nevermind the fact that use of Chromium is effectively an acceptance of Google’s monopoly over the web standards, which is the point we’re all arguing here. If you can’t handle criticism you should reconsider making such hyperbolic remarks.


Nothing about this is recent, those who pay attention to the standards process have been screaming for ages about the Google problem. It’s just that now between interest rates being what they are and them having a monopoly on the browser market that they’re cashing in on their investment.


It’s Brave, as evidenced in their history. The browser that peddles crypto ads, has a transphobe CEO, and has been accused of selling copyrighted data


For sites that rely on XHR using Javascript, which let’s be honest is pretty much all of them, this would not work due to CORS and CSP restrictions