Subconsciously, I think I decided a while ago not to make (b)log-In publicly available β that decision has finally percolated through to the conscious.
One reason is that I don't have the energy to update two separate codebases and keep track of what should go where. The main justification (if we can call it that) is it is such a personal and personalised platform that it is likely to annoy/frustrate others. (b)log-In is built specifically for my needs β yes, functionality has been introduced that would better cater to others, but I don't feel it's enough.
Then there's the state of the code. I'm willing to take the risk with it but know it's strictly amateur hour. It's basic, inefficient and, no doubt, poorly written; mistakes will have been made with no real understanding of why or how to resolve them. It's great being able to build something like this and have it working but my knowledge is limited.
Maybe this will change in future, maybe I'll learn more and have greater confidence in what I've built, but I think it would need almost a full rewrite before I get to that point.
@colinwalker Of course, one advantage of opening it up can be that other people pitch and fix the problems. But then you might end up managing a team of developers, and who wants to do that?
@devilgate I think there's a difference between fixing problems and probably needing to rewrite almist the whole thing π
@colinwalker why would you have to update two code bases?
There's my own version (which includes the personal journal and the muse-letter) and the other version which excludes these.
@colinwalker Ahh. My CMS will not be open sourced either. Mostly because it is just made to work for me and my needs
@colinwalker Yeah, I can see that; but remember, we tend to be most critical of our own work. It may not be as bad as you think.