One sore point there is that the code comes by default with a donation link (the heart at the top) to join-lemmy.org. Even without the tankie issue it should rather go to a page local to the instance explaining donation options, and the default should be “The admin didn’t set this up, if you urgently need to get rid of money here’s a link to Doctors without Borders”.
OTOH there’s now a huge influx of people including tons of developers so I expect tankie influence to be drowned out sooner than later.
A bunch of developers isn’t going to do anything though if they retain control over everything. I think after learning about this background, and their weird claims surrounding it yesterday, the path forward I would prefer is for a strong fork to emerge of the original code that instances deploy instead.
I prophesied that to happen back on reddit but with FLOSS development culture being as it is pre-emptive forking is kinda considered the same as a pre-emptive nuclear strike. It’s just not done.
I’m about 100% that there’s going to come a make-or break situation where, if the developers don’t concede, there will be a fork, but it could also be that the devs are conscious enough of what’s happening that they’ll cave under the pressure and thus manage to retain some influence over the project.
One sore point there is that the code comes by default with a donation link (the heart at the top) to join-lemmy.org. Even without the tankie issue it should rather go to a page local to the instance explaining donation options, and the default should be “The admin didn’t set this up, if you urgently need to get rid of money here’s a link to Doctors without Borders”.
OTOH there’s now a huge influx of people including tons of developers so I expect tankie influence to be drowned out sooner than later.
Yeah, developers of new instances should probably edit that out.
I don’t think its a huge issue though, looking at that page the number of people who have donated more than $10 is like… a dozen.
A bunch of developers isn’t going to do anything though if they retain control over everything. I think after learning about this background, and their weird claims surrounding it yesterday, the path forward I would prefer is for a strong fork to emerge of the original code that instances deploy instead.
I prophesied that to happen back on reddit but with FLOSS development culture being as it is pre-emptive forking is kinda considered the same as a pre-emptive nuclear strike. It’s just not done.
I’m about 100% that there’s going to come a make-or break situation where, if the developers don’t concede, there will be a fork, but it could also be that the devs are conscious enough of what’s happening that they’ll cave under the pressure and thus manage to retain some influence over the project.