![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.blahaj.zone/pictrs/image/fwrQkf9edg.png)
It really seems like we are looking at two sides of the same coin.
The coin has already ben tossed. Let’s see on which side it will land - I certainly hope it is the one you described.
I hear you. During the reddit exodus i left without having an alternative and stumbled upon lemmy much later. So i am fine going back to not having social media. However, a social network only survives if there is enough content. And if we are honest, lemmy barely has enough content.
Ill give you an example: I like climbing and there is [email protected] with roughly 2 posts a month and [email protected] with less. I am happy to see something about my hobby twice a month. But all my friends still are on reddit, because two posts a month are not enough to them.
If you click on my profile, you will find 4 posts. I am a natural lurker, like most people on the internet, i read, vote and maybe comment. These posts, i made them because i wanted to add some content to this platform. While facebook is federated, there will be much more content. We can see theirs, they can see ours. Sounds like a win-win, right? But it may also make lemmings dependent on facebook content. If there is always more than enough content to endlessly scroll, I don’t need to upload my stuff to the network. However, if facebook pulls the plug after a long time, that leaves barely any content here and lemmy is basically dead.
I would probably still be around: Angrily clicking on some link about random big corpo, once a month smiling because someone shared a picture doing the same hobby as i. But for sure there are still people on old XMPP instances, while motivated dev’s reinvented XMPP: Matrix
from https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html :
In 2013, Google realised that most XMPP interactions were between Google Talk users anyway. They didn’t care about respecting a protocol they were not 100% in control. So they pulled the plug and announced they would not be federated anymore.
Basically keep people from using all the other platforms. Then stop supporting them. Similar like .docx never quite works in the open document editors. At least i refuse to believe that OSS devs are less skilled and motivated.
For yelling too loud.
Statement of an observing police officer:
They say ToxicWaste murdered that Salesman… with his voice! Shouted him apart!
Keep in mind that this graph shows core temperature. It is obvious to most but it should be written down.
Don’t want someone with little to no cooking experience look at this chart and put his huge turkey for a couple of seconds in the oven at 165°F / 74°C 😅
The code is not obfuscated. The person i linked to even formatted it nicely. I do not have the time or energy to go through all of youtube’s JS. But the 5s everyone is talking about does target every browser the same. Serverside the code isn’t altered based on browser detection.
I know that you are memeing - but some ppl probably don’t have the background to see the difference.
A ping does not contain a http header containing a user agent. The response to a ping is not a webpage - and even if it was, your console won’t execute the JS.
I said that i found different articles blindly copying. But i did not say 404 did so ;)
The code is still present when spoofing the user agent or even using a freshly installed chrome. The demo video loafing faster after spoofing can be due to many different reasons.
If you want a better break down of what the code could be used for, this guy foes a good job: https://old.reddit.com/r/firefox/comments/17ywbjj/whenever_i_open_a_youtube_video_in_a_new_tab_its/ka08uqj/
Most of the articles writing about it seem to reference following reddit post: https://old.reddit.com/r/firefox/comments/17ywbjj/whenever_i_open_a_youtube_video_in_a_new_tab_its/k9w3ei4/
Following code is pointed out:
setTimeout(function() {
c();
a.resolve(1)
}, 5E3);
While this is a 5s timeout, the code itself does not check for the user agent. So wherever the code is the 5s timeout will occur. The code also does not seem to be injected server side. I spoofed my user agent and for good measure installed a fresh google chrome, both times the code was present. So this code cannot be used to make any browser slower without making the other browsers slow too.
There is a response to the reddit post, which most articles seem to take their intel from. IMO this response does a good job at exploring what the code could be used for and points out that it is more than likely not for slowing down Firefox users: https://old.reddit.com/r/firefox/comments/17ywbjj/whenever_i_open_a_youtube_video_in_a_new_tab_its/ka08uqj/
I am amused by thinking that many journalists seem to take this story from a post on reddit, without even reading the direct responses - or just copy from another article.
This is not correct.
Most of the posts/articles reference following reddit post: https://old.reddit.com/r/firefox/comments/17ywbjj/whenever_i_open_a_youtube_video_in_a_new_tab_its/k9w3ei4/ . It shows the code from your screenshot. However the code does not check the user agent and is not injected server side (I checked by user agent spoofing and using a freshly installed chrome). So it will run on every browser and cannot be used against some specific ones.
There is an answer to the post everyone seems to reference, which goes a bit deeper into what the code could do: https://old.reddit.com/r/firefox/comments/17ywbjj/whenever_i_open_a_youtube_video_in_a_new_tab_its/ka08uqj/
Yes, there is a 5s timeout in youtube’s code. However, it is not aimed at Firefox users.
The same code shows up on a fresh chrome installation without any extensions. And the code does not check for the user agent. So the 5s timeout is not there to make Firefox a bad choice for youtube. Following response to your link goes a bit deeper into what the code could mean: https://old.reddit.com/r/firefox/comments/17ywbjj/whenever_i_open_a_youtube_video_in_a_new_tab_its/ka08uqj/
Guys relax. Most of the ‘research’ comes from this reddit post: https://old.reddit.com/r/firefox/comments/17ywbjj/whenever_i_open_a_youtube_video_in_a_new_tab_its/k9w3ei4/
It points out following code in youtube’s polymer script:
setTimeout(function() {
c();
a.resolve(1)
}, 5E3);
But exactly this code does show up on a stock installation of chrome too, and it does not check for the user agent. One of the responses goes a bit deeper into what the code above could do: https://old.reddit.com/r/firefox/comments/17ywbjj/whenever_i_open_a_youtube_video_in_a_new_tab_its/ka08uqj/
It is rather clear, that this code is not aimed at firefox users to slow down their loading time.