Scroll to top

09/06/2021


2021/06/09#p1

6 comments: click to read or leave your own

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.

avatar
devilgate says: Reply to devilgate

@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?

avatar
colinwalker says: Reply to colinwalker

@devilgate I think there's a difference between fixing problems and probably needing to rewrite almist the whole thing πŸ˜‚

avatar
hjertnes says: Reply to hjertnes

@colinwalker why would you have to update two code bases?

avatar
Colin Walker replied:

There's my own version (which includes the personal journal and the muse-letter) and the other version which excludes these.

avatar
hjertnes says: Reply to hjertnes

@colinwalker Ahh. My CMS will not be open sourced either. Mostly because it is just made to work for me and my needs

avatar
devilgate says: Reply to devilgate

@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.

Leave a reply



You can also:

Click here to reply using email Reply by email Send a webmention Send a Webmention



2021/06/09#p2

0 comments: click to leave a comment

I couldn't resist and installed MacOS Monterey beta 1 on the MacBook Air – I'm holding off until at least the public beta for the MBP.

As promised, the first time you open the mail app you are prompted if you want to enable 'Mail Privacy Protection' – it's immediately in your face which is nice and I can imagine most people will choose to enable it, just like the App Tracking on iOS.

I've not had much of a chance to look at Shortcuts but a couple of tests of old shortcuts from when I had the iPhone X weren't working due to issues with picking images, I'll likely need to rework them.

I'm enjoying the update to Safari and the first thing that immediately jumps out at you is that it now supports the 'theme-color' meta tag. It's about time!

Safari theme-color support

No comments yet
Leave a reply



You can also:

Click here to reply using email Reply by email Send a webmention Send a Webmention



Close