It’s the Cypherpunk’s Manifesto all over again.
It’s the Cypherpunk’s Manifesto all over again.
TCP over IP as a protocol is an “open standard”. Network implementations are nearly always strictly proprietary.
The “protocols” behind browsers are public. HTML, CSS, and ECMAScript are all well defined on sites like the Mozilla documentation. You are free to implement your own browser that follows these standards.
Never point your DNS at two different IP addresses like this. It will only cause you pain and unexpected behaviour.
What you are experiencing is solved by so-called “NAT reflection” or “NAT loopback”. It’s a setting that - in the optimal case - you should just be able to activate on the appropriate interface on your gateway.
If you do not have that setting or do not have access to the edge router, but only some intermediate router, you can do a nasty hack. You can point static routes to your public IP address to point at your local IP address instead. In that case, you also need to tell your server to accept packets with your public IP address as the destination.
The graph makes no sense. Did a generative AI make it.
Buy EU products!
Your cat must be in on the conspiracy. Perhaps even part of the deep state.
Only if California joins the EU, too.
What happens according to article 5 if a NATO member attacks another NATO member?
Yes, but Macron tried to explain to him that taking these funds is illegal.
Not sure if I got the update yet, but I’m banning my printer from accessing the internet right now.
You can still build it yourself.
Wieso passiert das auf einmal so gut wie monatlich.
Doesn’t Bitwarden already have that feature? https://bitwarden.com/passwordless-passkeys/
I explained why. Misconfiguration and caching.