From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "Philip K." Newsgroups: gmane.emacs.devel Subject: Re: Proposal for an Emacs User Survey Date: Fri, 09 Oct 2020 20:17:41 +0200 Message-ID: <87lfgf9sca.fsf@posteo.net> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31738"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Adrien Brochard Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Oct 09 20:18:59 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kQwyp-00087Y-7U for ged-emacs-devel@m.gmane-mx.org; Fri, 09 Oct 2020 20:18:59 +0200 Original-Received: from localhost ([::1]:33468 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kQwyo-0005Jj-8x for ged-emacs-devel@m.gmane-mx.org; Fri, 09 Oct 2020 14:18:58 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60798) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kQwxg-0004ro-IJ for emacs-devel@gnu.org; Fri, 09 Oct 2020 14:17:49 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]:41409) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kQwxd-00022q-W8 for emacs-devel@gnu.org; Fri, 09 Oct 2020 14:17:48 -0400 Original-Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 7C32C2400FD for ; Fri, 9 Oct 2020 20:17:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1602267462; bh=jqUoLuc0EIZ9Wi9x5JZumKK27v4ujG7r5NGpgeHzo2M=; h=From:To:Cc:Subject:Date:From; b=sJFrInXn/aaDLty3KRwZxg/e58gNX65CXN9cz2C89/fLh20GRlPlF62lFfRcDUtYh gS+tSKfMsJdItcRDxXeiR8m9s/6fHJWmAd9kTpV3iI55asGFx7gh0KVZiQ4Q4JE66A qcgUd19GGUqUa6B+a/jS5ii5rzjgd0fR2fYzib2VnaQ/Hna3VrE56/icl9N/10SSIL Ydx0cZXko8WqxtavRRCK6vIbq0R1ak1iLo3icbcCYKggKiG15bd1qvhIq+FSkwx00b 1r4aT6IDKItutQnXJTFVvJHLvLT9ciSqp1iUrC0Ys/ui+CIJJFXE5Gt57rQfFb4hFZ XYqrLFyiZdk1w== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4C7GWn6Qlkz9rxK; Fri, 9 Oct 2020 20:17:41 +0200 (CEST) In-Reply-To: (message from Adrien Brochard on Fri, 9 Oct 2020 13:23:19 -0400) Received-SPF: pass client-ip=185.67.36.66; envelope-from=philipk@posteo.net; helo=mout02.posteo.de X-detected-operating-system: by eggs.gnu.org: First seen = 2020/10/09 12:40:08 X-ACL-Warn: Detected OS = Linux 3.11 and newer [fuzzy] X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:257275 Archived-At: Adrien Brochard writes: >> For the fun of it, I wrote a simple survey application[0] that includes >> a self-hosted captcha (without tracking anyone), requires no Javascript, >> is mobile friendly and should be fairly fast. Of course it can be >> improved. I wrote it as a quick and dirty evening project, but I >> think it demonstrates that this kind of an approach is practicable. >> >> [0] https://git.sr.ht/~zge/survey > > Thank you! I really like reading go code (no sarcasm). > It it clear that this approach will work but the remaining 20% are the > hardest. I'm concerned with: > - cleaner UI, not just HTML embedded in the code What would you have in mind? I know that my example is simple, but I prefer that to sites that take forever to load and reload everything all the time, for no apparent reason. > - mysql instead of sqlite, which also implies a mysql instance running SQLite is actually surprisingly resilient, according to [0]: > SQLite works great as the database engine for most low to medium traffic > websites (which is to say, most websites). The amount of web traffic > that SQLite can handle depends on how heavily the website uses its > database. Generally speaking, any site that gets fewer than 100K > hits/day should work fine with SQLite. The 100K hits/day figure is a > conservative estimate, not a hard upper bound. SQLite has been > demonstrated to work with 10 times that amount of traffic. But either way, I used sqlite to avoid setting up a RDBMS. [0] https://www.sqlite.org/whentouse.html > - DOS protection, maybe some rate-limiting and IP blocking > - HTTPS, thankfully it's easier now AFAIK these things can usually be handled by a frond-end such as NGINX. > - monitoring, how do we know the service is running as expected > - logging, and how to store logs for debug If there is any interest, extending the example to support this would be feasible. The "20%" you mention aren't easy, but from what I see it shouldn't be too hard either. > My greatest fear is people clicking on the link, filling out the form, > trying to submit, seeing an error page, and never coming back to it. The reason I suggested using a simple HTML form and implemented the demo was because I think simplicity helps avoid a lot of issues. With fewer dependencies, secondary services, modules, etc. the chance of one of these failing decreases. And having a smaller footprint should also reduce the network load. > Best, > Adrien -- Philip K.