⚔ Kirito

It would also be nice if the content/post reported could be attached directly to the warning itself.

If you warn a user for making a post and then delete the post, the user may have no clue what they're actually being warned for.

The only way to avoid this is to manually include a quote of the post with every warning you make.

There are so many potential improvements available to the warnings system. I'm kind of disappointed that no one else is expressing any interest.

Yeah, because if you forget to attach the image to a specific place in your post, it will just up and vanish into the abyss, it doesn't conveniently locate itself at the bottom of your post automatically or anything.

Because it definitely makes sense to assume that when you don't see your image anywhere in the post you're making, that it's magically going to appear in the place you were typing when you started to upload the image.

The only thing I'd really like is an "attach all to post" function, which I was looking to add into my forums myself sometime soon.

If IPS as a company would suddenly disband, the software would stop getting updates. It wouldn't go away.

It would mean that if any security vulnerabilities are discovered in the future, you would be responsible for investigating them and applying patches yourself.

But otherwise, who knows. You can't estimate how things will be in 17 years.

I looked into that, from what I've seen there don't seem to be many major differences between SPDY Draft 2 and Draft 3, minus flow control which has some reported issues that are still being worked on I think.

I believe that is the reason NGiNX has not yet adopted Draft 3.

I'm mostly wanting to see rate limiting support with SPDY connections. That's one "bug" that's still being worked on.

Just adding a note for myself for when/if I come back to this.

 

Imagemagic: -interlace Plane

GD: http://www.php.net/m...geinterlace.php

I've just added this in to Imagemagick's class directly on my forum. I have it set to interlace images larger than 100x100px when resizing, since I don't think there's really a need to exclusively add this as a function for IP.Gallery only.

Lines 304-359

                //---------------------------------------------------------
                // Use Plane interlacing for 100x100px+ images
                //---------------------------------------------------------
 
                if ( ($new_dims['img_width'] > 100) && ($new_dims['img_height'] > 100) )
                {
                        $interlace      = " -interlace Plane";
                }
                else
                {
                        $interlace      = "";
                }
 
                //---------------------------------------------------------
                // Resize image to temp file
                //---------------------------------------------------------
 
                if ( $type == 'gif' )
                {
                        system("{$this->im_path}convert {$this->image_full} -coalesce  {$this->temp_file}");
 
                        $this->image_full = $this->temp_file;
                }
 
                /* Canvas? */
                if ( is_array( $canvas ) && count( $canvas ) )
                {
                        $border         = array( 0, 0 );
                        $borderStmt = '';
 
                        /* Figure out border - round/str_replace are to ensure locales do not result in "39,5x0" */
                        if ( $new_dims['img_width'] < $width )
                        {
                                $border[0] = round( str_replace( ',', '.', ( $width - $new_dims['img_width'] ) / 2 ) );
                        }
 
                        if ( $new_dims['img_height'] < $height )
                        {
                                $border[1] = round( str_replace( ',', '.', ( $height - $new_dims['img_height'] ) / 2 ) );
                        }
 
                        if ( count( $border ) )
                        {
                                $borderStmt = ' -bordercolor white -border ' . $border[0] . 'x' . $border[1];
                        }
 
                        system("{$this->im_path}convert{$quality}{$interlace} -resize \"{$new_dims['img_width']}x{$new_dims['img_height']}!\" {$borderStmt} {$this->image_full} {$this->temp_file}" );
                }
                else if ( ! empty( $this->_cropX ) || ! empty( $this->_cropY ) )
                {
                system("{$this->im_path}convert{$quality}{$interlace} -resize \"{$new_dims['img_width']}x{$new_dims['img_height']}^\" -crop \"{$width}x{$height}\" {$this->image_full} {$this->temp_file}" );
        }
        else
        {
                system("{$this->im_path}convert{$quality}{$interlace} -resize \"{$new_dims['img_width']}x{$new_dims['img_height']}!\" {$this->image_full} {$this->temp_file}" );
                }

Not the best example of it in action, but it still makes a noticeable difference on slower connections:

https://www.anime-so...iew_style=large

Also, I have a minimum height for theImage set on my forum, which prevents that unpleasant "snap" on every page load. (The page rendering with no image, then the image loading and making the image box to expand with it.)

If you could add a dynamic minimum height to the theImage div container equal to the medium images actual height, it could offer a more pleasant viewing experience for the user.