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.

Because we like the smell. https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0274143

I’ll just add heavy emphasis to properly configure this, because otherwise anyone can use your domain as a catch-all host.

Which is how scammers hijack domains for sending spam and other content.

You don’t need to wait.

The format is address_at_provider.com_id@duck.com for sending emails.

Never.

How about duckduckgo’s email alias service? It allows you to send and receive without exposing your actual email.

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?

I can’t anymore. Leads to system crashing randomly. 11 works unfortunately.

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.

Could you elaborate a bit?

Isn’t Proxmox etc. “Gpu less”, as they only use tty instead of anything like a WM or DE?

I’d prefer a “master” / hypervisor running a bunch of VM’s for different purposes.

Whether they be for gaming, pirating, development, pen testing, home automation, porn, or anything else really.

'Course I’d only be running gpu passthrough into a single VM at a time, can’t split a single GPU into 50 passthroughs yet.

iGPU shares one monitor with the dGPU, but on different protocol, which from what I read online is supported.

It only really needs output when I flick it open.

So maybe it needs a KVM switch instead of trusting the monitors splits.

How would hooking up everything to the GPU be beneficial when it comes to GPU passthrough?

Albeit is it even necessary these days.

You can disable it explicitly, yes.

It should be possible to use it with the dgpu.

Edit: You can also prioritize using the iGPU over the dGPU in bios. Maybe that’d work, hmm.

Sadly not sarcastic. Ideal is Radeon handling the base, and NVIDIA being used in passthrough.

They just refuse to cooperate.

Scenario 1. X11 “works”, wayland doesn’t. Trying to update NVIDIA drivers leads to boot failure.

Scenario 2. Wayland works. Only on igpu. Only via HDMI. Only on one monitor.

Scenario 3. Wayland works on Displayport. Doesn’t even recognize second monitor.

Scenario 4. Everything seems to work. Trying to do GPU passthrough fails.

Scenario 5. IGPU is hogging displayport, despite being connected via HDMI, thus preventing the DGPU passthrough on either HDMI or DP.

Bookmarking this.