Can we ban massive photos being posted?

[531Aussie]

I know it ain't the end of the world, :) but it is annoying having
to continually scroll a long way left and right to read all the posts on a page
just because someone has posted a huge picture!!

This pic that someone posted measures 2ft3" wide on my screen!! :)

http://www.bikeforums.net/showthread.php?p=4498350#post4498350

I'm obviously not singling out this person, because a lot of people do it -- it's just an example

thanks

[jjvw]

I second this!

[Stacey]

If it bothers you so much either turn pictures off in your User Control Panel or don't bother looking at them.

Maybe a PM to the offending party asking if they need help resizing their wonderful pictures.

Just sayin' ya know.

[Wil Davis]

It's bad enough when folk post large pics, but even worse when the "me too!" brigade quote the original post along with the giant hi-res pictures!

It is actually quite easy to post pics which will load quickly, and still look a reasonable size; start by using a resolution of 72 pixels/inch (anything higher is wasted when viewed on a computer display), and resize the picture to around 800x600 pixels, and save as a .jpg file with a compression of about 6 (on a scale of 1-12 if you're using PhotoShop™ …you know it makes sense!

- Wil

[linux_author]

dial-up is the problem, FIOS is the answer... (i.e., 55Mbps service)

gotta have those fat pipes!

:-)

p.s. (i always use a '56K Warning' in thread title when posting big pics)

[531Aussie]

don't bother looking at them.
.as I suggest above, it's not that simple

a massive picture effects every post on the page

[slvoid]

You mean like when some jackass posts a 40,000 pixel wide image?
http://www.tawbaware.com/maxlyons/gigapixel_strip.jpg

[531Aussie]

You mean like when some jackass posts a 40,000 pixel wide image?
]
yeah, now see how much fun it to read my post, which will, no doubt, be very interesting. Don't stop reading -- it will be worth it. Once upon a time, a lazy brown pope in the woods with a quick duck and a lazy bear with one leg jumped over a quick green frog in a blender from the Bud commericial

now try reading last night's race report from the Giro

Alessandro Petacchi, showing some of the sparkling form that propelled him to a record nine Giro d'Italia wins in 2004, used his unbeatable turn of speed to take his third Giro win on stage 11. Petacchi prevailed in a messy dash to the line in Pinerolo that saw a huge pileup behind the first ten riders, besting Italian Gabriele Balducci (Acqua & Sapone-Caffè Mokambo) and Robbie McEwen (Predictor-Lotto) after 198 kilometres in the saddle.

"I think today was dangerous but my companions did well," noted Petacchi after his 22nd Giro stage victory. "Maybe they went from too far out. I lost a little bit of speed [through the final bend] but I was able to make a great remount."

Just before the finish line, the wet pavement caused Nikolai Trusov's (Tinkoff Credit Systems) to lose control from a top ten position, and his crash caused a domino-like effect that resulted in maglia rosa Andrea Noè (Liquigas) sliding across the line on his backside. World Champion Paolo Bettini was also among the crash victims, but he and Noè were for the most part unharmed. Noè held onto the race lead, keeping his 1'08" advantage over Marzio Bruseghin (Lampre-Fondital).

The day was characterised by a long solo breakaway by Mickaël Buffaz (Cofidis), who nearly cracked under the strain of his efforts and stopped in tears at the halfway point in the stage, but soldiered on until 11 kilometres to go before being caught. With the sprinters focusing on the finale, specifically a dangerous U-turn to the right at 3800 metres to go, the peloton negotiated the tricky bend safely before yet another last-minute attack from the Tinkoff team. It was once again Mikhail Ignatiev, the Russian Olympic Champion, who was pulled back by Petacchi's diminished train of four right under three kilometres remaining.

As the metres ticked down, the fight for Petacchi's wheel was in full fury, with McEwen and Danilo Napolitano (Lampre-Fondital) fighting for position while Crédit Agricole's Bodrogi launched Julian Dean off the front. All the while, Petacchi kept his cool, first behind Lorenzetto and then Lancaster while the New Zealand champion rocketed up the road with 600 metres remaining. "I was afraid with the water and I did not want another crash with my knee," Petacchi confessed, "Lancaster went at 600 metres and did a great job. I was happy with his work because I was really scared over the wet pavement."

Bettini and Trusov
Photo ©: Sirotti
With Dean reeled in, Napolitano and McEwen continued to fight for Petacchi's wheel in the final left-hand bend at 250m, but when Petacchi fired up his cylinders, he displayed his dominant form that seemed to elude him since he broke his kneecap in last year's Giro, and easily kept McEwen at bay. Acqua & Sapone's Balducci ended up third behind the Italian and Australian.

"Balducci did well to come up. I have known him for many years." Regarding the emerging rivals, Petacchi added, "In a sprint like this, on a slight decent [a 37m elevation drop in the last 3.7km - ed.], it is easy for the others to re-enter, like Balducci."

Thor Hushovd and stage nine winner Danilo Napolitano came across safely in fourth and fifth, but as Nikolai Trusov (Tinkoff Credit Systems) tried to play his cards in the sprint, he lost traction on the wet pavement and slid out, taking down World Champion Paolo Bettini (Quickstep-Innergetic) with him. The crash ricocheted through the peloton as riders tried to brake to avoid the carnage, with Benoît Joachim (Astana) and Alexandre Pichot (Bouygues Telecom) hitting the deck next.

Alessandro Petacchi (Milram)
Photo ©: Sirotti
Andrea Noè's pink race leader's jersey and matching shorts couldn't protect him from the force of gravity, and the maglia rosa arrived in a most ungraceful fashion as Noè skidded over the line on his backside. "I arrived, sliding across the line," he recalled. "Unfortunately the sprinters braked on the line but it remains a mystery why," said the 38 year-old.

"Tomorrow we will see. It will be a hard day for [Danilo] Di Luca but also for everyone else," finished Noè.

Having taken nine Giro wins in 2004, six in 2005, and then crashing out before winning any in 2006, Petacchi is uncertain whether he will contend for more wins in this year's Giro or cut his risks. "I still am not sure if I will go on from here. I want to do a good Tour [de France], so I don't know. I will enjoy this victory now and then tonight I will talk to [DS Gianluigi] Stanga. I will think about it."

Of the GC hopefuls who were affected by the maxi-caduta ('big crash'), Yaroslav Popovych (Discovery Channel), third overall in 2003, seemed to be in bad shape at the finish line, leading to doubts as to whether he will start stage 12 to Briançon. Two-time Giro d'Italia champion Paolo Savoldelli also went down, but was unhurt, while Euskaltel-Euskadi's Aitor Hernandez finished the stage, but was later confirmed with a fractured collarbone, and will not take the start on stage 12.

How it unfolded
38 year-old Andrea Noè (Liquigas)
Photo ©: Sirotti
Today's stage from Serravalle Scrivia to Pinerolo started at 12:02 when 171 riders rolled out. Flèche Wallonne Champion Davide Rebellin (Gerolsteiner) did not take to the start line.

Through small Italian cities, like Novi Ligure and Ovada, the riders stayed 'gruppo compatto' (meaning the peloton was all together). After the first hour of racing the pace was at 30 kilometres per hour, a completely different story than yesterday's stage, where the pace was an amazing 51.2 km/h.

Shortly after this first hour there was an attack by Frenchman Lilian Jegou (Française Des Jeux) and Belgian Pierre Drancourt (Bouygues Telecom). The former took the sprint at the line in Cremolino (kilometre 37.8).

This duo was absorbed by the peloton and, by kilometre 38, there were to more riders off the front, Frenchmen Carl Naibo (Ag2r Prévoyance) and Mickaël Buffaz (Cofidis). Two kilometres later, Naibo had faded gone and his compatriot had taken 50". This time gap turned into 1'48" by kilometre 45.

In Acqui Terme, kilometre 50.8, the lone rider had 3'55", and by Bubbio, kilometre 68.3, he had 5'10". The riders continued at a gentlemen's pace; the average was 32.5 km/h after two hours of racing.

After three hours of racing, in Borgomale (kilometre 94), the gap reached 8'14" but then the 28 year-old had a moment of crisis. At 15:15 the Frenchman, born in Geneva, stopped on the side of the road. While the cameramen did their jobs, taking photos, he was crying in the arms of his directeur. He only took back on his bike after some encouraging words by his directeur sportif.

This stop dropped the gap down to 3'16" at kilometre 101. But due to the Gruppo Maglia Rosa putting on the brakes and having a relaxed day, the gap to Buffaz had shot up to 7'05" at 75 kilometres to the finish (kilometre 123). Buffaz was seen waving to the camera and, now, enjoying the day and not really 'trying' to build his gap. He must have been thinking that the day would belong to the sprinters' teams of Milram, Predictor and Crédit Agricole.

Andy Schleck (Team CSC) rides
Photo ©: Sirotti
In Bra, where it was 34°C at 69.5 kilometres to go, Buffaz's gap had gone higher than the pre-crisis time of 8'14", to 9'15". This started to fall as Danilo Napolitano's Lampre men moved to the front. By 60 kilometres to go Milram added its men and the gap was falling further, to 6'15".

With fifty kilometres remaining Buffaz was clinging onto a gap of 5'55". It was looking bad for the Cofidis man; Milram, Lampre and Predictor were adding coals to the chase-fire while clouds and winds were making the going tough.

Buffaz took the Garibaldi sprint in Saluzzo (-38.1 km) and the peloton passed, led by Nicolas Crosbie (Bouygues Telecom) and then Simone Masciarelli (Acqua & Sapone-Caffè Mokambo), 4'15" later. The race started to fall at the same moment. By 30 kilometres to go, with rain hitting heavily in Pinerolo, the gap had fallen to 2'42".

Tinkoff was moving some of its men to the front to prepare for a counter-attack. By 20 kilometres to got Buffaz was barely holding on to a one minute gap. Petacchi was tightening his toe-straps and ordering his Milram milk men to the front, like Mirco Lorenzetto. But there was also Hushovd's Crédit Agricole men moving to the front.

Paolo Bettini (Quickstep-Innergetic)
Photo ©: Sirotti
The gap had dramatically tumbled to 24" only five kilometres later. The sprinters teams were gearing up and ready to fire over the wet roads. Slightly up the road Buffaz was waving goodbye to the TV viewers. His dramatic day ended at kilometre 187 and the 'gruppo compatto' had 11 kilometres remaining for counter-attacks.

One had the sense that Oleg Tinkov's Tinkoff boys would fire as they had been amassing at the front over the final few kilometres. They were joined by Acqua e Sapone, who were setting up for Balducci. The water and soap team slowly led through the U-turn that Mikhail Ignatiev used as his launch pad.

A relatively quite Tinkoff day became animated but it did not last long. Milram, washing out Acqua, caught the 22 year-old Russian after the road curved right onto Via Giustetto. Off of this road, slighting turning onto the Stradale di Fenestrelle, Milram led for the eventual Petacchi win.

Stage 12 - Thursday, May 24: Scalenghe - Briançon (Francia), 163 km
The first major mountains of the 90th Giro d'Italia loom to the west of Torino in the Alps on the Italian/French border. The antipasto is the heavy duty Colle dell'Agnello, a 21.3-kilometre beast that rises to 2744 metres after 102 kilometres of racing. At the summit, the road plunges into France and at the famous road junction in Chateau-Queyras, turns right up the southern face of the evocative Col d'Izoard.

This legendary Tour de France ascent covers 14.2 kilometres at an average of 7.1% and the last few kilometres traverse the picturesque section called the Casse Deserte. Once over the 2360-metre summit, it's a steep descent to finish in Briançon. Look for the Giro strong-men to emerge on Stage 12.

[linux_author]

You mean like when some jackass posts a 40,000 pixel wide image?


- congrats! you just exposed a firefox image display bug!

[vtjim]

Get a real browser! I.E. *6* handles it just fine.

:p (ducking)

Yeah, I hate extra-wide pictures too. Just to stay on topic.

[Psydotek]

You mean like when some jackass posts a 40,000 pixel wide image?
HUGEFREAKINPIC

Holy crap that's hilarious!

:roflmao:

[low8all]

lamest thread ever.

[spingineer]

I nearly fell out of my chair reading this ...

[Portis]

http://www.tawbaware.com/maxlyons/gigapixel_strip.jpg

This thread is a lot more interesting about 40 yards over that way ----------->

You guys should go check it out.

[Mr. Smashy]

I have one that is much much longer.

[kemmer]

Ya know, I don't have to scroll left/right to read the other posts in the thread with ie or Opera. Fire fox does make you scroll. I don't think it would be a good idea to restrict image size since some people have enought trouble posting pictures as it is. Then again, it doesn't hurt to force people to learn how to work the interwebs a little now and then.

[donnamb]

You know, those of you that find this annoying could always send the OP a friendly PM offering to help show them how to reduce an image. :)

[cycle life]

Funny thread

[sean999]

Actually, it's not funny, it's kind of a drag to have a BF page take *forever* to load because of a huge photo. Not everyone has a high-speed connection, and even if we all did, there's no excuse for wasting bandwidth. Sending an IM to every offender is not a real solution for this problem, just as it isn't for other "netiquete" issues that are avoided by preventative measures at this and other forums.

Truly huge photos are wasteful and stupid and easy to ban -- LOTS of other sites do it, for the sake of users as well as server loading.

[Pupsocket]

my worn out horizontal scroll bar just fell off the screen and landed on F10

[rm -rf]

That's interesting -- the 40k wide picture didn't affect the text for me, on Firefox. It all fits on the screen. Maybe it's so large that the text width doesn't go over there, because usually it makes the text boxes wide.

IE makes the text box really wide here.

That would be a good BF improvement -- to limit the the width of the postings, but allow the big photos to go off the right margin. I don't know if it's feasible.

[rm -rf]

At least he didn't post this 50 million pixel wide hydrogen atom picture. (http://www.phrenopolis.com/perspective/atom/) :eek: :D

[Brian]

I just plug my laptop into our 52" flat screen. Never had to worry about image size...

[jschen]

At least he didn't post this 50 million pixel wide hydrogen atom picture. (http://www.phrenopolis.com/perspective/atom/) :eek: :D
I like that pic. :)

[monogodo]

I noticed today that another forum (http://www.tarantulas.us/forums/) running vBulletin 3.6.7 has a large photo resize feature. Not quite sure how it works, but it's there.

If you check this post (http://www.tarantulas.us/forums/showpost.php?p=50674&postcount=13), you'll see two pics I posted that I cropped and resized. Below them there is a third pic that I didn't crop & resize, yet it fits nicely on the screen and has a message at the top that reads "This image has been resized. Click this bar to view the full image. The original image is sized 2288x1712." If you click the bar, it resizes to the original size and the message changes to "Click this bar to view the small image."

This might be something for the Admins to look into.

[Brian]

This might be something for the Admins to look into.

As if I really want to work. :D

I'll see what we can do.

[gmason]

For a start, when I go to post an image, the limits on the management window are all 100 kb. Why isn't that simply enforced? Or changed?

[Brian]

For a start, when I go to post an image, the limits on the management window are all 100 kb. Why isn't that simply enforced? Or changed?

Because that's for uploading images. If it's hosted somewhere else, there is no size limit.

[gmason]

Because that's for uploading images. If it's hosted somewhere else, there is no size limit.

Every day, even at this advanced age. :)

[monogodo]

Found another option to deal with this.

On another forum, running vBulletin Version 3.6.5, in the User Control Panel, under Options & Thread Display Options, they have the option for Maximum Width & Maximum Height.

Might be worth looking into.

[Brian]

Found another option to deal with this.

On another forum, running vBulletin Version 3.6.5, in the User Control Panel, under Options & Thread Display Options, they have the option for Maximum Width & Maximum Height.

Might be worth looking into.

See post 28. I don't think I can control what people hotlink to.

[monogodo]

See post 28. I don't think I can control what people hotlink to.

From what I understand about the feature I just mentioned, it controls inline image width/height. I'm working on clarifying this right now, and will let you know what the response is.

[jschen]

Not sure about the technicals, but in any case, auto-resizing may not be such a great idea. It encourages people on ultra-fast connections to go ahead and hot-link a pic even if it's absurdly large. Sure, it will be forced into a small rectangle, but you may end up with a lot more multi-megabyte images to download.

[monogodo]

Here's the plugin information the other forum uses:

nCode Image Resizer 1.0.1 Automatically resize posted images

[Brian]

Here's the plugin information the other forum uses:

Brian is not allowed to install plugins. :(


[edit] But I will suggest it to our tech guy.

[operator]

You know, those of you that find this annoying could always send the OP a friendly PM offering to help show them how to reduce an image. :)

What?? No. That's crazy!

P.S Please don't install any image auto-resizers. It's very lame. If someone is purposely posting large images as part of a page widening technique maliciously they can be banned. Other members can be reminded just to not post them.

[Brian]

What?? No. That's crazy!

P.S Please don't install any image auto-resizers. It's very lame. If someone is purposely posting large images as part of a page widening technique maliciously they can be banned. Other members can be reminded just to not post them.

So you know/knew Prisoner?

[Maelstrom]

Actually, it's not funny, it's kind of a drag to have a BF page take *forever* to load because of a huge photo. Not everyone has a high-speed connection, and even if we all did, there's no excuse for wasting bandwidth. Sending an IM to every offender is not a real solution for this problem, just as it isn't for other "netiquete" issues that are avoided by preventative measures at this and other forums.

Truly huge photos are wasteful and stupid and easy to ban -- LOTS of other sites do it, for the sake of users as well as server loading.

Even with high speed its annoying.

Especially when people quote respond.

I love pic threads, when they have an application. Look in mountain biking for some of petes threads of pics of trails etc. Absolutely stunning (makes for great backgrounds too) A nice warning in the title works too. I would hate for the pics to be tiny.

I would hate to see auto resizers too. Its a tough call, cator to the people with low bandwidth or let those of us who have it, have access to stunning pics in proper size. I think you need to look at the averages. How many people have dial up vs high speed. I betcha most of the active users have high speed.

[monogodo]

I'm on a T3 line at both home and work. I hate large size images because it throws off the formatting of the page.

I see nothing wrong with posting a small image (600 width) as a link to an off-site full-size image. People can still see the image and get the general idea of what it is, and can click the link and view it full-size if they wish. Using one of the resizing options I've posted about just make it easier on all of us.

[operator]

I'm on a T3 line at both home and work. I hate large size images because it throws off the formatting of the page.

I see nothing wrong with posting a small image (600 width) as a link to an off-site full-size image. People can still see the image and get the general idea of what it is, and can click the link and view it full-size if they wish. Using one of the resizing options I've posted about just make it easier on all of us.

Maybe you should install the plugin for YOURSELF and not recommend it to force it down everyone else's throat. Ok? If this does get implemented, at least let registered users control whether or not images are automagically resized via options.

[Blue Jays]

The courteous thing to do is to post normal-sized images that won't inconvenience the vast majority of users using typical monitors.

[monogodo]

Maybe you should install the plugin for YOURSELF and not recommend it to force it down everyone else's throat. Ok? If this does get implemented, at least let registered users control whether or not images are automagically resized via options.

The plugin has to be installed server-side, dumb*****, otherwise I'd already have it and would be telling people where to get it & how to install it, because I'm helpful like that. If it does get installed, I'd recommend that the default be set to off. My understanding is that registered users (both paid & un-paid) would have the ability to make the setting changes in the User Control Panel. Unfortunately my keyboard doesn't work (I'm typing this with the On-Screen Keyboard), so I can't get/post a screen cap.

You really should think before you click the Submit Reply button.