This is to announce and explain that we’re slightly modifying the relationship between syncthing and Ind.ie. You may recall that I announced that syncthing was going to be renamed Pulse and live under the stewardship of Ind.ie, almost exactly a month ago. This isn’t happening, at least not right now and not exactly in this manner. Syncthing is going to remain syncthing.
The reason for this is personal. I, in the position of lead developer, have felt that the fit between me an Ind.ie isn’t really what I thought it was. Ind.ie has taken on a fight against the currently ruling business and privacy models, and this is a fight I support. Many others support it too as we can see from the currently ongoing funding drive, and I wish Ind.ie nothing but success. But it’s also a fight that I don’t have the energy or will to be an active part of. Having syncthing be a cornerstone in this fight would make that involvment unavoidable, so in the end it would mean either withdrawing myself from syncthing or disassociating syncthing from Ind.ie. I chose the latter.
Obviously announcing one thing and then reverting it and doing something else looks bad; both for myself and for Ind.ie. Sorry, Ind.ie! But I believe in this project, the initial decision I made unfortunately wasn’t fully thought through, and I believe in correcting mistakes and moving on.
Ind.ie is going to do their thing and may indeed maintain and release a fork of syncthing under the name Pulse. They have my blessing to do so - if that is what happens, it isn’t a hostile fork. I think projects should be free to move in the direction they need to, and it’s quite likely that Ind.ie will want different features and optimizations for Pulse than we need in syncthing. On the other hand, it’s also likely that a bunch of stuff would be common and the advantages mutual. Only time will tell what happens here.