It was *NEVER* about shortcuts. Someone else made that up. Prly same people who also arranged for some guy to insist I drive my car directly behind him through security "[..] because there was something wrong with [some parking issue]".
I didn't fork the library. Another group did. I did a lot of work, because the library was neglected and there previously were other reported issues that went unresolved. You didn't want a functioning library, it's open; you wanted to steal my work and effort.
This isn't about "shortcuts". I did the work already, in the timespan of the last 10 years. You can read the discussions online ffs.
Let me be clear: Ola and Sofia did not do any work on otr4j at https://github.com/otr4j/otr4j repo that I worked on. I caught up with the spec a bit after their Draft 3, meaning that things were also becoming more solid. And provided feedback on practical matters and theoretical oversights, because I had an implementation to compare against and I read pedantically to ..
.. to ensure that no inaccuracies slipped through the cracks that would cause confusion for anyone not familiar enough with the theory and/or specifics.
The whole point of the spec is that the hightly theoretical aspects are solidified/established, such that you don't have to be an expert in every field at once.
Not one human will be able to explain the complete functioning of a laptop, yet you all operate one.
They *claimed to* have the expertise in defining the protocol. I have experience in software engineering. I learned their domain because I find it interesting. I learned a lot and I always said so. There is *NO* reason to attack me, when I did the work already, showed the results already and never representedn the circumstances in the first place.
The repo got forked by the GuardianProject guys who wanted to make this a collaborative effort. But it immediately died out because most independent devs hosting a clone of otr4j didn't want to be involved. When I started making more radical changes, I suspect GuardianProject guys didn't want to put in all the effort reviewing so I eventually did the massive refactoring followed by OTRv4 implementation by myself. (I checked with @eighthave a few days ago on a few matters but he didn't respond.)
@eighthave From the perspective of the GP guys, it makes complete sense. They had plenty of other projects in flight, and for them I'm the loose canon whose every step they'd need to review. So when I continued as single dev, I could make the changes that could otherwise never have happened.
@eighthave same old, I have been under attack by a legion of people who attack me for stealing the otr4j and having done no work. That's by no means the only false accusation. Apparently I have been under attack for the last 10 years, including at my professional workplace, which I documented on recently.
However, for this specific instance, I'm trying to explain that I did the work on otr4j, both refactoring and OTRv4 work.