dtho

Censorship can be used to monopolize the spread of misinformation.

If you do not "have it" and you are unable to reproduce the imagery you see in your mind's eye using a pencil on paper, then that is clarifying. Whatever you consider to be visualization is not even close to the same as actually seeing something. If whatever you experience was a "vivid visualization", then you would be able to reproduce it drawing.

I personally don't experience anything that I would consider "visualization", and I am also terrible at drawing, but I can reproduce a photorealistic drawing of a photograph if I am allowed to look at the photograph while drawing.

You would be able to reproduce the object very accurately, given enough time. You can simply continuously refine the drawing by comparing the drawing to the object.

The ultimate test is having them draw a picture. If they can visualize imagery then they should be an excellent artist. If they are bad at drawing, then they must have aphantasia.

Each token affects the probabilities of subsequent tokens. Let's say you want the model to produce Python code, and you are using a grammar to force JSON output. The model wasn't trained on JSON-serialized Python code. It was trained on normal Python code with real newlines. Wouldn't forcing JSON impair output quality in this case?

The defining characteristic of science is that one can independently arrive at a logical conclusion by observing cause and effect. There is no belief or indoctrination necessary. Having faith in science is an oxymoron (although it's all too common).

The constructor of std::string is constexpr in C++20. A runtime call to 'strlen' (or equivalent) can be optimized out by computing the string's length at compile time and initializing the object accordingly.

In the absence of IDE features, you can't differentiate between value arguments and reference arguments unless you view the callee's prototype. Pointers do not have this problem.

Another biblical example is Psalm 90:10: "Our days may come to seventy years, or eighty, if our strength endures; yet the best of them are but trouble and sorrow, for they quickly pass, and we fly away."

Member functions have an invisible argument: the pointer to the C++ object. You can access this argument using the 'this' keyword. John Carmack describes pure functions like so:

> Pure functions have a lot of nice properties. Thread safety. A pure function with value parameters is completely thread safe. With reference or pointer parameters, even if they are const, you do need to be aware of the danger that another thread doing non-pure operations might mutate or free the data, but it is still one of the most powerful tools for writing safe multithreaded code.

Emphasis on 'value parameters'. The invisible 'this' argument is not passed by value, it is passed by reference. By Carmack's definition, C++ member functions are not pure.

The title of the linked article has a question mark, while the HN title does not.

Anyone can create a fake 'seized' page.

Sure, at this point. Yishan resigned from Reddit in 2014.

Seems like he had it under control, and was recording it in order to publicize the problem and possibly get it fixed.

Yes.

Is it fair to assassinate someone's character by suggesting to millions of people that this someone is a criminal when they have not been found guilty in the court of law?

That's the problem he's pointing out. The media doesn't attempt to portray reality objectively or truthfully whatsoever. They have gotten quite good at influencing our opinions without rationalizing those opinions.

How does that make them very different? The latest version of the software is still exploitable in either case. In my opinion, that is why it's useful to call them 0-days until they are patched.

It started out as a 0-day in 2012, and since it has remained unpatched, it continues to be called a 0-day. That is how it is commonly used.

It's not only the speed. All of the timestamps of the files are even numbers, which is indicative of a FAT file system.

> "The directory entry for the FAT file system only has a 5-bit field for storing the number of seconds in the time. This limits the number stored in the field to the range 0-31, which is multiplied by two to obtain the number of seconds."

The timestamps appear to have been copied to a FAT filesystem (common for USB devices) on May 25, 2016.

https://turcopolier.typepad.com/sic_semper_tyrannis/2019/04/...

Why would the legality make this test invalid or unfair? Illegal things still happen. I have seen countless street signs with graffiti on them. I could see rebellious teenagers doing this on purpose without fully understanding or caring about the consequences. Search google images for 'street sign graffiti' and you will see thousands of examples.

Are you criticizing LuaJIT rather than Lua? LuaJIT is a third party implementation of an older version of Lua (with cherry picked features from newer versions). A lot of this criticism is no longer valid for Lua.

> lack of a separate integer type (chars are strings, ints are floats)

Lua 5.3 introduced integer types. [1]

> Even bit manipulation requires going through the FFI.

LuaJIT includes a bit manipulation library, but its FFI acceleration is optional. Also, Lua 5.3 introduced bitwise operators. [1]

> One cannot even format UTF-8 text

Lua 5.3 introduced "basic utf-8 support" [1] although I am not sure to what extent.

> The official documentation mostly revolves around C bindings. The actual Lua language documentation is provided by another web site that looks like it has been written by an attention-deficit child

Again, I suspect you are criticizing LuaJIT. The actual Lua documentation [2] has never let me down.

[1] http://www.lua.org/manual/5.3/readme.html#changes

[2] http://www.lua.org/manual/5.3/manual.html