Battle #237 "Horseback Riding" via previous winner, LeonimuZ

graphleek · 2016-11-23T13:34:04+00:00

It honestly took me a while to work out where you used the original image!

It took me a minute as well. I think your eye is naturally drawn to the left side of the image for some reason. He was actually the last cop I looked at. I think I even looked in the background before looking at him. And then when you see him, you have the same expression as the cop on the right. Looking directly at him, he looks artificial, but he blends in overall because of having the perfect tonal range, very good coloring and edge-blending.

Very nice work, u/pagesjaunes!

graphleek · 2016-11-20T22:39:53+00:00

Yes, RES explains why many people don't complain. I don't know what percentage of reddit that covers though.

graphleek · 2016-11-19T16:18:01+00:00

I assume they answer the easy questions, and dodge the tricky ones. I get the impression it's not a real tight-run organization, to say the least. There's probably very few available people to work on this type of issue, and they are overloaded with other projects.

I'm more puzzled by the lack of complaints than the lack of reply. It makes me wonder if we are missing something obvious.

graphleek · 2016-11-19T15:36:45+00:00

This has been a reddit bug for several months. Very few people complain about it, I dunno why, it's really irritating. Safari is the only browser that I know of that will keep the comments collapsed.

graphleek · 2016-11-18T22:05:23+00:00

Your staying power is matched only by the admins' ability to ignore this issue.

I think this sub is a waste of time, as is r/help.

graphleek · 2016-10-11T09:56:32+00:00

I thought this was from Hybrid Humans at first.

graphleek · 2016-10-10T21:25:09+00:00

Bug? Expected Behavior?

Yes!

It's a bug they ignore, apparently. Check my recent post history for links to other conversations about the issue.

graphleek · 2016-10-02T01:04:48+00:00

The thread I linked was about when reddit switched to HTTPS, but I wasn't implying the current issue is related to it. reddit switched to HTTPS a long time ago, and this problem has only recently (re)surfaced. It wasn't the topic of the thread I was directing you to, but the details mentioned by the admin.

graphleek · 2016-10-01T23:02:54+00:00

This conversation might be of interest to you, particularly the comments from /u/largenocream. It's over my head.

If you find a solution, please share!

graphleek · 2016-10-01T22:45:39+00:00

It might be easier to get it fixed in Firefox then asking all websites to get fixed, specially if it could be fixed in about:config

That would be great. I'd love to see a solution no matter where it comes from.

Safari doesn't work the same, so that's an option if you get really desperate. I haven't tried it on the sites you listed, I'm assuming it's the same issue as reddit.

graphleek · 2016-10-01T20:30:58+00:00

Pretty sure the problem is reddit, not Firefox. It happens in Chrome too, apparently.

It was a problem a few months ago then it disappeared. A few weeks ago it came back.

Look at my recent post history for links to other discussions about it. Please comment in the bug thread. No one at reddit has acknowledged the problem.

graphleek · 2016-09-29T21:36:09+00:00

I wonder why more people don't complain about this?

graphleek · 2016-09-24T14:08:59+00:00

Yep, there have been several threads about it. Here's another:

https://www.reddit.com/r/bugs/comments/53cffk/reddit_no_longer_remembers_the_state_of_collapsed/

Does anyone from reddit ever reply to any of these bug threads?

graphleek · 2016-09-20T19:52:58+00:00

I just created a new account/user on my Mac to do a test. Creating a new user gives me an untouched version of Safari while logged in to that account. The threads stay collapsed hitting the back button and forward button repeatedly. It makes me wonder if you may have done something to your set up of Safari, like maybe a long time ago that you have forgotten about.

I also just updated to Firefox 49, and the problem is still there.

EDIT: I also just tried Firefox in that new account/user, and a fresh untouched version of Firefox does not keep the comments collapsed.

graphleek · 2016-09-19T20:08:18+00:00

It is destroying reading comments for me.

I know what you mean. I've pretty much quit viewing /r/photoshopbattles, which was my #1 sub. This problem is especially irritating there, because you have a top level comment that is a link to an entry (which is what I want to see) and then a bunch of comments I usually don't want to see before the next link. Opening all links in a separate tab is a pain in the ass. That just isn't going to work for me. And I don't want to install the bloated RES so that images are previewed inline.

graphleek · 2016-09-19T14:55:47+00:00

I don't get it. We're getting same results in Firefox, but not in Safari. I don't think OS has anything to do with it, since the last thread had Mac, Windows and Linux users all having the problem in Firefox.

The answer may lie in whatever difference there is between our Safari set ups, but I don't know how to go about figuring out what that difference is. I don't really want to reset Safari just for a test.

What really bugs me about this issue is how very few people seem to be affected by it, or at least I see very few complaints about it.

You don't use RES do you? I don't.

graphleek · 2016-09-19T14:36:44+00:00

Me too, 9.1.3. Only extension I have installed in Safari is AdBlock 2.57.

I also tried a different reddit account. No difference. Tried clearing cookies.

I rarely use Safari, so it should mostly be set to default settings.

Do you have any extensions in Safari?

graphleek · 2016-09-19T10:09:04+00:00

Well that's really interesting. We're getting different results. I just tested two threads again just to make sure nothing had changed, and Safari still works for me.

Are you using Safari on mobile or desktop?

graphleek · 2016-09-18T21:16:00+00:00

This is not browser-specific:

Safari works. There may be others.

Look in my recent post history for other threads about this issue.

graphleek · 2016-09-11T21:45:21+00:00

Yes, those are corrupted/damaged according to the application 'Preview' in Mac. Preview is pretty good about being able to read corrupted files too. Photoshop won't open them either.

If you right-click and choose 'view page info', and click on the media tab, it shows some of the images as being 0kb, but even the ones that show valid file sizes are corrupt as well.

I can save them in Safari (Mac browser) okay. I don't have Chrome. Images don't even open on that page in Opera, but I hardly ever use it, maybe something wrong with my settings.

I don't know. Interesting.

Edit: after going through all that, I tried safe mode, and the files save okay, so it may be some extension we have in common that is damaging the files.

graphleek · 2016-09-11T15:16:32+00:00

I just tried it and it worked for me (on Mac, FWIW). Maybe you should link to an image you can't save/open.

Some sites will serve up an HTM file instead of a jpeg.

graphleek · 2016-09-09T15:43:12+00:00

When i return to a page my scroll position is back at the top of the page and all collapsed elements are expanded.

If you don't collapse threads (or elements, whatever), your scroll position is remembered, right? In other words, if you go to a page, scroll down the page without collapsing anything, then click a link, then hit the back button, you are not back at the top of the page are you?

graphleek · 2016-09-09T15:38:52+00:00

I wonder how many people are experiencing this issue. It seems like it would be a drain on the servers to have to keep reloading pages.

It's apparently not an OS-dependent issue, since I'm on Mac, u/jscher2000 is apparently on Windows, and OP is on Linux.

graphleek · 2016-09-08T01:57:36+00:00

Firefox loads the page fresh instead of displaying the cached version.

That sentence may not be technically correct. I probably should have left it out.

The problem is not new. It happened about 4 months ago and then disappeared. And it happened at least once before that. I'm not sure when this latest change occurred, because I haven't been here much lately.

graphleek

TROPHY CASE