News for hackers. Stuff that matters.
Re:Announcing Caddy Commercial Licenses by StavrosK on Wednesday September 13, 2017 @10:10AM (#15238394)
> And even among your technical visitors, how many of them actually inspect the response headers?

I find that a bit disingenuous. You can't both include annoying headers and argue that they aren't annoying anyone because nobody will see them. If nobody will see them, why add them in the first place?

Re:Announcing Caddy Commercial Licenses by mholt on Wednesday September 13, 2017 @10:29AM (#15238602)
I know devs who use Sublime Text almost indefinitely without paying. They don't mind the little "Hey don't forget to buy" popup every once in a while.

We aren't putting popups on your site. :P

Re:Announcing Caddy Commercial Licenses by tylersmith on Wednesday September 13, 2017 @06:05PM (#15243165)
No, you're injecting data into traffic. That's way worse than a text editor occasionally reminding you you haven't paid.
Re:Announcing Caddy Commercial Licenses by kbenson on Thursday September 14, 2017 @03:23PM (#15251626)
Really? I don't see it as any different than an unregistered document editor saving "created with an unregistered version of X" in the comment section of saved documents that it edits. Stuff like that has been going on for decades.
Re:Announcing Caddy Commercial Licenses by kelnos on Saturday September 16, 2017 @02:46AM (#15263300)
Sure. Some people are fine with using free-as-in-beer software if the "cost" of that is the maker gets some free advertising. Some people -- like many in this thread -- are not ok with that. Both positions are perfectly valid.
Re:Announcing Caddy Commercial Licenses by bauerd on Wednesday September 13, 2017 @10:18AM (#15238478)
To give commercial users an incentive to pay for the open source software they use. Can you name an open source project that does not offer extended features for commercial versions and that sells? Because I can't
Re:Announcing Caddy Commercial Licenses by TAForObvReasons on Wednesday September 13, 2017 @11:14AM (#15239013)
There's a difference between "extended features for commercial versions" and "adware". Usually the open source version includes core features that solve a basic set of problems, and the commercial versions add additional features to solve other and/or larger problems. At no point is there an explicit crippling of the open source.

What's particularly frustrating is the burying of the lede here. The summary of the page intentionally omits the fact that you can build from source and use it in commercial contexts. And the section discussing the Apache license is factually incorrect: "Remember that building Caddy from source is still subject to the Apache 2.0 license which requires attribution and stating changes." -- that is only true if you are selling on-prem software that ships with the program. If you are using it in the normal course of your SaaS, no attribution is required.

Re:Announcing Caddy Commercial Licenses by StavrosK on Wednesday September 13, 2017 @03:43PM (#15241879)
Exactly. I would have no issue if paid usage was for things big companies are more likely to need, e.g. support, high-performance features, etc, like nginx does, but this is egregious.
Re:Announcing Caddy Commercial Licenses by snark42 on Wednesday September 13, 2017 @01:52PM (#15240745)
> Can you name an open source project that does not offer extended features for commercial versions and that sells?

pfSense, Ceph (prior to RH purchase) and OpenNebula off the top of my head.

Re:Announcing Caddy Commercial Licenses by tiernano on Wednesday September 13, 2017 @04:05PM (#15242075)
Pfsense does have commercial offering though netgate...
Re:Announcing Caddy Commercial Licenses by detaro on Wednesday September 13, 2017 @04:09PM (#15242115)
Netgate sells service, hardware and certification, not extra features.
Re:Announcing Caddy Commercial Licenses by tiernano on Wednesday September 13, 2017 @05:21PM (#15242812)
Doesn’t gold membership include extra features?
Re:Announcing Caddy Commercial Licenses by detaro on Wednesday September 13, 2017 @11:31PM (#15244798)
Looking at it again, it seems their cloud configuration backup service has special client code and could qualify as such. But the primary thing seems to be access to information, the devs and an officially certified VM for AWS.
Re:Announcing Caddy Commercial Licenses by StavrosK on Wednesday September 13, 2017 @10:34AM (#15238639)
Ad headers isn't an extended feature, it's a nag screen.
Re:Announcing Caddy Commercial Licenses by bauerd on Wednesday September 13, 2017 @10:37AM (#15238675)
Removal of ad headers surely counts as a feature then?
Re:Announcing Caddy Commercial Licenses by StavrosK on Wednesday September 13, 2017 @11:07AM (#15238934)
No, it counts as a bugfix.
Re:Announcing Caddy Commercial Licenses by andkenneth on Wednesday September 13, 2017 @10:15AM (#15238448)
I think the headers are there so they can see if commercial sites are using the personal version and get them to pony up.
Re:Announcing Caddy Commercial Licenses by jayrox on Wednesday September 13, 2017 @10:49AM (#15238792)
commercial sites have the easy ability to go to https://github.com/mholt/caddy; download the source; remove the header from header.go and server.go; compile; run

i'd venture to guess many build the binary themselves already. so they can add their own tweaks.

how would anyone be able to prove a website is being ran by caddy if the server doesn't announce that it is caddy?

Re:Announcing Caddy Commercial Licenses by detaro on Wednesday September 13, 2017 @11:19AM (#15239064)
If you do build it yourself, you don't fall under the commercial license, so it's correct if those are not detected.
Re:Announcing Caddy Commercial Licenses by nopzor on Wednesday September 13, 2017 @10:43AM (#15238731)
Wouldn't they already know who their customers are?
Re:Announcing Caddy Commercial Licenses by underyx on Wednesday September 13, 2017 @10:17AM (#15238473)
It's enough if nobody but the site maintainers will see them, that's what can annoy them into upgrading.