Copying my comment from the Vercel post that gained no traction here:
> From what I can gather, Express 5's body-parser has Brotli decoding enabled by default which would make any endpoint with this middleware vulnerable to this. Am I mistaken?
From what I can gather, Express 5's body-parser has Brotli decoding enabled by default which would make any endpoint with this middleware vulnerable to this. Am I mistaken?
> Is Coding → Prompting like Assembly → High Level Coding? […] I do not agree with this simile. Compilers are, for the most part, deterministic in a way that current AI tools are not.
I have a very different view of this, coming from C++. "Undefined behaviour". Compiler optimizations that only kick in if you align your chakras just right. Memory alignment and cache locality being completely vibe-based, relying on hopes and prayers that the CPU actually does what your mental model thinks it will.
In many ways it's EXACTLY like C++ -> Assembly. You never know what you ended up with until you run the benchmarks, just like you never know what your AI generated until you look at it!
"What do you mean? This worked in the debug build! Why does it crash in release?!"
But with a compiler you can see why the compiler did what it did, with AI you have a black box. Even if you fixed the AI model to be deterministic you could still not see why it produced the specific output for that specific input.
As the lowly programmer, rather than a compiler engineer or a CPU architect, I will never dig into the reasons why my tools decided to do something crazy. I'm much more likely to just try random things until it works. How is that different to how people use LLMs? Even here the opposite is true, the LLM enables me to ACTUALLY dig into the lower levels and work around those issues! It will happily dig into the Chrome source to find exactly why my page rendered weirdly, or why an optimization didn't kick in!
I mean, that's kinda on you, though, right? If you're just going to poke at your code until it works, that's your choice, I guess, but I wouldn't call it good programming.
The point is that it's reasonable and possible to predict the compiler's assembly output from high-level source. Maybe each individual can't do it, but they could, with a little learning.
With LLMs, you just can't predict the output for a given prompt, and can't predict how changing that prompt will change the output (or how much it will change the output). Even the people who build and work on LLMs every single day and know them intimately can't.
Why would that someone want to listen something you haven't created? What have you "shared"? Claude could have made the tools that let the creator build their cities from their own imagination, but that's not what this is.
Do you have a blog post about this? The link is to the home page and doesn't mention anything! Sounds super interesting but the landing page reads like survivalcraft in space #1001
Hey, thanks for asking! If you scroll to the bottom on the homepage, there's a bit of info, and we also have some information on the Steam page of the game.
We plan to do a series of blog posts with technical information about the game and its internals, but right now, we're busy preparing for an Early Access release.
Is that really true? I feel even with Fable and the likes, once the LLM has locked down an implementation any reworks I try to do gets it really tunnelvisioned on the current implementation, treating it like the truth even though it JUST wrote it, and any attempts to make it reframe the problem just makes it dig down further. In these cases I always get way better results throwing the whole thing away and rewinding the conversation rather than trying to evolve it.
No, usually humans write more than just a short unsubstantiated punchline in their "it's not x, it's y's", unless they're trying to sell you something.
They have some nasty "dynamic tap zones" algorithm that dynamically resizes the hitbox for keys based on what it predicts you will type in order to reduce miss-taps. Anecdotally, it has just steadily been getting worse with every update. I swear I can be pressing the center of a key and it will select the next one over and immediately autocorrect to a completely different word than what I typed.
I had the pleasure of typing something on an Android the other day and it was such a breath of fresh air when it actually accepted the keys I was pressing...
In addition to this, there is a delay in the suggested word such that when you see the options above the keyboard, decide you see the word you want, stop typing and move to select it, it changes right as you land your finger.
That drives me crazy. What's crazier happens when the suggested word is the one you are going to type. You hit the next letter in the word, recognize that it has already been suggested, yet right after you hit the letter, it decides to suggest another word.
Compliments of product managers, engineers, etc making millions and millions of dollars to produce a much worse end user experience, if it wasn’t painful enough
Oh wonderful. That’s what’s happening to me. I’m an author and Apple‘s dictionary appears to be missing about half the more uncommon words in the English language. It’ll never recognize “prescient” in dictation for example. Some words it marks in red because it thinks it’s a spelling error. I know it’s not because I’ve used it, read it, and it’s in online dictionaries.
At least I’m macOS I can use Talon instead of the system dictation.
Thank you for putting a name to this phenomenon. I hadn't gone through my yearly attempt to figure out why iOS was terrible for text entry. I figured since I only have an iPad and not an iPhone, and infrequently type in it, that it just hadn't learned my habits or words. It's incredible that they've developed these kinds of algorithms that have made every facet of text entry from speech to text to spell checking to typing itself such a miserable experience.
Try turning off slide to type. It's under Settings > General > Keyboard.
I did it earlier this year. It seems to be much more accurate and confident with which key it thinks I want. I do occasionally miss the sliding but it's worth it overall.
Yeah, I’m not a dedicated iPhone user and my personal phones are androids so my iOS experience has been iPod Touch 2G -> employer owned iPhone 8 -> employer owned iPhone XR -> iPad Air M3. Each of those big gaps have seen the UI shift and the keyboard decline.
Interesting. Because I have a much harder time typing on my Pixel. In fact, I hate it. I wish I had a blackberry.
When I use iOS devices, it feels better but I don't use them enough to have used them in anger. Ok, well, yes they have made me angry but for other reasons than the keyboard hence why I'm on Android lol.
I used a Clicks keyboard with a folded Moto Razr for a while and it was Blackberry-esque. The keyboard is a little narrow compared to the Blackberries of yore, though. I'm somewhat hopeful about the Clicks Communicator which is wider, but sadly still only a four row keyboard.
To be clear, I only kind of recommend the keyboard. I stopped using mine after a while because of how awkward it was with the Razr unfolded and never actually found it faster or more accurate than the on screen keyboard.
someone posted high speed videos a few months ago where the keyboard will popup the key you thought you pressed (therefore did press, as far as the UI is concerned) but iOS will insert a different character anyway.
Some of those videos are misleading. They sometimes slide a finger off one key onto another: taps need to not move.
Personally, I use the slyde to type rather than tapping to type and have gboard installed for when slyde doesn't work (I think the Apple algos are not quite as good as Google's).
Yep; this has been the case since the very first iPhone, it can't be disabled, and there is no feedback it happens other than the typos. It is very crazy making and mind boggling.
I wrongly assumed I was below version 10.10.7 and tried to "upgrade" to it first as the migration guide said, but this completely blew up and the db migrations failed. I then tried to skip straight to 12 and that also crashed on startup during db migrations, so I just nuked the whole Jellyfin config and started from scratch.
Bit unfortunate how this can even happen, but it's on me for not checking or taking a backup first. The config/db really contain anything important anyways, other than "watched" markers that are already out of sync for me across Emby/Jellyfin/Plex.
> From what I can gather, Express 5's body-parser has Brotli decoding enabled by default which would make any endpoint with this middleware vulnerable to this. Am I mistaken?