Working on DayJob code, I noticed how one file is like nearly 3,000 lines. Now for my own projects, I have this "thing" where I'm reaching nearly a thousand lines of code (including comments) that I feel compelled to move it into another file. That's if I notice it. I barely do nowadays but when I do, I'm always a bit shocked—for no particular reason outside “wow, that's a lot of lines”.
This kind of makes me want to keep track of this for no other reason outside curiosity. I wonder if this is something I should put in my editor as a plugin (to collect these numbers and then throw it into SQLite for number crunching later.
Need to use this for my site's color palette. https://www.youtube.com/watch?v=UWwNIMHFdW4. Might rewrite a recap for research and reference.
Manton has a book that's available online and as print at https://book.micro.blog/. Been reading https://book.micro.blog/interview-tantek-aaron/ and noticing a lot of things that are cyclic when it comes to the IndieWeb space.
Namely, getting from “I need a Website to be on the IndieWeb” to “I use this as my presence online”. Hosting is a solved problem, but it requires quite a bit of investment up front and the funds to hold down things for people. I still think we require some sort of “linting” tool for sites to make sure they at least allow for some baseline discovery and interoperability. Angelo's working on something like this but not completely. I might end up doing this to help people onboard when they use Lwa but it'd also help to explain what can get you into an app before using it. Or at least interoperating with other sites and apps. A bit of the XMPP problem, but at least there's a registry and a way to check your implementation for support via https://compliance.conversations.im/.
All this time, my representative h-card was missing a link back to itself to prove that .. it was the representative h-card. Marty said something in the chat that I can't find but some sort of "MF2 linting" for post type discovery is definitely needed (and I can see such a tool making the lives of newcomers and experienced people alike a lot easier).
Made lots of changes to my site's parts this evening. Most of it is to lean more on protocols to get me what I need. Eventually, this site would essentially become a feed renderer of the content I store in my Micropub server (and other places). Very exciting.
Definitely need to figure out this bug that's happening when I try to hit some parts of the p3k suite of tools. That's no good. But also subtle incentive for me to work on my own implementations!
Made lots of changes to my site's parts this evening. Most of it is to lean more on protocols to get me what I need. Eventually, this site would essentially become a feed renderer of the content I store in my Micropub server (and other places). Very exciting.
It's probably going to take me a long time, but I do want to import the stuff from my older site's implementation into this current one. I still have it, I just haven't made it compatible with this one. It's mainly JSON, though.
A next step is to have my theme 'auto-deploy' to my site. I think I'll have to write a custom script for this and have a token that has the ability to push it for now. Adding that functionality to Shock directly would require a bit too much work right now.
Working with Micropublish is making me realize that I need to do a bit of HTML sanitization when I get HTML content. It wrapped the article's HTML in a div tag and that broke my layout a bit.
I'm always curious about ways of using SQLite in a distributed fashion but not like how we currently do distributed databases. I'm thinking more like "file sharing" distributed. I've also abstracted a lot of the I/O for my site — my long term hope is to be able to "pack" the data for it in a 'portable' (torrenting) way, so I can modify it from any device that's familiar with the filesystem layout and the database schema. This would effectively put the data in the hands of clients that are permitted access to it. This is how something like inkandswitch's Local First Software could be used for personal sites.
Also, having the generator and syndication information populate at a later time is nice. I think it's the same for Webmentions when they're sent. I might just need to make a log view of actions/jobs for Koype so I can see what happens when.
Might need another channel called "pages" so I don't have things just float up there whenever I make a standalone page on my site.
As I was walking Stella, I was thinking about how I want to make sure that the things that I write are either as accessible as possible or I can link out and give enough context to help the reader. I wrote down a ticket for my site's theme and added a ticket to implement the editor aspect in Lwa. That'll be fun to implement!