131 karma · joined January 10, 2020
That is exactly what the DMCA is and Google does abide by that. This case is about Google's compliance with the law, not whether the law is fair.
> "Her Honour has found that Google is a publisher of the defamatory imputations once Google receives notice of a defamatory publication online as a result of the use of its search engine," he said.
I think it is reasonable to argue that Google should remove results if they are notified of defamation. I hope that was the ruling in this case, because anything else would set a terrifying precedent.
I'm not a kernel dev, but WireGuard v2 will probably be implemented as a separate kernel module so they can coexist. It makes sense to do it that way since they're practically entirely separate protocols.
Maybe I don't understand the issue to be solved (I was unfamiliar with the 'road warrior' term so I looked it up [1]), but I think both Avery Pennarun and Michael Tremer misunderstood what WireGuard is capable of. WireGuard works just fine when the physical network interfaces have dynamic IPs (on both ends even). You can use the basic wg or wg-quick tools to create a VPN server on a server with a dynamic IP and have clients connect from dynamic IPs. However, all the tunnel IPs must be static unlike e.g. OpenVPN where the server gives the client a tunnel IP during authentication.
> (for example, so you can get to an office network whose home connection uses dynamic DNS). It’s true that plain WireGuard does not support this configuration out of the box.
I have done literally that for over a year now. I cannot think of a way to interpret this that would make Avery's claims true.
> Someday, WireGuard will need to be upgraded to support a second cipher suite. When this happens, users will be able to configure it peer-by-peer to allow one cipher suite or the other, or both, exactly as they would with any other VPN.
That is not how I interpret what Donenfeld has said [2] about the future of WireGuard. I believe the software will get a v2 without backwards compatibility. However, even that is a non-issue because sysadmins can run both protocols in parallel during the transition.
[1] https://en.wikipedia.org/wiki/Road_warrior_%28computing%29
[2] Page 3 of https://www.wireguard.com/papers/wireguard.pdf
Isn't this a bit poorly timed, considering the recent Cloudflare DNS announcement?
> In the coming months, we will provide the ability to define additional configuration settings for 1.1.1.1 for Families. This will include options to create specific whitelists and blacklists of certain sites. You will be able to set the times of the day when categories, such as social media, are blocked and get reports on your household's Internet usage.
https://blog.cloudflare.com/introducing-1-1-1-1-for-families...
I searched around a little and neither this nor the recent Facebook story have been covered by Danish non-tech media at this time.
EDIT: The story is still new, it might get coverage later this week.
Only compared to the current, unencrypted version. For E2E encryption, the alternative, as I see it, is pushing out an encrypted video stream per recipient. He has reduced his egress from O(n) to O(1).
The 2019 Zoom vulnerability[1] was a much bigger deal and did get picked up by the media. Zoom already had a terrible reputation before COVID-19.
For example, my default Kubuntu 19.10 installation flips the primary and secondary if the primary is unresponsive for a while. Since my laptop takes a moment to establish a WiFi connection upon waking up, it always decides that the primary server is down and to default to the secondary server. It has currently been 3½ hours since my laptop queried its primary server and it has queried the secondary server over 1000 times in the past 24 hours despite the primary having 100% uptime.
Most stub resolvers have an option to use strict order, but you can't rely on it as a network admin.
I don't think it does, dnsmasq is optional. It does configure dnsmasq regardless, but that configuration only applies if you install and enable dnsmasq. As far as I can see, the script does none of that nor does it change /etc/resolv.conf. The readme is very clear about needing dnsmasq for wildcard blocking.
The script also modifies the host file which will apply regardless.
I VPN to my home (and by extension my Pi-hole server) when on that kind of network. A local ad-blocker doesn't prevent MITM or malicious DNS servers. Maza won't help if DHCP is handing out the IP for a server that claims google.com is a CNAME to hereisyourvirus.xyz or if the router is transparently redirecting DNS traffic so you don't even know what DNS server you are hitting. Which means you have to use DoH or DoT as well.
I don't know how to test it properly, but I tried looping over both the initialisation and a single search, and the hash sets were much slower, so much so that hash sets trailed lists by microseconds at size 10000. In retrospect, making those data structures unsurprisingly dominated running time and the test kind of lost all meaning. It was clear, however, that it wouldn't take many searches for the hash sets to win, search times for lists were going through the roof.
I ran your Python test on my machine and the hash set was faster in every case: 10x faster at size 50, 2x faster at size 5, 1.3x faster at size 3.
That's barely true for H.264 and it is a much worse format in every other way. Effective quality is higher with modern video formats because the lower data rates afford higher resolutions and higher frame rates. Even the LICEcap demos show that.
It's a neat tool, the user interface is really cool, but it would be better in a different format.
Yes, but the issue is with your monitor brightness or your ambient lighting, not the content. I tune my monitor for use at night with the lights on and as a result, #000 on #FFF is perfectly comfortable at all times. There's rarely a good reason to use a PC in complete darkness and I can't think of any reasons to do it in your own home.