This is great!
My first thought reading the title was this was going to be about HTTP error code 507 because something is moving data around mechanically ;)
6,591 karma · joined April 30, 2015
My first thought reading the title was this was going to be about HTTP error code 507 because something is moving data around mechanically ;)
The Butlerian Jihad has started.
String sql = "INSERT INTO users (name, email, age, status, country) " +
"VALUES (?, ?, ?, ?, ? )";
I ask because `Where(u => ComplicatedBooleanFunction(u))` can't in general be transformed into something you can do in SQL, especially if it's stateful, but maybe there's a trick if the function is simple enough?
Some ORMs get around this problem with methods like .WhereEqual(User::id, 123) so you don't need to parse anything to know the semantics.
PS. I have in the past got praised at work for massively speeding up database access, when I fixed something like `List<User> userList = UserDAO.fetchAll(); return userList.length();`. You need a minimal understanding of databases to use an ORM correctly. The DAO even had a `.count()` method, but you need to know a little about databases to know to look for that in the first place.
Some ORMs let you specify the extent of the data that you want, like Hibernate has its own Hibernate Query Language.
At some point you are better off just writing SQL yourself, though. Even without join problems, if you ask an ORM to get the person with user id 123 and all you want is their name, the ORM cannot know that unless to tell it, and so you end up with a 'SELECT *' type query.
*with the help of AI*. Does in fact make a difference.
Whether it applies to non-AI generated images is a question for the reverse engineers (or ironically, a suitable AI). My bet is on "no".
Of course, the pre-AI versions of paint and notepad can still be installed with a bit of trickery, and it's worth it just for the UX.
The AI with watermark picks its bits from a CSPRNG, then does the same transform to get the distribution. The result I think is that you can reduce distinguishing the distribution to breaking the CSPRNG.
In this example the entropy after the transform is around 0.13 bits, so the watermarking scheme cannot add any useful information. Once you have hundreds or prehaps thousands of bits of entropy, it starts to become feasible to add information into that 'spare' space.
For an analogy, distinguishing AES ciphertext from random bits without the key would be counted as breaking AES (the more precise statement of this is called AEAD).
This is what you'd expect to see if the poster were a bot linked to the same PR network.
Both levels can be deactivated on Android (no idea about iOS but I presume it's the same), there's no unblockable presidential alert level.
> Hugo Chavez realized that there’s no technical limit on how often you can invoke the emergency broadcast system. You can do it every day! The “emergency” can be that you had a cool new thought about the true meaning of socialism. Or that you’re opening a new hospital and it makes a good photo op. Or that opposition media is saying something mean about you, and you’d like to prevent anyone from watching that particular channel (which is conveniently bound by law to air emergency broadcasts whenever they occur).
> To illustrate, in the special case that GPT had a bunch of possible tokens that it judged equally probable, you could simply choose whichever token maximized g [a cryptographic function]. The choice would look uniformly random to someone who didn’t know the key, but someone who did know the key could later sum g over all n-grams and see that it was anomalously large. The general case, where the token probabilities can all be different, is a little more technical, but the basic idea is similar.