Bump.

Support!
This will make new users not get confused when their pfp is still the same even after changing it

Nice idea! There is literally no point why not

POST https://scratch.mit.edu/discuss/topic/466864/bump
Cache-Control: no-cache

I support, that confuses me when I change my profile pic

Support. For me, even that doesn’t work, I have to clear my search history. This being implemented would make life so much easier.

Actually, recently there's been an overflow of questions about “my pfp isn't showing” in QaS. Maybe this could solve that annoyance.

gosoccerboy5 wrote:

Actually, recently there's been an overflow of questions about “my pfp isn't showing” in QaS. Maybe this could solve that annoyance.

yea, the amount of times i see that.

NanoPIex wrote:

Support. IT`S SO ANNOYING!!!!

I mean, you can just hold shift and refresh the page, I think…

But either way, total support.

gosoccerboy5 wrote:

Actually, recently there's been an overflow of questions about “my pfp isn't showing” in QaS. Maybe this could solve that annoyance.

There are even more posts about this in Bugs and Glitches.

Maximouse wrote:

gosoccerboy5 wrote:

Actually, recently there's been an overflow of questions about “my pfp isn't showing” in QaS. Maybe this could solve that annoyance.

There are even more posts about this in Bugs and Glitches.

i think i saw over 7 of those topics ON ONE DAY

Support! It is really annoying when I have to do ctrl+shift+r instead of just reloading the page. This would stop the people in Bugs and glitches from posting about 5-8 topics a day just on this one topic.

Support

i wonder if the old image host did this by default, or maybe that one had a really low cache time.

anyways, for obvious reasons, i support

Jeffalo wrote:

i wonder if the old image host did this by default, or maybe that one had a really low cache time.

It probably had a low cache time – doing this probably requires client side code so it doesn't depend on the image host.

POST https://scratch.mit.edu/discuss/topic/466864/bump
Cache-Control: no-cache

Support. Not doing so causes all sorts of issues.

I just discovered they're now affected by the server side cache too, so they should also be removed from that one.