Replies

Don’t know if it’s just me, but I can’t see the images you post tonight. I’m just getting the little squares. I can usually see them fine.

I usually can’t see foldy’s posts. It may be the time of day/traffic at the hosting site.

SLIDE- ON FILE SIZES

Q&A is On.

"Don’t know if it’s just me, but I can’t see the images you post tonight. I’m just getting the little squares. I can usually see them fine."

As meyer just said: "The burger hasn’t changed,..."

Nothing has changed in the uniform manner that [F] posts, i.e. source file sizes are 90% identical.

The issue(s) experienced here were caused by Sobieskis' WHALE-SIZED gif of 38.2MB at post #994.

Even when you navigated to the next page, this post would be causing download, latency, and bandwidth issues for your 'pipeline', locally and on the network. Most with high-speed connections didn't have a problem.

But I even noticed a 1/4second hiccup loading this MONSTOROUS FISH on the screen, downloaded the gif, and saw that the "FISH WAS THIS BIG".

SOB- You may choose to keep the individual'GIF's under 7MB, most are under ~6MB, with a few done at 9MB.

[F] typically edits 90% of gif posts; with 3sec pause to start, and 5sec pause at end.

This self-imposed 'size matters' was found to be acceptable by prolific posters in 2017-2018 on the Q thread.

Those sizes suggested may have improved recently, yet there is no guideline published by FR to my knowlege.

That said, the combination of provider speed, computer hardware, and computer software all affect the users web 'experience' in literally a thousand ways!

F