Conversation

Notices

1. Verius (verius@community.highlandarrow.com)'s status on Saturday, 16-Sep-2017 10:45:09 EDT Verius
   Lol. Caddy webserver goes proprietary for provided binaries and adds promotions for sponsors in HTTP client headers. Fork happens (named Wedge). First issue in the fork (by fork author): remove references to Caddy. Second issue (by someone working on Caddy): accusation of trademark violation.
   
   Caddy author later writes a post saying people are mean to him over the changes. In that post he says the trademark thing was well handled and amicable between the Caddy and Wedge authors whereas people accused Caddy folks of being mean over it.
   
   Uhm, if you don't search the literally one element issue list and immediately create a lawyeresqe issue about trademark violation that's perceived by most hackers as aggressive. Getting flak over that isn't weird.
   1. Verius (verius@community.highlandarrow.com)'s status on Saturday, 16-Sep-2017 10:49:19 EDT Verius

      in reply to
      Also if I were still running Caddy I'd be looking very hard at a migration to something else. The monetization drive _will_ create pressure on the authors to add features to the proprietary binaries that aren't in the Apache licensed source code. And eventually you end up with Nginx. Except that Nginx is actually a pretty solid piece of software despite the annoying open core model and Caddy is essentially a webserver for really lazy people who can't be bothered to figure out how to configure Apache or Nginx.