This is really exciting! I particularly like the lightness of the web-pages and the non-necessity of javascript. The support for the BSDs in the build system (F

This is really exciting! I particularly like the lightness of the web-pages and the non-necessity of javascript. The support for the BSDs in the build system (FreeBSD at the moment, OpenBSD and NetBSD planned[0]) is also nice — as a Linux person I've far too often ignored the other Unixes and POSIX / general Unix compatibility. I hate being THAT guy, but would you consider trying[1] to re-license the AGPL-3.0 bits to AGPL-3.0-or-later, unless sticking with just v3 was deliberate (in which case fair enough)? My rationale: i) License-incompatibility is a curse that fragments the copyleft world. ii) Worrying about AGPL-3.0-only being incompatible with AGPL-4.0, in ten years time, if/when the latter comes out, will be too late, as (hopefully) sr.ht will have had hundreds or thousands of contributors, many uncontactable, by then. iii) Having AGPL-3.0-or-later instead of just AGPL-3.0 is unlikely to put off any contributors. iv) (This is subjective and might not hold for you:) I trust the FSF not to do something sufficiently crazy with its next iteration of licenses (if such exist), that I would prefer my code not to be compatible with such licenses. [0] https://lists.sr.ht/~sircmpwn/sr.ht-announce/%3C20180802214500.GA5332%40homura.localdomain%3E https://lists.sr.ht/~sircmpwn/sr.ht-announce/%3C201808022145... [1] This obviously also depends on the other contributors, so you might not want to bother with the effort.