See what JavaScript commands get injected through an in-app browser
1–10 of 330 posts
Re: See what JavaScript commands get injected through an in-app browser
#2Was anyone expecting otherwise?
They'll use it to make their algorithm better, and they'll use it to better target ads.
Both of those things are good for me the user, so I'm fine with it.
And for those who don't like that, use a blocker, or don't use TikTok.
Re: See what JavaScript commands get injected through an in-app browser
#3Is it similar to what Meta in Instagram does? [0] - a week ago thread.
Re: See what JavaScript commands get injected through an in-app browser
#4Was anyone expecting otherwise? They'll use it to make their algorithm better, and they'll use it to better target ads. Both of those things are good for me the user, so I'm fine with it. And for those who don't like that, use a blocker, or don't use TikTok.
I like TikTok, I think that algorithm is toxic and that "better" currently means "more toxic". My simple ask is that I wish we could control it a little better. It sends you down a tree, but I wish we could zoom out, visualize the tree and just pick a different branch to go down.
Re: See what JavaScript commands get injected through an in-app browser
#5This is wonderful work you are doing. It has been a joy to follow.
Re: See what JavaScript commands get injected through an in-app browser
#6Was anyone expecting otherwise? They'll use it to make their algorithm better, and they'll use it to better target ads. Both of those things are good for me the user, so I'm fine with it. And for those who don't like that, use a blocker, or don't use TikTok.
I like TikTok, I think that algorithm is toxic and that "better" currently means "more toxic". My simple ask is that I wish we could control it a little better. It sends you down a tree, but I wish we could zoom out, visualize the tree and just pick a different branch to go down.
The product/feature you're describing will never be implemented in their spyware.
What incentive do they have to satisfy this feature request?
Re: See what JavaScript commands get injected through an in-app browser
#7Was anyone expecting otherwise? They'll use it to make their algorithm better, and they'll use it to better target ads. Both of those things are good for me the user, so I'm fine with it. And for those who don't like that, use a blocker, or don't use TikTok.
I like TikTok, I think that algorithm is toxic and that "better" currently means "more toxic". My simple ask is that I wish we could control it a little better. It sends you down a tree, but I wish we could zoom out, visualize the tree and just pick a different branch to go down.
They’re not going to do that because they don’t want you going down a different branch that will lead to lower engagement metrics for them.
Re: See what JavaScript commands get injected through an in-app browser
#8Is it similar to what Meta in Instagram does? [0] - a week ago thread. [0]: https://news.ycombinator.com/item?id=32415470
Yes and that’s literally the first link in the first sentence in the first paragraph of the article lol
Re: See what JavaScript commands get injected through an in-app browser
#9I just don't understand how we can allow a Chinese social media app in the west, while any non-chinese social media apps aren't allowed there?
Same with housing, why can Chinese nationals buy housing here, while I can't do so there?
Re: See what JavaScript commands get injected through an in-app browser
#10Earlier quoted context omitted.
I like TikTok, I think that algorithm is toxic and that "better" currently means "more toxic". My simple ask is that I wish we could control it a little better. It sends you down a tree, but I wish we could zoom out, visualize the tree and just pick a different branch to go down.
The product/feature you're describing will never be implemented in their spyware. What incentive do they have to satisfy this feature request?
Imagine there was a competitor which did have this feature.
And users appreciated it, and used it to discover more content that they were more interested in.
Preventing that happening would be a good reason to implement it. Don't wait for someone else to implement something users like...