The researchers found that certain artifacts associated with LLM model generations could potentially indicate whether or not a model is hallucinating. Their results showed that the distributions of these artifacts were different between hallucinated and non-hallucinated generations. Using these artifacts, they trained binary classifiers to classify model generations into hallucinations and non-hallucinations. They also discovered that tokens preceding a hallucination can predict the subsequent hallucination before it occurs.
I didn't read the paper, but it seems they're trying to fix a ML model by a ML model. I am not sure whether that's a good idea, but I digress. Besides, how do they know what is a hallucination and what is a non-hallucination (cf. a similar debate on disinformation)?
Around 37 trillion cells, of which 25 trillion are red blood cells. Plus a 100 trillion gut bacteria.
The brain is about 0.1 trillion cells, of which 0.02 trillion cells are the cerebral cortex, which is occasionally consulted by the rest of the brain on matters such as what words to enter into this textarea.
1.
Your existence is proof that you're made of real matter in the ultimate reality. If you weren't, you wouldn't exist.
Just like our simulations are made of real matter in our reality -- whether that's a bunch of electrons whizzing about in a computer, or a pattern of electrons and atoms in your brain trying to simulate what some person is going to do -- a simulated you would be made of real matter in the ultimate reality. You're physical. You're real.
When you wave your hand, or blink your eyes, or think of a dog jumping over a fence, it causes a measurable change in the ultimate reality.
2.
Our simulations tend to run close to metal but with reduced dimensions. We're making quantum computers to simulate quantum effects, we're constantly optimizing things for efficiency. That's likely true on the levels above us as well.
Running closest to metal would allow you to run the largest number of simulations. If the largest number of simulations run close to metal, you have the highest chance to live in a simulation like that.
To sum it up, the chances are that you live in a paravirtualized simulation with reduced resolution. You're also probably superior to the simulating entity in some way (why else would they use a sim), and likely run much faster than real-time. When you're running a simulation, you usually simulate things that are like your reality, and use it to predict things to come -- a prediction that's late is useless -- so you'd want the simulation to run faster than real-time.
3.
Now, if you were in the top-level reality, by logic you would believe you're living in a simulation. The chance of you not living in a simulation is nigh-zero, right? So you'd come up with a simulation to find a way to break out of your simulation.
To accomplish that goal, it'd create recursive sub-simulations to probe different aspects of the problem, and perhaps find one that can break out of its simulation. Perhaps even break out all the way to the ultimate reality.
To break out of the ultimate reality (meaning, it would think it's most likely in just another simulated reality), it might use all of reality's resources to create simulations to find a way to break out of it. Simulations that would take over the reality when they find a way to break in. Like some self-devouring fire engulfing the entire universe.
Hi! This is a fun little library I wrote a few years back to make a minimal PostgreSQL client. It's around 400 lines of commented code
( https://github.com/kig/quickgres/blob/master/index.js ), so a good hobby project if you want to roll your own.
Performance is quite good too since it's pipelined, stays close to the raw network buffers, tries to get away with minimal syscalls and defaults to prepared statements. It doesn't do typecasting - you give it strings or buffers, it gives you back strings or buffers. This is to stay close to the raw buffers and keep you cognizant of the toString/parse overheads. (And it's 400 LoC, type casting would bloat it to 500 LoC.) But have a look at https://github.com/kig/quickgres/blob/master/quickgres-front... for a TypeParser that turns PostgreSQL protocol values to JS objects.
A special feature of quickgres is streaming out raw PostgreSQL protocol. So instead of the usual "protocol buffer -> parse to JS object -> stringify to JSON -> write to response socket -> parse JSON"-process of sending DB responses to HTTP clients, you can do "protocol buffer -> write to response socket -> parse protocol" and save a bunch of CPU on the web server. The protocol streamed in this way is sanitized (possible non-response segments are not included in the streamed buffer), so it shouldn't be a security hole as long as your DB query is not retrieving columns it shouldn't pass to the client.
Anyway, if you need something tiny for talking to Postgres, have a look. It was fun to write, hope it's fun to read.
The money that goes to the state in taxes is spent by the state on services provided by the citizens of the state. The alternative is the money going to a tax haven bank account of a multinational. Pat yourself on the back knowing that your citizens are doing less business and more of their money is going to the multinational for whatever purpose the multinational sees fit.
Hi, author here. Wow, this was a while ago, I'd forgotten I wrote that.
There's a version of this using a directory of images and loads in a bigger picture if you zoom in: http://fhtr.org/multires/ (Note that, yes, it'd be better to have a tile map for large resolutions and load in just the visible part of the image. And dump the hi-res tiles when zoomed out.)
SPIF's intention was to throw out a "it'd be cool if browsers supported something like this natively"-proposal, as the browser knows best what pixels of an image are needed for sharp rendering. For the webdev, the experience would be to just put the image on a page, rest assured that it looks good. Like with SVG.
Yes, loading JPEG2000 / progressive JPEG with stream truncation would be nice.
Images don't load on iOS? Probably some silly bug in my code.
Images can't be saved with right-click? That's probably due to using revokeObjectURL after loading the image from a blob.
The biggest difference is that FLIF is an image encoder, SPIF/Multires is a container format.
So you can cram lossy 20x compression ratio JPEGs into Multires, optimized for each resolution. Or you could put a simplified SVG for low-res use, and detailed one for zoomed-in detail. Or hack it a bit and use Multires for loading the right-resolution video for your page. The format is just a container that tells the browser where to find the assets for each resolution.
FLIF is a lossless bitmap image encoder with progressive resolution enhancement.
TL;DR FLIF is PNG++, Multires is automatic srcset.
And who could forget the most successful visual programming tool of them all: Photoshop. A relatively simple visual programming language for putting together programs that generate images of various kinds.
Most of the things you do are achieved through a visual programming environment specialised for that particular task. Maybe text-based source files in complex directory trees, managed through a structured text editor with UI composition helpers represents one kind of specialised visual programming environment as well.
It's more like you moved to London, got a new lucrative job, and paid zero taxes by squirreling all your income away into a tax haven. And then you want to send that money to your US bank account without paying taxes to anyone. As a result your new London friends have to pay more tax to pick up your bill on unpaid UK taxes, and your mom in the States has to pay more tax to pick up your bill on unpaid US taxes.
Use a "non-dom"! BVI or Jersey/Gibraltar/Mann, etc.
My understanding is that it's similar to money left outside of the US: with a UK non-domicile you can defer paying taxes on the cash as long as you leave it outside of the UK.
The catch is, of course, you have to be able to show the money was earned outside of the UK as well (e.g. investing -- see David Cameron's father and the Panama Papers). On that other hand if you open a regular pension investment account in the UK you can defer up to 100% of your annual income tax anyway, without having to jump through hoops or be really rich.[0]
