@freedosproject About 13 years ago a client bought a new high-end workstation (i7, 16 GB RAM, SSD). He also wanted to be able to still run his old QuattroPro for DOS on it, and to print from it. I set him up with DOSBox-X to do that.
@emilygorcenski I've got a .htaccess that redirects a bunch similar endpoints to a tarpit (short perl script that outputs around 9 bytes/second, limited to at most 20 simultaneous requests, to not DoS my own server).
@hramrach@Polychrome Those hours include typesetting (including animating all the moving signs) and at least one QC pass (or at least they did back when I was doing this).
@christian@Suiseiseki You have to do it within the program itself (according to the strict AGPL interpretation, you have to offer the source code as the very first thing when any user accesses the program running on your server). And no, NextCloud does not do this, and neither does any other AGPL program I've come across – it's a mess.
marcan had a great twitter thread on this (with a bunch of examples), but it's unfortunately gone.
@Suiseiseki The point of AGPL is that any end-user of the software has the right to the source code of the program they're using, even if it's running on a remote server. It doesn't matter that the patching here was done by the distro – since you're running the program, you're the one that has to provide the exact source of the running program, otherwise that'd be a loophole anybody could use to avoid complying with AGPL.
And while marcan's post was about dspam, where it's questionable if its use even counts as end-users having interacted with it, there are a lot of web apps, where the end-user interaction is obvious (eg. NextCloud).
@christian@Suiseiseki The problem is that if you put NextCloud (or any other AGPL-license program) on the internet, you yourself have to provide the source code of your running instance to anybody who accesses it. How do you achieve that?