2,574 karma · joined June 10, 2010
I don't think I've seen any good argument against normalization, though.
> People keep asking what Web 3.0 is. I think maybe when you've got an overlay of scalable vector graphics – everything rippling and folding and looking misty – on Web 2.0 and access to a semantic Web integrated across a huge space of data, you'll have access to an unbelievable data resource… — Tim Berners-Lee, 2006
That's funny, he didn't mention blockchains once.
> A source close to the union said Local 44 does not know what projectile was in the gun and clarified that “live” is an industry term that refers to a gun loaded with some material such as a blank ready for filming.
https://www.ghacks.net/2010/03/18/blacklist-google-search-re...
MacVenture support has been tinkered with over a couple of GSoC terms. It's not ready but there's interest and a foundation to build on: https://wiki.scummvm.org/index.php?title=MacVenture
youtube.com##.ytp-suggestions
youtube.com##.ytp-pause-overlay
youtube.com##.videowall-endscreen
youtube.com###related
youtube.com##ytd-commentsCurrently yes. When Chrome eventually mandates Manifest V3 extensions, they will no longer be able to run code not contained in the signed extension package.
https://developer.chrome.com/docs/extensions/mv3/intro/mv3-m...
Also, frankly, the spartan design of native Gemini pages (very limited formatting, no scripts or even inline images!) means that the circle of nerds who use Gemini will almost certainly remain too small to catch the eye of ad-tech. It's hostile to commerce in a way I find kind of delightful.
The Haxe website has links to some other popular frameworks like OpenFL and HaxeFlixel: https://haxe.org/use-cases/games/
The problem described in the blog post is that prefetch loads the resource into cache, which when combined with per-site cache segmentation means that it's ambiguous which cache a resource should be loaded into when it's prefetched across sites.
https://chromium.googlesource.com/angle/angle/+/master/READM...
> The Encoding standard requires use of the UTF-8 character encoding and requires use of the "utf-8" encoding label to identify it... If an HTML document does not start with a BOM, and its encoding is not explicitly given by Content-Type metadata, and the document is not an iframe srcdoc document, then the encoding must be specified using a meta element with a charset attribute or a meta element with an http-equiv attribute in the Encoding declaration state.
<https://html.spec.whatwg.org/multipage/semantics.html#charac...>
This is a valid HTML5 document:
<!doctype html>
<title>This is valid!</title>
<p>Really, it's valid!
Paste it into the validator yourself if you don't believe me: <https://validator.w3.org/nu/#textarea>