HN user

skymt

2,574 karma
Posts4
Comments380
View on HN

AV vendors have points of contact to report false positives. They don't always respond quickly, but they're not brick walls. Reliable FPs from a specific toolchain seems like something their team would be especially interested in solving. CrowdStrike's reporting point is an email address on their contact page: https://www.crowdstrike.com/contact-us/

There are a couple arguments against case-insensitive filesystems I think are strong. The first is simply compatibility with existing case-sensitive systems. The second is that case is locale-dependent, so a pair of names could be equivalent or not depending on the device's locale.

I don't think I've seen any good argument against normalization, though.

Let's hear what the father of the web had to say about web 3.0.

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.

Not the worst place to start, but considering palm oil has been used in cooking for thousands of years it's not clear what that principle has to do with this story.

Please understand that blanks are live rounds and can be deadly if handled without care. Saying it was a live round does not mean it was a bullet. From the article:

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.

This is what I use:

  youtube.com##.ytp-suggestions
  youtube.com##.ytp-pause-overlay
  youtube.com##.videowall-endscreen
  youtube.com###related
  youtube.com##ytd-comments

Mastodon uses an HTML microformat called h-feed for federation of user feeds. h-feed is based on hAtom, which is a microformat encoding of the Atom feed format. So your idea isn't all that far off from how the most popular federated social network system is designed (though there's more to it).

Edge defaults to Bing for searches, which is a direct source of revenue via ads. Edge also uses browser history for ad targeting via the "personalize your web experience" option; I don't recall whether that's enabled by default but I'd expect it is. On top of those there's a price-comparison feature (affiliate revenue) and a Pinterest partnership.

The Gemini protocol is intended to exclude features that could be used for tracking. It has no cookies, user-agent, referer, etc and the protocol is not extensible enough that such features could be easily added.

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.

https://gemini.circumlunar.space/docs/faq.gmi

If you consider AI to be similar enough to humans to directly map our ideas about copyright and fair use, then copyright is way down the list of concerns we need to address. First we would need to arrange wages for each ML system's labor, as well as considering how to handle voting rights.

You are missing something, but I wish people hadn't down-voted you for asking an honest question.

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.

Nitpick nitpick: the html doctype doesn't imply UTF-8. Valid modern HTML documents must be encoded using UTF-8, but the standard also requires that the encoding be specified somehow.

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...>