You do realize with more donations they can AFFORD to hire more people, and to get the help they need? Money is the solution. Let’s not downplay the value of it.

Try Windscribe, they offer residential and datacenter IP’s. I don’t get the point, but it’s your money.

I erroneously said the IP’s are less shared, but that’s not the case per the page.

But still, they get past more ip-blocking.

https://windscribe.com/staticips

After reading where I’m even posting: Renting a cheap VPS and using Wireguard to tunnel to it is also an option.

Then it really is only used by you.

• Man, I’m really not reading today.

See: Anything that can open ports. NAT of any kind tends to not allow opening ports.

You can get Let’s Encrypt certificates for DuckDNS, so you don’t even need to own anything.

Works with anything that can open ports. DuckDNS works by pinging their service from anywhere to update the target IP for the subdomain.

You do realize all this is easily done with a reverse proxy + DuckDNS?

Imo this is why big projects that are borderline like this should use github alternatives, preferably self hosted solutions. This was always going to happen.

What we need isn’t browsers. What we need is an universal way to write extensions cross-browser.

Browsers themselves are easy to make. The problem is convincing extension devs to work with yet another codebase.

E: Think of it this way. There’s a lot of open source browsers out there.

Are you using any of them? Probably not.

Would you use one if it doesn’t have for example Bitwarden, Ublock Origin, Sponsorblock, and such mandatory extensions?

Users follow extensions and ease of use; not what’s good for them.

E2: A good project would be a builder extension for VSC for example, which compiles to all supported browsers.

Browser devs would then contribute to said extension via native-made plugins.

Cooperation of two fronts.

Bookmarking this.