Put a Fork in Caddy; It's Done

#1

Post by neflabs » Mon, Apr 30, 2018, 2:10 PM UTC

Put a Fork in Caddy; It's Done
neflabs.com

Re: Put a Fork in Caddy; It's Done

#2

Post by rrdharan » Mon, Apr 30, 2018, 2:38 PM UTC

The original announcement is here: https://caddyserver.com/blog/caddy-0_11-telemetry

And forum discussion here: https://caddy.community/t/caddy-0-11-will-have-telemetry-dis...

I thought some of the ideas in the "middle ground" section discussing opt-in versus opt-out being the default depending on how you obtained the software were sort of interesting, hadn't heard that compromise suggested before.

Re: Put a Fork in Caddy; It's Done

#3

Post by dsissitka » Mon, Apr 30, 2018, 2:41 PM UTC

Mirror: https://web.archive.org/web/20180430141629/https://neflabs.c...

Re: Put a Fork in Caddy; It's Done

#4

Post by conradk » Mon, Apr 30, 2018, 2:41 PM UTC

It's amazing the lack of gratefulness some people have for open source devs. Matt Holt, which I don't know nor have ever met, has spend a tremendous amount of time developing Caddy and making it available for free. It's creating a lot of value, regardless of what you think of recent telemetry announcements.

And still, apparently, some people will use the slightest disagreement to say that the whole project is garbage, just like this article is doing. I think we're lucky that open source developers don't get deterred by these kinds of article, because they sure could be. What does religion have to do with the quality of a free software project ? Does your server run better if coded by an atheist ?

Instead of being disdainful, a more constructive thing to do would be to openly talk about forking, on Caddy's forum, and see the response. If nothing changes, fork and convince people that your fork is better.

Re: Put a Fork in Caddy; It's Done

#5

Post by Touche » Mon, Apr 30, 2018, 2:42 PM UTC

I sort of agree with this post but not for the reasons given. That developer doesn't want a negative video posted to his forum is not a big problem to me.

The reason I left Caddy was that it just didn't feel that stable to me. By that I don't mean that there are bugs, just that he keeps changing things. A web server is not something I want to have breaking changes all of the time. I want to deploy it and leave it alone; only upgrade for security patches. So I've decided to switch to AWS.

Re: Put a Fork in Caddy; It's Done

#6

Post by rrdharan » Mon, Apr 30, 2018, 2:42 PM UTC

rrdharan wrote: post #2

The original announcement is here: https://caddyserver.com/blog/caddy-0_11-telemetry And forum discussion here: https://caddy.community/t/caddy-0-11-will-have-telemetry-dis... I thought some of the ideas in the "middle ground" section discussing opt-in versus opt-out being the default depending on how you obtained the software were sort of interesting, hadn't heard that compromise suggested before.

Skimming through that discussion, it seems like the developer is also somewhat naively optimistic and possibly underinformed regarding how much of his own and his customers/users' effort will be required to comply with the GDPR while gathering this data.

Re: Put a Fork in Caddy; It's Done

#7

Post by eklavya » Mon, Apr 30, 2018, 2:43 PM UTC

From the caddy blog post, I can’t seem to find any objectionable behaviour. What are you the objections if any?

Re: Put a Fork in Caddy; It's Done

#8

Post by jamespo » Mon, Apr 30, 2018, 2:43 PM UTC

Article timed out for me, seems neflabs needs new webserver software.

Re: Put a Fork in Caddy; It's Done

#9

Post by stevekemp » Mon, Apr 30, 2018, 2:43 PM UTC

I can't reach the site to read the post, but it seems that Caddy has been plagued with controvosy/drama as they tried to monetise their project - as past discussion here shows:

https://news.ycombinator.com/item?id=15237923

It's a nice-looking project, and the integrated Let's Encrypt is great for non-sophisticated users, but the user-base must be suffering.

Re: Put a Fork in Caddy; It's Done

#10

Post by pmlnr » Mon, Apr 30, 2018, 2:44 PM UTC

conradk wrote: post #4

It's amazing the lack of gratefulness some people have for open source devs. Matt Holt, which I don't know nor have ever met, has spend a tremendous amount of time developing Caddy and making it available for free. It's creating a lot of value, regardless of what you think of recent telemetry announcements. And still, apparently, some people will use the slightest disagreement to say that the whole project is garbage…

Being able to fork in case of disagreements is a feature of open source, not a bug.

Some of these forks get re-merged a few years later (see ffmpeg), others don't, but this is not bad at all.

The ideal solution would be to build Caddy with flags that disable telemetry, just like Firefox is built for Debian.