Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xHhNh-00000003FgJ-2OiL for pgsql-www@arkaria.postgresql.org; Fri, 16 Oct 2026 12:49:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xHhNg-0000000EDC6-1hLU for pgsql-www@arkaria.postgresql.org; Fri, 16 Oct 2026 12:49:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xHhNg-0000000EDBv-0muC; Fri, 16 Oct 2026 12:49:52 +0000 Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xHhNd-00000002UEy-2nXy; Fri, 16 Oct 2026 12:49:51 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.stravinsky; h=X-Debian-User:In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=kZElzoLMnu6aoFz16QmDk7NVKngs8y5nqirKEneCSD8=; b=YYjCbRaJVZQYndjq9RE3DY4nVP Css7pVEYRpA2LSZiCwkullULEnjZTgp+hXHfE450iciSZNT1Ao+iKI6kfzcUpS8DuTPU93K1V3T8E P8G5w+BrP60vM1ycQJfM9Kon8WoJrAd/SviHHQVv6uT7k5l0CUbhhNiD1NvPgrYu921/YmR7G1pTV xsMqMelrN1G4Lk8wZpvxKh/nDIzt1lhm8XMzpf44DqTlm89rvzBAO4NkUJW2ZSbsR1K71ao+u++3y LwcnilpRMaXjxrsRBW193jYTGVAQ1v++LVmNQiGCfjfc1iNZyBQGse/hPiBosAql16Yb4gsAd3CDq c3Z3wScw==; Received: from authenticated-user by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from ) id 1xHhNa-005ybL-33; Fri, 16 Oct 2026 12:49:47 +0000 Date: Fri, 16 Oct 2026 14:49:45 +0200 From: Christoph Berg To: Dave Page Cc: Magnus Hagander , "Jonathan S. Katz" , Daniel Gustafsson , pgsql-www@lists.postgresql.org, Andrey Borodin , Melanie Plageman , PostgreSQL Contributors Subject: Re: Introduce contributor badges Message-ID: References: <329b5d0e-44ba-4c5f-8cc9-c9eb5424955b@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Debian-User: myon List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Re: Dave Page > > What max input size would we accept? 2000x2000 (4 megapixels) should > > be pretty much enough for everyone? > > These are images for badges - why on earth do they have to be that big? You > pad them and then display them at 150x150 from what I can see. All of that > seems like work that needn't be done by our servers - I would have the user > upload at <= 256x256 or something (and adjust max_length to something more > reasonable), and then pad and resize them in CSS. Which looks like it might > be broken anyway - .badges-grid uses minmax(150px, 1fr) with img { width: > 100% }, so on wide layouts a 150px image likely gets stretched beyond its > real size. That would be the max acceptable input size before server-side rescaling. I proposed something insanely large that shouldn't get in the way of anyone uploading while still limiting server memory. What you are saying is that we shouldn't do server-side rescaling but just take the user image-as is. That works for me. I'll work on a patch to make that switch. (The question might come back if we want to build a sprite image.) Christoph