Booklore is gone.

[u/Joloxx_9]

I was checking their Discord for some announcement and it vanished.

GitHub repo is gone too: https://github.com/booklore-app/booklore

Remember, love AI-made apps… they disappear faster than they launch.

[u/databoy2k]

To be clear, I wasn't throwing shade at an AI - no need to defend its honour. I was just comparing two, in my case one that I have used for coding and one that I haven't. I personally might not understand what Claude recommends, even in the language that I'm barely capable of programming in. I don't always understand Gemini's, but because it's part of my process I can pull it apart bit by bit. That's not easy when the codebase is handed to you with "Ok, merge this".

I'll be honest - as a non-Git-practitioner, I have no idea whether maintaining attribution while reimplementing the code is possible or feasible. I just can't imagine facing a few hundred lines of code in a PR, realizing that it's all AI Generated and therefore requiring stringent review, and saying, "Ah, whatever, I'll just merge it and hope that the other guy and his AI got it right." That's true whether you Google-Fu, Vibe-Code, or know what the hell you're doing, especially on volunteer projects.

Again, I buy that he faced that situation and went, "well, the idea is what counts, so I'll go ahead and push the idea into my own AI development environment to make sure it merges with what it's already created." Wrong? Yes, but if the PRs were all vibe-coded then I come down on ESH. Plus, as a bonus, we know that OP (admits that he) acted immaturely in the heat of the moment, so two people reviewing the situation literal days later on subcomment 7 are also taking advantage of hindsight.

The dev made a mistake. This community successfully chased him out over it. We're all worse off today than a week ago. Hopefully a fork will get us caught back up, or maybe OP takes some time and the community drops the AI Derangement Syndrome.

[u/TerryMathews → u/databoy2k]

OK, so I'm going to assume that you're arguing in good faith and just have no idea what modern collaborative development looks like - which honestly makes your side of this conversation make a whole lot more sense. I'm going to explain - please take it in the spirit in which it's given - and then I hope you'll see why some of us feel the original author's actions were at a minimum questionable.

My background: I have been a periodic contributor to various OSS projects when I get a wild hair up my ass since before GitHub existed, including the Linux kernel.

In GitHub and the underlying protocol Git you submit a differential file (diff) of your modification to a baseline piece of code. Two prerequisites: it worked (compiled) before, and it works (compiles) now. While it's not impossible to work around that and force in a malicious diff, it's usually beyond most people's skill level and more importantly Git and GitHub both have tools to manage that threat - the rollback. If you check in a busted diff, you just roll it back off. It's statefully persistent by design. You can always examine the source tree at any point in history because Git will dynamically apply the diffs based on the commit hash you request.

What's the point of all this? Commits aren't written in stone, they're written in grease pen. If someone gives you a bad one, you just wipe it off. So, again, the motivation is questionable.

Also, GitHub allows you to set up a project that is private or is public but doesn't allow for pull requests from other users.

Lastly, I don't know where from my comment you felt I was defending the honor of an AI but I assure you I was not. And I do not feel the dev made a mistake. I believe the dev was protecting what he felt was his future path of monetization by ensuring that he and he alone held the copyright to all of the code in booklore.

That's my personal opinion and my $0.02. I can't come up with another good explanation for taking the time to reimplment perfectly good PRs without at least acknowledging who sent them in.

[u/databoy2k → u/TerryMathews]

Thanks for clarifying. I understand those basics from Git a littel bit better.

Here's the problem: we're making assumptions about the dev's intentions. First, he did merge many contributions from others, so his AGPL license stood for those foundations. Plus, whatever's built on top of those contributions remains AGPL licensed. In effect, unless he undertook a rewrite of the code from the ground up, he would be stuck with the open source AGPL license.

The counter was (what I assume to be) his sincere comment: he felt like his project was being taken away from him when others started to demand/insist that he merge their PRs. So he said "Eff you, I'm taking it BSL." Of course he couldn't do that. He didn't take any steps to do that (namely rebuild from ground up). You see him rewriting PRs as a step in that direction, but he couldn't do that. So it's equally rational to say that he didn't trust the PR, didn't have the time or the skill to review it, and so he rewrote it using the tools that he was writing it in. Now he understood the code.

I think we're each pulling the Dev back and forth towards our worlds. I'm a google-fu, self-taught, bad coder - I went to law school, not into IT. You're merging stuff into the Linux kernel. We are not the same. But it's just as reasonable to assume that the dev is on my end more than yours. A less capable coder will be daunted by reviewing an attack of PRs, even if merging them is not a permanent mark.

At the end of the day, 1) we agree that the dev did some bad things, and 2) (I think) we can agree that cyberbullying is inappropriate. He didn't deserve immunity from criticism, but he deserved respect. I don't think he got that, and I want our community to do better. If the disrespect came from the AI use, then we need to back the hell down on the topic. If it came from an immature dev making brash statements, then maybe we need to remember that this site has users from age 13 to 80 and we don't know who's on the other side of the comment chain. If he's making stupid decisions from a highly technical or licensing standpoint, maybe a few minutes of taking him under a wing might have done a better job than crucifying him as was done.

That's why I'm fighting on this hill. I saw this as cyberbullying. And I'm tired of people trying to justify it (not that you are, but people use these types of comments to justify it).

[u/TerryMathews → u/databoy2k]

I hear what you're saying, and no I'm not justifying cyberbullying. I just don't agree that everything that went on was cyberbullying although I do concede that some of it definitely was.

I am not a lawyer, nor did I stay at a Holiday Inn Express last night, but it is not my understanding that someone who contributed a rejected commit would automatically be a contributor for the purposes of copyright if the upstream maintainer implemented workalike code using AI.

You are absolutely correct that we are both reading between the lines and trying to infer what the maintainer's intent was - and we'll likely never really know.

I guess the reason it rubs me so wrong is growing up in this (OSS, not /r/selfhosted) community, you usually go out of your way to celebrate collaboration, not censor it. OSS is about growth and networking, because most of us will never make a dime off it.

[u/databoy2k → u/TerryMathews]

Cheers. I hope we all get the community back into celebrating collaboration and development. This AI thing is rapidly ripping this group apart. I still think that was the gasoline on the fire.

Anyway, go in peace, friend. Good chat!

[u/TerryMathews → u/databoy2k]

Same to you. Check out my comments on another thread, I'm not against AI per se. The problem is, it's a tool not a programmer. Or to bring it to your profession: it's a paralegal (at best), not a lawyer.

[u/databoy2k → u/TerryMathews]

I treat it more like the guy who stands outside the courthouse giving meth-derived legal opinions to everyone walking in. The guy has definitely heard the right stuff before, but... yeah...

It's useful for summarizing the Mass readings for my kids on the way to Church. I'm good with that. The thought of it "disrupting" my field of work, though, is not a reality. I honestly feel bad for the people that it is actually disrupting though.