Google is definitely rigged in certain ways, but this looks like a bug, which you'd realize if you knew how modern web apps work. The way modern web applications work is that frontend updates are made optimistically in real time (for speed) and simultaneously hit an API in the background and rely on that as the source of the current application state which takes maybe 0.25 to a few seconds on average.
What it looks like is the user submitted a comment and the frontend added it to the comment list. In the background, it hits the API to submit the comment and the frontend returned a new list of comments for that view. That's where the error occurred: they probably mixed up the comment IDs somewhere in the code. When the new application state was returned, the view layer rendered that out. That's what you're seeing, they're not rewriting your comments in a quarter of a second.
People made posts here a few months back about "twitter unchecked all of my favorites right in front of my eyes" and it was the same issue.
Trust me, if Google wanted to alter comments, they could do so in a way that wouldn't be detectable to you.
That's where the error occurred: they probably mixed up the comment IDs somewhere in the code
Ok so you draft a comment and click submit, and instead of taking the text of your comment (which your local machine already has) and displaying it in the new location (posted comments instead of the box you draft in), they... post the comment, poll the API to get the ID of your comment, then poll the API to get the text of that comment, then display that where your comment should be?
How does that even remotely mesh with you saying
frontend updates are made optimistically in real time
Wouldn't an "optimistic real time update" just be taking the text you entered, formatting it to look like all the other posted comments and then displaying it on top of the other posted comments?
How in the world does "frontend updates are made optimistically in real time" mean your local machine pulls a "comment ID" from the API, then gets the text of that comment?
Learn more about the things you babble about before you babble about them, lowberg.
Every app is different, especially ones that operate at a larger scale like YouTube.
But in a typical modern app, say you make a comment like "I like puppies". The frontend would make that show up in the comment list basically instantly (as fast as the DOM could be altered, probably faster than .1 seconds) so it looks like it's working super fast. At this point, it is NOT yet saved to Google's database.
It's done this way assuming the request succeeds (probably around 99.9999% of the time it does) so that it has the appearance of the App being lightning quick. This is done for good user experience because making a network request is slower than instantaneous and companies don't want people waiting around for actions to submit. Even half second delays here and there waiting for HTTP request responses add up and annoy people.
In the background at the same time, the JS would make a network request to Google telling them you said "I like puppies" and the API would respond, maybe a quarter second or maybe several seconds later. Because most requests succeed, this setup works great for good user experience most of the time.
Different APIs return different types of data when data is submitted. But typically the backend is the ultimate source of truth. In many APIs, when you make a POST to add new content, they return the new current state of the data for the view layer to re-render.
Many companies use a view layer like React to take the current app state and render it. That's likely close to what you're seeing half second after the submit. The API responded with some data about the current application state and the view layer is rendering what it believes to be the current state of the data. We don't have enough info to know whether the bug was on the backend or frontend, but my guess is that they messed up a comment ID somewhere, possibly with an off by one error.
Most Apps work something like this and around 99.9999% of the time, nothing goes wrong with a network request so you don't notice any issues.
There are some things in life I know little about and am open to learning more: but I guarantee you I know what I'm talking about in this domain, so fuck off niggerfaggot.
Yeah, I'm pretty sure that's not what's going on. I don't admit to know what is going on, but I'm certain that youtube isn't accidentally grabbing the wrong ID for his comment multiple times. Especially looking at the weird generic text and relation to what he was trying to type. It's also a bit suspect that we're seeing this on a big firearms channel... But as with all of this that's just speculation. I, for one, have seen enough from google to not trust their platform in any way/shape/form.
view the rest of the comments →
cdglow ago
Google is definitely rigged in certain ways, but this looks like a bug, which you'd realize if you knew how modern web apps work. The way modern web applications work is that frontend updates are made optimistically in real time (for speed) and simultaneously hit an API in the background and rely on that as the source of the current application state which takes maybe 0.25 to a few seconds on average.
What it looks like is the user submitted a comment and the frontend added it to the comment list. In the background, it hits the API to submit the comment and the frontend returned a new list of comments for that view. That's where the error occurred: they probably mixed up the comment IDs somewhere in the code. When the new application state was returned, the view layer rendered that out. That's what you're seeing, they're not rewriting your comments in a quarter of a second.
People made posts here a few months back about "twitter unchecked all of my favorites right in front of my eyes" and it was the same issue.
Trust me, if Google wanted to alter comments, they could do so in a way that wouldn't be detectable to you.
6cd6beb ago
This is stupid.
Ok so you draft a comment and click submit, and instead of taking the text of your comment (which your local machine already has) and displaying it in the new location (posted comments instead of the box you draft in), they... post the comment, poll the API to get the ID of your comment, then poll the API to get the text of that comment, then display that where your comment should be?
How does that even remotely mesh with you saying
Wouldn't an "optimistic real time update" just be taking the text you entered, formatting it to look like all the other posted comments and then displaying it on top of the other posted comments?
How in the world does "frontend updates are made optimistically in real time" mean your local machine pulls a "comment ID" from the API, then gets the text of that comment?
Learn more about the things you babble about before you babble about them, lowberg.
cdglow ago
Every app is different, especially ones that operate at a larger scale like YouTube.
But in a typical modern app, say you make a comment like "I like puppies". The frontend would make that show up in the comment list basically instantly (as fast as the DOM could be altered, probably faster than .1 seconds) so it looks like it's working super fast. At this point, it is NOT yet saved to Google's database.
It's done this way assuming the request succeeds (probably around 99.9999% of the time it does) so that it has the appearance of the App being lightning quick. This is done for good user experience because making a network request is slower than instantaneous and companies don't want people waiting around for actions to submit. Even half second delays here and there waiting for HTTP request responses add up and annoy people.
In the background at the same time, the JS would make a network request to Google telling them you said "I like puppies" and the API would respond, maybe a quarter second or maybe several seconds later. Because most requests succeed, this setup works great for good user experience most of the time.
Different APIs return different types of data when data is submitted. But typically the backend is the ultimate source of truth. In many APIs, when you make a POST to add new content, they return the new current state of the data for the view layer to re-render.
Many companies use a view layer like React to take the current app state and render it. That's likely close to what you're seeing half second after the submit. The API responded with some data about the current application state and the view layer is rendering what it believes to be the current state of the data. We don't have enough info to know whether the bug was on the backend or frontend, but my guess is that they messed up a comment ID somewhere, possibly with an off by one error.
Most Apps work something like this and around 99.9999% of the time, nothing goes wrong with a network request so you don't notice any issues.
There are some things in life I know little about and am open to learning more: but I guarantee you I know what I'm talking about in this domain, so fuck off niggerfaggot.
rootbeervloat ago
Yeah, I'm pretty sure that's not what's going on. I don't admit to know what is going on, but I'm certain that youtube isn't accidentally grabbing the wrong ID for his comment multiple times. Especially looking at the weird generic text and relation to what he was trying to type. It's also a bit suspect that we're seeing this on a big firearms channel... But as with all of this that's just speculation. I, for one, have seen enough from google to not trust their platform in any way/shape/form.