It was easier to browse remixes and their remixes with it. What was the reason for this?

The remix tree showed remixes made by deleted accounts so people can use it to show inappropriate images with the thumbnail.

Why not simply put something like this?\

if <[user] = [banned]> then 
  dont show thumbnail
else
do show that thumbnail
end

Coolboy0516 wrote:

Why not simply put something like this?\

if <[user] = [banned]> then 
  dont show thumbnail
else
do show that thumbnail
end

Scratch code is built NOT on block script. It would be a lot more complicated than that, along with the fact the remix tree is discontinued

Scratch_Cat_Coder8 wrote:

(#4)

Coolboy0516 wrote:

Why not simply put something like this?\

if <[user] = [banned]> then 
  dont show thumbnail
else
do show that thumbnail
end

Scratch code is built NOT on block script. It would be a lot more complicated than that, along with the fact the remix tree is discontinued

I know, just trying to put it in something others can understand.

Kind of a shame. That was the easiest way to find remixes, but now it's almost impossible to find a particular remix in a project with lots of them. Looking through page after page to find a remix sounds like a nightmare.

TMEA123 wrote:

Kind of a shame. That was the easiest way to find remixes, but now it's almost impossible to find a particular remix in a project with lots of them. Looking through page after page to find a remix sounds like a nightmare.

It would also be impossible if a Scratcher were to unshare their remix.

Just one unshare and good luck trying to find the other remixes. It's basically like cutting the branch off a tree. The rest of the branch's remixes go with it.

NovaShrugs926 wrote:

TMEA123 wrote:

Kind of a shame. That was the easiest way to find remixes, but now it's almost impossible to find a particular remix in a project with lots of them. Looking through page after page to find a remix sounds like a nightmare.

It would also be impossible if a Scratcher were to unshare their remix.

TMEA123 wrote:

Kind of a shame. That was the easiest way to find remixes, but now it's almost impossible to find a particular remix in a project with lots of them. Looking through page after page to find a remix sounds like a nightmare.

Agreed (if anyone is wondering what happened, they made the remixtree redirect to the remixes page)
It might be related to the recent remixes thing that happened, but it still makes me mad lol

medians wrote:

Agreed (if anyone is wondering what happened, they made the remixtree redirect to the remixes page)
It might be related to the recent remixes thing that happened, but it still makes me mad lol

wait what
now i'm mad because the remixtree would be easier for add yourself projects and would update faster than remixes

I just want to add something, NFE detectors completely relied on the remixtree API to function, because a projects review status was sent with the remixtree for some reason. The only other ways to determine if a project is NFE are unreliable or take a long time to update.

I feel that this is the reason remix trees were removed.

MagicCoder330 wrote:

The remix tree showed remixes made by deleted accounts so people can use it to show inappropriate images with the thumbnail.

NoUsername-King wrote:

I just want to add something, NFE detectors completely relied on the remixtree API to function, because a projects review status was sent with the remixtree for some reason. The only other ways to determine if a project is NFE are unreliable or take a long time to update.

These sound like some pretty good/plausible reasons to me.

medians wrote:

Agreed (if anyone is wondering what happened, they made the remixtree redirect to the remixes page)
It might be related to the recent remixes thing that happened, but it still makes me mad lol

Can I ask, what was the “recent remixes thing that happened”?

Za-Chary wrote:

medians wrote:

Agreed (if anyone is wondering what happened, they made the remixtree redirect to the remixes page)
It might be related to the recent remixes thing that happened, but it still makes me mad lol

Can I ask, what was the “recent remixes thing that happened”?

Some bots plagued the platform a while ago and spam remixed a bunch of projects with questionable project titles and thumbnails

Za-Chary wrote:

MagicCoder330 wrote:

The remix tree showed remixes made by deleted accounts so people can use it to show inappropriate images with the thumbnail.

NoUsername-King wrote:

I just want to add something, NFE detectors completely relied on the remixtree API to function, because a projects review status was sent with the remixtree for some reason. The only other ways to determine if a project is NFE are unreliable or take a long time to update.

These sound like some pretty good/plausible reasons to me.

I mean, I feel like both of these could be fixed, but I have no idea if they're gonna bring it back. I feel like it's useful.

Za-Chary wrote:

medians wrote:

Agreed (if anyone is wondering what happened, they made the remixtree redirect to the remixes page)
It might be related to the recent remixes thing that happened, but it still makes me mad lol

Can I ask, what was the “recent remixes thing that happened”?

It could be the same remix bots that impersonated other users too.

this is a real shame because i think the remixtree is the most ‘scratch’ feature possible. it is the visual representation of the scratch philosophy and i really hope they consider reimplementing the remix tree in a ‘scratch 4.0’.

Especially considering that the issues sound easy to fix since it already hid deleted projects, but apparently, Scratch is that lazy.

aw man rip remixtree

dang