[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: hosting lua.org
- From: Paul Ducklin <pducklin@...>
- Date: Tue, 22 Aug 2023 21:44:30 +0000
The lua-users.org content needs to become a proper HTTPS site with no inept-looking certificate error when anyone with a browser built within the last few years tries to visit it securely.
Proper HTTPS on a web server should be considered as unarguable as banning smoking in the workplace, and failing to provide it by default for your users can be considered as disrespectful and as reckless as not wearing your seatbelt when in the rear seats of an automobile. (You wear rear seatbelts to protect the person in front of you from being smashed to pieces by the momentum of your head and body in the event of a crash, even if you couldn’t care less what happens to you.)
And once you have HTTPS then it’s useful to auto-redirect HTTP to HTTPS, and to use HSTS in your secure headers
Time to party like it’s 2023…
> On 22 Aug 2023, at 08:59, Pierre Chapuis <lua@catwell.info> wrote:
>
> The hardest part by far will be the mailing list. For this I do not see any good alternative to something like mailmanhost.com indeed.
>
> lua-users.org should be slightly simpler but it's an old stack, mostly composed of Perl CGI for all I know. The wiki is a fork of UseModWiki [1]. The mailing list archives is a CGI script too. The simplest solution is probably to migrate everything a VPS somewhere.
>
> I don't think there is a need for separate static hosting for lua.org, maybe just stick it on the same box as lua-users?
>
> [1] http://lua-users.org/wiki/ThisWikiImplementation
>
> --
> Pierre Chapuis
>
> On Sat, Aug 19, 2023, at 01:01, Petite Abeille wrote:
>>>> On Aug 18, 2023, at 20:21, siiky <github-siiky@net-c.cat> wrote:
>>>
>>> I would suggest SourceHut[0,1]
>>
>> Ah, yes, SourceHut. Perhaps more in keeping with Lua's ethos of frugality.
>>
>> https://sourcehut.org/alpha-details/
>> https://sourcehut.org/blog/2022-11-15-four-years/
>> https://sourcehut.org/blog/2023-03-27-2022-financial-report/