I used to work at a company who used to do this, but I'd argue that it almost never does what you want re: concealing the input space. There are so many ways to recover the input space from the latents, and often they are constructed expressly to contain exactly enough information to do precisely that.
But how much effort would that require? ... is what I was going to say but in this age of "claude reverse engineer this doohickey" maybe the better question is how much compute and how many tokens it would require.
Out of curiosity, does anyone know of anything similar that will plug into an HDMI port directly à la Roku? Would be cool to stream my Jellyfin collection on something like this
You could look into Intel Compute Sticks[0]. They're small Bay Trail (quad core Atom) PCs with a male HDMI and a USB port. They will run Linux well enough but it's a bit of a pain to get it installed since they've only for a single USB port. They used to be really cheap so they may still be. IIRC they've got full VP9 and h.264 High Profile hardware acceleration.
I think your best option then is CoreELEC running Kodi. Look for a deal on Fire Cube 2nd gen on eBay, root it and install CE. Not as compact as a Firestick and a bit more expensive.
My trouble with Pangram is that the calibration is totally off. It can tell you if there is a drop or an ocean of AI in the text you submit. The "X% of AI" message doesn't really mean much. You can test this yourself: Slowly add generated text to a human write paragraph and you'll see it hit "100% AI" quite quickly.
That's the state of the tech right now. It'll be nice if we can get it and keep it more granular than that, but even at the current state it's pretty impressive.
I think my issue is more about how the tool communicates it's result than with the tool itself. The people I speak with don't understand that this is a binary "YES/NO" for many of the passages they are testing.
I don't really know why you would expect a "X% chance of containing AI" number to rise slowly or smoothly alongside the percentage of text that has a 100% chance of containing AI.
My understanding is that the main focus is on the engine and building a good embedding API so that folks can build browsers (and apps and web drivers etc...) with it.
That is my understanding too. In contrast Ladybird has really improved in the UI area and the recent addition of session restore, content blocking and performance makes it a very capable daily driver browser
great idea. Currently working on updating benches on frontiers models, so far on glm-5.3 it's already showed great results. Can I have a link to oh-my-pi to make sure will sure use right one for it?
Also, quick question: Could I use octomind upstream of harnesses like omp and get the savings? Or do you primarily get the savings from using the octomind CLI?
did they stick with the image-based compaction (when vision is supported i guess)? It boggled my mind: "snapcompact, which archives older history into dense images for a vision-capable model"
For obvious reasons it underperforms on models that hide their reasoning chain. Other than that it works fine for a non-customizable method. But properly customized handoff is still better.
I believe that with the budgets but it's crazy we don't see more risks from a creative perspective. In order for the VC model to work, you need to take risks for asymmetric payoffs. In the end, I guess management would rather follow the internal herd and play it safe.
Compare it more to movie production and book publishing. Where we also see a pattern of the big budget stuff being risk averse and the really creative stuff happening downmarket. Often so far downmarket that the creators themselves end up being the primary financiers.
reply