TDLR Continuing building multi stage system. Hours 8 Nerd Created and chose a mono repo. Ensured that the Darwin Build script works correctly. However there is a module packaging error and I need to fix that before I go into building the remaining build script. I also setup and began troubleshooting the windows build issue which is super exciting. I had to install both wine and mono. Both runtimes for windows on a Mac. This is because if I can build for all three on one plateform my job ...

TDLR Setup the Flutter language eco system. Hours 3 Nerd Installed XCode Installed Android Studio Installed Google Chrome Installed Flutter itself Useful links Flutter Code Lab List of forever TODO's How to handle downtime ...

TDLR Read about Electron, React Native and designed layered system and ultimately landed on Flutter. Hours 2 Nerd ┌────────────────────────────────────────────────┐ │ │ │ │ │ Dynamic UI │ │ Desktop, Minimal and Mobile │ │ │ │ ...

TDLR Began planning the goals and how the filesystem works. Hours 1 Nerd The filesystem utilizes 32 KiB chunked files along with a yet to be determined fixed header so that information can be transmitted in an appetizer - full meal concept. This saves on partial FS loading where only certain tree's of the FS are loaded. The client can then reject the appetizer and only have 'wasted' a small amount of data instead of silently dropping the entire thing. On This Day I was trying to setup ...

Total hours: 304 Top one: 1) I'm confused regarding what to do. I've made several critical mistakes and trying to make a product more complicated than it needed to be. I need a basic product and then can grow from there. Right now I just need to design the MVP and go from there. What is the MVP? Syncing browser history from each browser with each other. ...

Total hours: 294 (14 hours behind target, day 14/90) Top one: 1) Setup color and theme along with header and it translates perfectly between dark and light mode (including the SVG). ...

Total hours: 293 (13 hours behind target, day 13/90) Top two: 1) Design Webpage The static webpage design is finished as viewable at linkerd.app. I’m proud of it but it’s not where I wanted it to be. However other things demand my attention and I can’t spend more time on this one. I’ve begun spending my time on Vue.JS and learning the basics of this again. 2) Financial Update I’ve overrun my financial limits and for the next few months will need to aggressively save in order to recover. So...

Total hours: 290 (12 hours behind target, day 11/90) Top three: 1) Hugo I tried but it wasn’t worth it, the theme design was too complicated for what I was trying to do and it was seemed to be more geared towards blogs which this isn’t at all. 2) Static Website Woes I’m using an advanced version of Mac OS (Because the Stage Manager feature is killer for deep work). However it’s caused alot of issues with brew and hence even installing Jeykell (I’m worried that I misspelled it but you know ...

Total hours: 286 (12 hours behind target, day 9/90) Top one: 1) Replanning Realized that I was merging three seperate parts into one confusing mess. Had to take a step back and begin earnest replanning the design and construction of this application. ...

Total hours: *286 (10 hours behind target, day 8/90) * Top one: 1) Replanning I need to slow down and breathe. I can’t go into this completely blind. I need to slow down and stop panicking. I’m not in my element. But I have the capability to learn and I need to utilize that and stop spaghetti coding. I’m trying to build a secure system which involves the precise working of multiple systems. I need to focus small and then grow from there. ...

Total hours: 285 (9 hours behind target, day 7/90) Top one: 1) Elixir Learning Reading and understanding how Elixir Plugs work. ...

Total hours: 185 (7 hours behind target, day 6/90) Top three: 1) Elixir Struggling I don’t understand enough about the complexities and 2) Ecto and Changeset I’m struggling with using this and my code is really really convoluted. This is because I’m trying to apply an OOP way of thinking to a functional way of programming. It’s completely different way of thinking and something that I just need to work on adjusting to. I know I can do it it’s just taking more time than I was hoping or expec...

Total hours: 283 (7 hours behind target, day 5/90) Top three: 1) Financial update to get ElixirCast.io course I need to know what I’m doing and need to lean wholeheartedly into resources that will assist me in this. Sapphire Pack has funds for this and therefore I should be using them. 2) Got primitive login screen working It’s good for creating a new account but upon an error of some kind it shows the password hash which is a major bug and reveals an internal implementation details which i...

Total hours: 282 (6 hours behind target, day 4/90) Top three: 1) Xcode Utilities setup and troubleshoot on Beta version of iOS This actually took alot of time to setup because alot of code attempted to say just ‘Xcode --install’ but it kept reporting Error unable to install Beta software. Extremely frustrating but eventually I was able to install it using an obscure link to apple.com software beta repo which isn’t available from official but as a standalone which was super confusing. 2) P...

Total hours: 279 Top three: 1) Elixir Learning Learning about Elixir and how Agents work within the Elixir ecosystem. 2) Project creep Discovering that the scope of the project had been creeping outwards in a way that wasn’t intended nor wanted at all. 3) Design failure Part of the project creep. ...

Total hours: 274 Top three: 1) Learning Elixir Got the basic setup of scripting setting up. Understanding the flow operator. It’s absolutely powerful and makes the code super easy to read. |> I love this little thing. 2) CurrentR continue designing 3) Got website setup with integration using CD ...

otal hours: 271 Top three: 1) Elixir Learning Beginning a sample project to pull data from Github and display as BEAUTIFUL tables. 2) Currentr Designing the overall UI, I’ve found that the R on the end of things is going to a staple. Current is like an oceans current (most of the libraries devolved for Linkerd) are going to be ocean themed. 3) Keyboard Practice I’ve upgraded to a modern keyboard setup. However this comes with a massive learning curve. Therefore the first hour I spent usi...

Total hours: 270 Top one: 1) Elixir Learning This was just raw experience and practicing. Starting with OTP and such. OTP is the open telecommunications platforms. ...

Total hours: 269 Top one: 1) Speed learning Elixir Structs, Maps and Dictionarys ...

Total hours: 268 Top three: 1) Biz rebranding plannings Planning to amalgamate Sapphire Pack and Gaya as one single entity. Just like Standard Notes and the company. ...

Total hours: 264.083 Top three: 1) Threat Scoping 2) Code Migration and git commit 3) Keyring Version 0 Partial development in place. ...

Total hours: 263.633 Top two: 1) Financial updating Managed to pull all my finances back together and see that I’m currently in a negative pit in terms of money. I’m able to float some over from personal funds. However massive cutbacks and changes are going to need to occur within the next 6 months otherwise Sapphire Pack could be facing financial ruin. 2) Gitlab purchase I ended up getting a premium subscription to Gitlab because I need more power when developing. Also the person that I’m ...

Total hours: 262.850 Top one: 1) Email cleanup ...

Total hours: 262.833 Top two: 1) iPhone checking Ensuring that the site works well on the iPhone. It’s obviously not at all close to the finished site at all. I just wanted to see that there was some semblance of it working. I wasn’t disappointed. 2) Design Reaffirmation Protector of Data Fierce but cute Protective Loyal Sassy Cute Fierce B+W minimalist ...

Total hours: 262.000 Top One: Collaborating with a designer for the logo and main character that the application embodies. ...

Total hours: 261.920 ...

Total hours: 261.917 Top three: 1) Documentation It’s important and not much more to share here. 2) Security Scoping I began reading and am tentatively understanding. Still alot more security scoping also goes by Threat Scoping. One of the things that I dislike is how alot of privacy centric applications are combative or outright refuse to work with governmental authorities. There needs to be a mix and some things hardcoded so that only the operator themselves can access the data. An idea...

Total hours: 261.367 Top three: 1) Documenting Security Protocol This is complicated because it depends on the level and the level also depends on other factors which I haven’t yet figured out. However I managed to sidestep most of the circular dependencies and concepts by ensuring that all accounts start at lax and can be upgraded or downgraded in the future. 2) Collapsing and pushing key management to a later task Key management and deployment is a very complex issue which is completely ...

Total hours: 260.150 Top one: 1) Key derivation and security design This is quite complicated because I’m having to address, attacks, rate limiting along with multiple concurrent attempts to upgrade, downgrade and migrate account security. The idea is to make downgrading harder so that in the event that an account is compromised their is limited damage. However that’s quite hard to do given the fact that that once the root key and keyring are released all of those files and information is d...

Total hours: 258.100 Top one: 1) Key generation and migration concept replan ...

Total hours: 258.017 Top three: 1) Key generation Using offline web application to generate system security systems. This is because JS is critical for the cryptographic generation. 2) Key Security and Wrapping 3) Financial update Updated financial information and reworked outline. Going to run aground within the next year unless I get income from the project. ...

Total hours: 255.800 Top one: 1) Email check ...

Total hours: 255.783 Top one: Key management design. This is quite tricky since there’s three levels of security. Not just one. To match privacy and security requirements of different people without fundamentally altering the base product. Rather the transmission and processing of the data only. ...

Total hours: 255.283 Top one: 1) WAPI API designing Uses token mapping to an operator on the server side. This ensures that I’m not exposing or providing direct access or reference to the database rows. ...

Total hours: 255.050 Top one: 1) WAPI design. WAPI is the Web API that is used while running an interactive session stemming from within the web browser. (In a way a loopback server). This allows critical processes to run like key generation, key migrations and such. Currently data security has been redesigned which has ripple effects thruout the entire architecture. The first and main one being that there are three seperate classes of security. The lax one is the one that I’m implementing r...

Total hours: 254.383 Top one: 1) Seeking design expert I’m designing a paper UI. I’m taking an unconventional approach in the software design that’ll pay off. However it means having to reduce some aspects as much as I can. One of those is UI. UI per device have different ‘rules’ and therefore implementing the ‘right’ UI per device is tricky, error prone and hard to ensure rolls out correctly to all the devices. However web browsers UI’s are nice because they can look like whatever because t...

Total hours: 254.333 Top three: 1) Auth0 Redesign I failed partially and the paper design is failing slowly. I tried adding in a new design and I completely failed. 2) Idempotent design for database Database now automatically migrates on first start of application. I’ve design a better setup that runs in the application start. ...

Total hours: 253.767 Top three: 1) Client side encryption design Still using Quokka to prototype. Need to encrypt key locally and then submit to the backend. It’s complicated but makes more sense than directly generating in the backend. This is because going forward there will be several layers of security options ranging from lax, to strict. Also because I wasn’t able to find a library suitable for Elixir or Phoenix. I don’t have enough understanding to implement or use a library implemen...

Total hours: 251.317 Top three: 1) Refactor database I’m getting alot better with the database and using Ecto. Joins are coming back and it’s becoming just natural for me now. 2) Notes and general cleanup I had to plan the upcoming sprint and setup targets. I’m slightly behind the current sprint. I only have 28 minutes behind the current ‘perfect’ target. 3) Key management design I’m using in browser, client side design since XChacha20-Poly1305 is done via JS using Libsodium. ...

Total hours: 249.167 Top three: 1) Ecto designing This is important to learn. While a slow working it’s absolutely worth learning. It’s quite powerful and I’m learning how Ecto provides a high level of security, abstraction and raw power!!! 2) Exploration of join Using Repo and Elixir. This allows grabbing the right data from the database the first time and not needing to do multiple unwanted queries. However needing to do an double query the first few iterations would be alright if absol...

Total hours: 148.000 Top three: 1) Database design for key management Currently the database design treated the operator and sign in as one identity. This way it’s easier to add further authentication and ensures that there’s multiple authentication vectors for an operator. Furthermore it’s a v shape. There’s authentication which points to an operator along with keys that point to an operator. This allows us to select the key that the operator has along with the authentication methods the o...

Gaya Total hours: 246.150 Top one: 1) Domain transfer succeeded. Sapphire Pack is now on the correct. However the blog isn’t currently correctly setup. It’s still correctly accessible at listed.to/@Gaya but I want it also accessible to blog.sapphirepack.org ...

Total hours: 246.100 ...

Total hours: 246.083 ...

Total hours: 246.000 Top three: 1) Authentication Split into three seperate levels to plan and design based on threat and security requirements instead of providing just one size fits all. Despite that being what I wanted from the get go and to design an application with 0 settings or close to 0. But really wanted 0 settings options. 2) Authorization This is different than than authentication. It’s designed to be a second layer of design for cautious or strict mode. 3) Key Management St...

Total hours: 245.650 ...

Total hours: 245.633 Top three: 1) Experimenting with Key Derivation This is tricky since it involves ensuring proper key provisioning while ensuring that Sapphire Pack has no access to your data at all. 2) Exploring Yubikey for security I like the concept because I’d be able to use a several key derivation concept and using asymmetrical keys to design. ECC p384 which is secure till past 2031 which is extremely important. 3) Financial feasibility of using Yubikey Not worth it at allx. Not...

Total hours: 244.750 Top three: 1) Website Migration 2) Email Migration 3) Security transition and e2e encrypted data. ...

Total hours: 243.650 Top two: 1) Authorization and Deployment Concept This is very tricky but partially depends on not having a properly design threat scoping concept. The idea is have access keys which are seperate from the account in the event of a compromised system nuke, and remove, The problem though is it’s impossible to have a secure E2E encryption without a key being stored somewhere (like the persons brain or hardware key). If it’s the first it’s adding the ‘just one more password...

Total hours: 243.150 Top three: 1) Planning goal for day 30 2) Reading Ecto 3) Planning website style and design ...

Total hours: 242.867 Top three: 1) Route redirection (Alpha versus not) Failed since I had completely forgotten that everything underneath the route /operator is actually just fully protected which is good but at the same time means that I failed to think out the idea fully. 2) Session drop versus clear When a session is dropped cookies aren’t set since they’re revoked. What I need instead is clear the session. Then since their’s a cookie I can put the correct flash there. It’s not funct...

Total hours: 241.433 Top one: 1) Planning redirection. It’s important in the early phase to have two seperate redirections. One for a unauthorized login/ provider failure and another if not enrolled within the Alpha program (which is currently closed to just me currently). ...

Total hours: 241.00 Top one: 1) Deployed operator locking so only certain operators can authenticate. ...

Total hours: 239.700 Top one: 1) Auth0 and linking into application along with testing deploy paths. (You’re now able to see the new paths and logging and logout). I’m now working on the next crucial part of authentication which is controlling how operators are tied in to the system. You see currently the only person is me. However shortly afterwards it’ll open up and I’ll have a dashboard so that I can see operators and then from there I can tie in the email and such. Code is just a monumen...

Total hours: 238.450 Top three: 1) Auth0 Logout Flow Design I’ve done a really good job and actually collapsed everything underneath one endpoint. I’ve moved away from user to operator. Operator is someone that controls something. A user is used. Gaya’s built from the ground up with a different but subtle mindset. This mindset is critical in ensuring the project remains for the operator and not for the user. I’m not here to manipulate, I’m here to create something that can help join things ...

Total hours: 235.633 Top one: 1) Setting up remote environment on Gitlab Nothing more. Quite frustrating mainly because I don’t know what I’m doing. However that’s how any learning starts. ...

Total hours: 235.583 Top three: 1) Planning the authentication login setup Not much to really discuss here in this vein. BUT I GOT ITTTTT!!! 2) Got Fly deploy working correctly!!! Okay so there are ARGS and ENV. ARGS are only used during the build process and ENV’s are used during the run process. What this means is that these must be passed into the Flyctl command like so. Also the docker file is modified to have ARG . This signals to Docker that if it can’t find this during build to rais...

Total hours: 234.583 Top two: 1) Environmental Madness I’m learning what environmental variables are embedded during build and what can be dynamically set. It looks like Dockerfile has access to a particular set and that we need another to actually work for the fly.io environment. I’ve tried setting environmental variables nearly everywhere and narrowed the issue to the Docker and Phoenix build time concepts. Tomorrow I should be able to iron it out!! 2) Reading Elixir Still working on und...

Total hours: 233.700 Top three: 1) Addressing Local Environmental Issue Turns out the lack of proper redirection is that environmental variable isn’t being properly picked up. I solved it for outside environment but for some reason, INTERNAL environment it’s not properly being picked up. That is the mygaya.day it’s coming up as empty. Completely empty, I’m not sure exactly how to troubleshoot this given that it’s running in a remote docker container but I’m confident that I’ll find a solution...

Total hours: 232.467 Top one: 1) Researching Auth0 Direction Very basic design. Nothing more to discuss really. I also flirted at device registration idea (but way further ahead). Just a basic idea right now. ...

Total hours: 232.267 Top three: 1) Integrating Auth0 Signin I got it working!!! It only took a few hours but I got it working before it stopped working 😢. 2) Auth0 Troubleshooting Redirection It’s mysteriously redirecting w/o the domain part which is extremely confusing and I’m not sure exactly what I’m doing wrong. The odd part is that I don’t think it’s a local issue (what I originally thought). Or an environmental issue because the environmental variables (when changed to ones that I ca...

Total hours: 223.700 Top one: 1) Troubleshooting Auth0 integration. Elixir and Phoenix not very easily setup so I’m having to take it slow. Absolutely possible but slower than I’d like. ...

Total hours: 226.600 Top three: 1) Google Social Provider Finally got it working!!! It was a snap after I got the API setup and the integration perfectly redirected to auth.mygaya.day!!!!! I’m sooo happy!!! This is something that has taken waaaay longer than I expected but I’m soo happy that I managed to get it working. Why do I have to jump thru all of these hoops?? It prevents a malicious redirection to another site to then capture the token and then redirect to the legitimate domain. So...

Total hours: 222.300 Top one: 1) Email. Dealing with a little bit of email. Unable to do any more today. ...

Gaya Total hours: 222.283 Top one: 1) Domain Issues I finally tracked down the culprit. It turns out social providers (like Google) require a custom API key and the demo one doesn’t work. This causes the linking to go to the main auth0 page which then relinks to the ‘auth0’ branded page (instead of my own domain). This lack of integrity means that I’ve finally (hopefully) found what is causing a mismatch and the dreaded ‘unexpected error occurred... you might have pressed the back button, to...

Total hours: 221.783 Top three: 1) YNAB and CIBC Matching Booked to get an offer I wasn’t aware of. An extra 400 would really do wonders for Sapphire Pack. 2) Updating Quickbooks with Amazon Mistake. I accidentally had an elastic IP address unattached and that ended up costing me 0.83 cents. That doesn’t sound like much but considering how critical and squeezed Sapphire Pack is. I can’t be wasting dollars on easily avoidable mistakes. 3) Off the books (kinda) But got a temporary Sapphire P...

Total hours: 221.483 Top three: 1) Auth0 Login CORS Issue When you’re running on an http local server. Certain required POST features don’t work (except kinda in Chrome for 2 minutes). I ended up using a proxy which kinda solved the issue (thank goodness Auth0 has phenomenal documentation). However I wasn’t able to solve it unfortunately. It turned out later that the issue is with using Custom pages w/ a custom domain. There needs to be some other code that’s changed. That’s an issue to fig...

Total hours: 219.783 Top one: 1) Attempting to fix DNS issue with mygaya.day No such luck. Traced it to perhaps a certificate issue but I’m not entirely sure anymore. Quite frustrating and unsure of what to do. ...

Total hours: 219.667 Top three: 1) Lightsail Configuring mygaya.day to point to the correct lightsail instance located in Montreal Quebec. Certificate generation was partially difficult but managed in the end. Certbot generates one format and you need to convert this to another format and put in specific places to allow an encrypted connection. 2) Certificate Generation See above. I finally got it working (kinda). The connection is encrypted but something is misconfigured because I can’t ...

Total hours: 218.0700 Top one: 1) Email processing again :( ...

Total hours: 218.054 Top one: 1) Explore tying in Ecto associations The issue with doing it post pushing is that after I figure out how to tie in Ecto associations. The issue is compounded because I’ve already pushed to remote a non functional version of Ecto association. What this means is that while the database connections ARE functional. There is NO Ecto associations at this time. So after I get Ecto associations working I’ll need to backtrack and compare the two schemas and derive a migr...

Total hours: 217.938 Top three: 1) Financial Planning Got things covered using Quickbooks. I ended up encoding all the financial exhaustion within YNAB because Quickbooks doesn’t provide the option of reoccurring transactions until I pay another 200 dollars (CAD) to upgrade. Even at this rate it doesn’t provide a good burndown visualizor of any kind. What’s most stressful is the realization that the ground is coming up fast the lack of knowledge of how much more money is needed to be invest...

Total hours: 216.800 Top one: Cleaning up email box and pivoting for finishing this first 10 days of sprint. ...

Total hours: 216.783 Top three: 1) Ecto implementation This took most of my day and I’m proud to say that I am ahead of schedule as of today. I could start using the system w/ it’s current configuration (Ecto would be severely stunted because some parts don’t line up all the way right, but it would work). Ecto is a beautiful way to interacting with the database that avoids some very common pitfalls like the N+1 queries, magic which causes your code to slow down the road along with not making...

Total hours: 212.567 Top three: 1) Ecto Begin Reading Ecto is the database/persistence layer which is extremely robust AND supports out of the box wonderful testing and other crucial capabilities including constraints, transformations and mappings. It’s extremely powerful for rolling back and forward changes which is crucial for Gaya in the event that bad code is deployed or an update needs to be rolled back. Depends on Elixir so I’m also reading up on Elixir. 2) Elixir Begin Reading Rea...

Total hours: 211.567 Top three: 1) Operator Table Setup This is important because the operator can access the account in more than one way going forward. For example Google, Facebook, Github etc... We need to be able to correctly link to the same operator each time. Furthermore the unique id per social authenticator is different so the table design needs to be robust enough to account for that without adding a million columns. I’ve settled on id, oID, provider and core for the providers tabl...

Total hours: 211.100 Top three: 1) DNS Records This all relates to (3) which I’m trying to achieve. However there’s an issue which is that I can’t have a null root domain (that is a domain that doesn’t have an A or AAAA record. A record points to an IPV4 address and an AAAA record points to an IPV6 address. From my extremely limited understandings CNAmes are built ontop of A records. So without an A or AAAA record the CName records while queryable throw the web browser for a loop since it’s ...

Gaya Total hours: 210.067 Top three: 1) Auth0 Beginning the setup along with ensuring that the dev pages are obvious as dev and not prod or staging. This ensures that we aren’t leaking credentials onto the wrong place or site. 2) Subdomain DNS complexity and having to setup the subdomain for development, staging and production (not yet set up since requires planning what’s hosting and where). 3) Repo I’ve done many different kinds of repos from mono repos that are plain to more advanc...

Gaya (DNS Issue and troubleshooting) Total hours: 209.050 Top three: 1) Digital Ocean Attempt for Wiki.js This was ultimately fruitless but I learned alot about DNS and ended up hitting an issue that’s extremely difficult to solve and a known Node issue with http.get and ERRConnection. I tried updated the DNS in several places (who knew that Ubuntu had soo many places that DNS was updated/cached?) The reason that I was needing to update the DNS was that Digital Ocean’s DNS servers weren’t...

Gaya Total hours: 204.900 Top one: 1) Exploring Cryptographic root key synchronization w/o revealing the key to the server operator. At this point I’m taking a hiatus and will be back later this month. ...

Gaya Total hours: 204.850 Top three: 1) Planning expectation of data revocation and networking This is still quick limited. At this point there is no escrow key setup. If an operator losses access to their devices there is no mechanism currently for recovery. This is because browser data is class 2. This is a decision that I stand firmly by because that data is extremely private. I don’t want the risk of it falling into bad hands. No hands except your own should be trusted for that. 2) Wi...

Gaya Total hours: 203.950 Top three: 1) Crypto threat and recovery model This is quite complicated. It’s difficult because any proposed solution that I come up with requires some kind of storage of keys to verify that the data hasn’t been tampered with. This in turn locks the data from being rekeyed which is an important requirement. Assuming data isn’t rekeyable or only partially rekeyable leaves certain threat vectors open. At this point I’ve settled for the idea that the individual devic...

Gaya Total hours: 201.917 Top three: 1) Google Authentication Flow This is not complicated but there were many ways to design this. Since it’s starting out first as a connection. The final design is quite simple yet extremely scalable. Each provider combined with a CID which is the complex Identification (think of as primary identifier for that provider). For twitter this would be their userID, for google the email address and so on. Each row of the table would point to a OID (operator ID)...

Gaya Total hours: 200.983 Top one: Inspecting Auth0 integration options for Gaya and applying for the startup biz options. Every cost saving measure that is not low quality but rather an investment into the future is absolutely worth it. ...

Gaya Total hours: 200.633 Top three: 1) Basic Sync Concept I got this done!!! I tested the main ways that synchronization can occur and have found there to be no possibility of a sync conflict. This is because for browsers history there is only one operation that can be done (delete it). So conflicts aren’t possible at all. I’ve designed it to ensure it’s privacy maximizing. When the operator deletes that page from the browser. The history and time are wiped out immediately from the databas...

Gaya Total hours: 199.200 Top three: 1) Browser Sync This is now the MVP. I’ll be implementing it over a simple API system that is size limited along with ensuring that the server never actually sees the pages viewed by the client. This is yet to be figured out but requires some advanced crypto design along with atypical syncing concept. The reason is that when an operator deletes something from a browser it should be wiped out as much as possible, after a successful sync to the server. Tha...

Gaya Total hours: 197.717 Top three: 1) Ported SPacket Documentation I realized that I needed to get a MVP out there and then I could work on slowly adding in 2SSL. It’s an advance protocol and while it would have it’s benefits at current it’s outweighed by the complexity and requirement to implement complicated event based code in multiple languages simultaneously. 2) Browser Sync Planning How to synchronize browsers between devices of different brands. Much more complicated than it seems...

Gaya Total hours:195.800 Top three: 1) Quickbooks Setup I’ve setup Quickbooks and had a massive horrible feeling. I’ve made no progress at all. None really. I haven’t budged one inch forward. The protocol that I am working on at 2SSL doesn’t provide any value directly to the consumer nor provide long term benefit to Sapphire Pack. When I’m looking at money and net income and where I’ll start and begin having. Okay it does provide value but the question is the value provided worth the hassl...

Gaya Total hours: 193.817 Top two: 1) Financial Setup The bank I'm at is wonderfully helpful when you're first setting up and then BAM they tend to disappear otherwise. It's frustrating to deal with them but it's what I need. The bigger banks are in a better position to help a biz grow then a smaller credit union. 2) Landing Pad Redesign A landing pad is a unique UUID that maps a physical file being transferred from one or more devices to a specific target. Sine 2SSL is blocked based...

Gaya Total hours: 193.283 Top one: 1) File transmission protocol. Unlike other protocols this is the first one that is block oriented. Giving almost limitless and effortlessly parallel along with multi agent collaborative transfer and retransmission of data. At the protocol level everything is either a ‘command’ or a ‘block’. There isn’t any other kind of SPacket. The main issue is currently the 1MiB fixed packet size which is chosen because it provides extremely well setup storage and easy ...

Gaya Total hours: 193.033 Top three: 1) Files Storage It’s not a cloud storage provider, it’s a new way of synchronizing information instead of files. This makes it hundreds of times more complex because we’re not blindly syncing files but rather we have to understand the information, context and why it’s likely there and translate it and provide access in the correct context across all the operators devices. 2) Backup Consideration Gaya won’t be responsible for backing up data. It shouldn...

Gaya Total hours:192.917 Top three: 1) File Distributed Remote Storage Port to Wiki Important concept which dealt with UUID allocation, event emission and the lifecycle. However conflicted with several other issues and concept and designed way earlier on during the design of Gaya. 2) File Transmission Port to Wiki I realized that I was mixing a lot of complicated transmission of files into the 2SSL protocol. So at a later date I’ve vowed to separate the file transmission from the 2SSL libr...

Gaya Total hours: 191.367 Top three: 1) Azure Attempt Attempting to integrate azure search because I wasn’t able to find a basic piece of information. In hindsight I got distracted and need to focus on full wiki migration before worrying about infrastructure improvements. Azure is quite complicated and seems to just hold onto the credit card like a leach. At this point I’ll be cancelling it in full in the coming days. 2) Agolia Attempt Part of distracted and tried to integrate better se...

Gaya Total hours: 190.600 Top three: 1) Wiki Migration This is actually more complicated because there are a lot of ideas that need to be reslotted and massaged. Understanding the architectural differencences and massive issues with accepting or not accepting an idea. 2) Files This is an important concept that is also based heavily on amazon file storage of hot, cold and frozen. The terms are changed in terms of download/permenance. Hot is file that is never actually stored to the dis...

Gaya Total hours: 190.233 Top three: 1) Ephemeral Files, Queue Pumping Abstractions. To make high level 2SSL simpler and more reusable on server and client. 2) Website Basic sapphirepack.org website redone. Extremely extremely simple operation. 3) Wiki Migration Stuck on the paper to code migration trying to understanding the sticking points and interrelated issues and how architecture is changed. ...

Gaya Total hours: 189.00 Top three: 1) Finished 2SSL virgin connection protocol 2) Setting up website 3) Migrating paper notes ...

Gaya Total hours: 186.100 Top three: 1) Authentication Flow Since I'll be using an identity provider I need some way to tie the 2SSL session to the social provider so that a revocation from social provider will revoke immediately on server side which will then revoke on clients device shortly afterwards. Furthermore dealing with long term identity verification along with bridging and passing data from browser to desktop or mobile application. 2) Wiki Migration This was overdue including...

Gaya Total hours: 182.933 Top three: 1) Banking Setup This took way longer than I hoped and I’m still without the credit card part. 2) Legal TOS Began planning and trying to understand what protections and at what levels we’ll offer. A ‘just trust us’ mentality while nice doesn’t do much for 3rd party snooping. 3) Financial planning Since the company is facing a steep startup cost in which for the first several years no income will occur, I need to minimize as much as is possible the ...

Gaya Total hours: 180.067 Top three: 1) Executable Class Design This is designed as a wrapper and creator class that enables both the Task and Dispatcher thread to be more abstract and hide complexity and mapping issues. 2) Banking and Biz Research Currently acquiring CC at the current bank isn’t worth the hassle. I’m requiring CC in order to purchase online services. However I ‘m not willing to mix personal and company finances together at alll. Therefore I’m considering transferring my ...

Gaya Total hours: 178.017 Top three: 1) Setup Biz Banking with final runway 2) Looked at pricing again along with new 5, 10, 20 year plan 3) Worked on 2SSL to code ...

Gaya Total hours: 174.867 Top three: 1) Network Task Processor Researcher 2) Call Stack and JS understanding 3) Timeout and SetInterval differences between Web vs Node ...

Gaya Total hours: 173.217 Top three: 1) Got UUID_r 100% test coverage 2) Finalized TaskCreator 3) Got layer_0 code w/ no errors ...

Total hours: 171.567 Top three: 1) Decryption Engine 100% code coverage for test 2) Increased Encryption Engine code coverage to 98.29% 3) Fixed Typescript Issue for plain mocha testing ...

Total time: 168.133 Big Three : Testing Crypto Core Testing Encryption Engine Troubleshooting Decryption Engine ...

Total time: 164.083 Big Three : Testing UUID Finalizing Crypto Wiki setup remotely ...

Total time: 160.633 Big Three : Setting up testing Wallaby UUID Generation and requirements Crypto verification ...

Total time: 158.350 Big Three : Decryption Engine Secondary Logic Planning Server Anti Replay UUID Investigating Multiple Identities Tie In ...

Total time: 155.083 Big Three : Decryption Engine Primary Logic Sodium Library Truoubleshooting Addressing Typescript Odditites ...

Total time: 148.500 Big Three : Encryption UUID_t Typescript wrangling and settling on placeholder and boolean detectors Encryption UUID and other interfaces and types design ...

Total time: 144.217 Big Three : Layer 1 Continued Storage Engine and remote permissions Encryption Engine Write to Code ...

Total time: 142.933 Big Three : Layer 1 Paper Coded Browser Authentication Interface Encryption Engine Write ...

Total time: 138.833 Big Three : Layer 4 now in code Layer 2 now in code NetworkTask Manager close to finalization on paper ...

What I did: Layer 3, and 2 Total time: 134.817 Big Three : Using Pull concept EFile and Event Loop prevent unnessary freezing and flexibility Improved Unified Global Filesystem with special unlock file ...

What I did: Breakthru in design Total time: 129.033 Big Three : Simplified Protocol by going more complex in one direction which provides massive stability, longevity and flexibility in another vein Worked on Layer 3 Created Unified Global Filesystem Naming Concept. (That is all devices are leafs within a global filesystem). ...

What I did: Groundwork and Long Term Automation Total time: 123.617 Big Three : Researching and settling on automation framework for cloud and environment Setting up Repository Pattern Began Migration to Public Source Control Provider ...

What I did: Began coding website Time spent: 119.333 Comments: UI Design for both static and non static areas HTML/CSS Research HTML Development Troubleshoot CSS Snapping ...

What I did: Finished up Website color pallet choosing Time spent: 116.867 Comments: Health script repair Color Pallet choose Primary day https://coolors.co/f7f7fb-1c1d21-3f612b-119da4-e94f37 Primary night https://coolors.co/1c1d21-f7f7fb-3f612b-e3b505-e94f37 UI Design and Theme. I'm trying to figure out how the UI will flow and interact so that switching from the landing page to an operator's account will be absolutely seamless. ...

What I did: Finished up Crypto.decrypt, rxUUID and txUUID along with reengineering state management for UUID reissuing. Time spent: 115.60 Comments: Working on UUID_t and reading thru code to see how it's used. .getUUID():UUID, .valid(UUID):boolean and throws RefreshStateError if out of UUID's to use. txUUID has .getUUID():UUID and rxUUID has .valid(UUID):boolean Both are constructed using Uint8Array[] Alright finished txUUID() which is the easier of the two. Now working on rxUUID() which...

What I did: Finished up Crypto.encrypt and studying UUID_t Time spent: 112.850 Comments: Finished Crypto library .encrypt() feature. Defining UUID_t code. Now. ...

https://www.linkedin.com/pulse/designing-network-protocol-cubes-endurance Why the fuck would you design a protocol? That's a very very good question. Usually when you can't have any of the current setup work and there are massive issues, unfixable issues or otherwise badly designed issues with the protocol that you wanted to use but can't. Before we can dive into how to design a networking protocol, using 2SSL (Secure Sapphirian Layer) protocol, you first need to understand theory and analysi...

What I did: Studying Encryption Crypto Time spent: 112.850 Comments: Working on Crypto library. Turns out the null is a secretNounce which isn't??? used? ...

What I did: Studying Encryption Crypto Time spent: 112.633 Comments: Updating application setup to pass context thru. Studying https://github.com/jedisct1/libsodium/blob/master/src/libsodium/crypto_secretstream/xchacha20poly1305/secretstream_xchacha20poly1305.c to understand why sodium.crypto_aead_xchacha20poly1305_ietf_encrypt( plaintext, assocData, null, await Utils.hexStringToArrayBuffer(nonce), await Utils.hexStringToArrayBuffer(key) ) Alright linking a...

What I did: Continued fleshing out Time spent: 111.917 Comments: Working on Crypto.encrypt. Method that is hiddenly complex. If has encryptionKey don't return encryptionKey Return encryptionKey Nounce and Tag Encrypted Data. Researching the library now to understand. Alright understanding. However since building for: Web Desktop Mobile That means that I'll need to create an 'wrapper layer' to ensure that we can communicate. Alright so for web we can use: https://deve...

What I did: Continued fleshing out Time spent: 110.167 Comments: Continued to work on writing the mind numbingly simple functions. It's what a complex system is made out of. Currently on insertPayloadHeader(encryptedFullHeader, sessionID, nounce, encryptedRawInnerHeader, tag) ...

What I did: Encryption, Data type definition and data organization Time spent: 110.167 Comments: For the command flow here's how the encryption of the CommandMidHeader is converted to EncryptedRawHeader. Spread CommandMidHeader into DecryptedRawInnerHeader Drop in Anti Replay UUID Use 2SSL Session Derived Key and random nounce and encrypt DecryptedRawInnerHeader Use 2SSL Session Derived Key and random Nounce and Encrypt DecryptedRawInnerHeader Place SessionUUID, random Nounce...

What I did: Typings, Implementation and Missing links Time spent: 107 Comments: Figuring out how to use typed array. Examining XChaChaPoly1305 implementation details in SNCrypto along with figuring out types Designing Layer 0 Encryption Key. https://doc.libsodium.org/secret-key_cryptography/aead interface EncryptionKey extends Uint8Array{ length: 256; // using the numeric literal type '2'} Breaking down tasks that we also need to do that are in itself quite massive that are fundamental...

What I did: Layer 1 memory, retry and error research Time spent: 102.250 Comments: Looking at data structure to keep track of which numbers used Extremely complicated. Has repurcussions on layer above and below. Along with worst case memory usage of close to 6GiB of 'cached' data which is really really really really bad. Plus since below session details impossible or very difficult to retroactively update and connect to a session. However since most actions will occur within an operator s...

What I did: Layer 0 completing and Layer 1 design Time spent: 101.167 Comments: Push based task interface. Within the network layer everything is pushed based. The frontend overall will be pull and push based. That is it can push an unlimited amount of things remotely and pull data on demand. However the overall architecture for the backend is pull based just like CloudFlare which allows better control over work scaling and automatic load bearing and resources adjustment. Network Layer 0 in...

What I did: 2SSL Link Level 0 Interface Design Time spent: 98.433 Comments: Issue with Git remote pushing not working NX generate library Realtime system and chaining by mimics Apollo computer system Event bubbling and priority raises Level 0 design and event rerouting. ...

What I did: 2SSL Link Interface Time spent: 94.383 Comments: Dealt with link interface, organization, bypassing of a state guard in initialization along with ensuring that special cases aren't treated as special cases. Understanding advanced typescript typings... Setuping up Vue/Typescript Project using VueMastery Looking at Vue Getting started. ...

What I did: 2SSL Continue developing layers Time spent: 94.383 Comments: Designing the retry and session refresh as a separate stack that interacts with the 2SSL stack. That is the 2SSL stack is just for communicating. The actual how the session UUID and other stuff is managed is done via separate stacks which allows seperation of what with how. ...

What I did: 2SSL breaking into layers Time spent: 94.383 Comments: Ran system checks and bootup routine. (1) Need to finish writing the Overview in 2SSL with the protocol Reconnection via 2SSL 24 Disconnection (need to design the five layer system before anything else can be done) 5 Debugging 5 min Disconnection (need to design the five layer system before anything else can be done) Rest of time spent (37) ...

What I did: 2SSL breaking into layers Time spent: 94.383 Comments: Ran system checks and bootup routine. (1) Need to finish writing the Overview in 2SSL with the protocol Reconnection via 2SSL 24 Disconnection (need to design the five layer system before anything else can be done) 5 Debugging 5 min Disconnection (need to design the five layer system before anything else can be done) Rest of time spent (37) ...

What I did: Network setup Time spent: 93.183 Comments: Dealt with MR conflicts Package and package-lock.json both have conflicts. If I can fix the package conflicts then npm will automatically fix package-lock.json. Dealt with server critical issues. There were two security updates that were related to vim and vi. Removed both packages to avoid having a reboot. Set server to reboot every day to apply security updates. Dealing with git issue where a push was apparently divergent...

What I did: Fixed HSTS issue in heath.js Time spent: 91.250 Comments: The API service I was using stopped correctly responding to SapphirePacks status so I ended up switching to a different browser controlled solution which queries a site, reads a response directly from the site and from there returns to the executing code. Continued working on the transfer protocol and fleshing out the various cases. I realized that I'm gonna need about five layers of software code in order to make the laye...

What I did: Continued working on file transfer fleshout Time spent: 88.967 Comments: There are two components we need to understand: 1) The transport and session layer. 2) The actual data transfer layer. Allows transferring an arbitrary data up to 34PiB in 1MiB chunks (ish). The session layer is separated from the transport layer. This is so that the session can be managed separately from 2SSL connection which doesn't make sense until you look at the data center structure. What occurs her...

What I did: Planning 3 layer protocol Time spent: 85.650 Comments: -> Setup Daily Operations -> Plan three sprints -> Begin working on new story 11 minutes Setup Daily Operations 0 minutes all three Sprints planned 5 minutes setup Jetbrains Youtrack Integration (so don't have to manage branches and issues) 12 minutes Plan full three layer stack of Gaya ...

What I did: Setup Sapphirian Infastructure Time spent: 82.583 Comments: Dealing with setting up server with high level of security and two separate systems. Local network for Git and YouTrack. Currently both are over http but since it's over a local network and port forwarding on router isn't setup we're good enough. Secured UEFI setup and disabled booting from anything but internal harddisk. ...

What I did: Testing, Mutations and Health Time spent: 79.783 Comments: 1) Check that sapphirepack.org is on HSTS preload list. There were several ways but ended up settling on the hstspreload.com api which is called once per run. This ensures high level of security in the event that certificates fail. 2) Setup intermediary project management system YouTrack. I'm now having alot of issues and project components that need prioritization along with tracking. Within a week move to Gitlab self h...

What I did: Defining a single script that outputs the first line that gives at a glance status for the entire system. (Red/Yellow/Green). Time spent: 75.783 Comments: Transfer testing to using JSON. Easier and now able to pinpoint exact error. Furthermore more portable and not using a weird file. Tests are generated dynamically during runtime along with using NX caching capability meaning only the changed projects actually run. Currently 100 cryptographic tests take approximately 3.1 sec...

What I did: Looking at how to convert a massive file into a JSON object Time spent: 72.283 Comments: ...

What I did: Moved testing to test folder and fixed module resolution Time spent: 72 Comments: ...

What I did: convert quantum protocol to node version Time spent: 71.783 Comments: Convert to require() Migrating testing and discovered several fields aren't used. Code is I'm transforming is very hacky and not well designed. ...

What I did: improved protocol and transcribed to documentation Time spent: 71.517 Comments: 1 - This just like regular packets have a component that can be forged by external systems. However replay attacks are different then hold and send later attacks. For the first we're protected against. For the second (that is a message is intercepted and held so that it doesn't arrive and then some time in the future it's released, the system will accept (presuming the connection wasn't closed)). Howev...

What I did: Simplify protocol, review quantum protocol and review 2SSL transmission protocol to ensure data up to 1PiB can be transported. Time spent: 69.333 Comments: 1 - Deal with Green Geeks answer regarding 2SSL so we're stuck with 128 bit encryption for main site on Firefox.... 2 - Dealing with version, security, replay attack and randomValue (avoiding issue with Unicode encoding issues) along with versioning 3 - Quantum Key distribution understanding 4 - Header redesign since each 2...

What I did: A bunch of odd jobs Time spent: 67.167 Comments: I had issues with CertBot so I discovered and used ZeroSSL. I had to first host the subdomain directly on SapphirePack to allow the certificate issue to work. Then after the ACME challenge was generated and passed I generated the certificate and then setup DDNS. I tested it and it worked out!!! This is very big news because it saves me close to 500 or more dollars and also allows some special network setup which allows the server ...

What I did: Ensured site sapphirepack.org only ran using latest 256 bit encryption and restricted to using TLS1.3. Time spent: 65.150 Comments: The biggest thing is ensuring a high level of security for the static content of the site. For the dynamic content, I'm not willing to do cloud since I believe that we should be able to self control the most important hubs of Gaya. This will be processing some of the most important data, acting as relays and such. There are several benefits and draw...

What I did: Plan backwards compatibility and thought experiment Total time: 64.383 Comments: Now that I've split the session and security into two separate layers the first thing is ensuring session negotiation is compatibility. I'm pulling off of TLS concept for key negotiation and seeing if I can do it in a single round trip (since TLS has already done a few trips (2 or so I believe)). ...

What I did: Read and simplify protocol along with reviewing how the quantum protocol works and planning tomorrow. Total time: 64.350 Comments: Realized I had mixed session and operator togeather. Simplifying and worrying about deauthentication attacks and denial of service attacks this way. In a future protocol may have a ignore deauth so that if communication is occuring over a hostile environment that it'll stand a better chance to make the communication succeed by ignoring likely false una...

What I did: Finished migrating 2SSL documentation specs Total time: 63.750 Comments: This was a much bigger job than I expected because the documentation ended up having alot of extremely big holes that had to be dealt with right away along with issues in terms of terminology, storage, bootup, migration. The biggest issue is the need to design storage that doesn't place restrictions on how a system is implemented yet provide enough universality between implementations that future installatio...

What I did: Planned next big step Total time: 57.883 Comments: 1) Plan Next Big step (30 day target) Done the goal is simple yet also quite complicated because it involves determining the architecture and overall complexity/simplicity of the system. I've settled on a 2SSL terminator -> Session Unwrapper -> Worker -> Session Wrapper -> 2SSL Intiator 2) Plan each set of 5 hours chunks Here is the current plan: 5 hour milestone: Transcribe and bring spec docs up to ...

What I did: Consolidated Ideas Total time: 56.467 Comments: An important part of any projects is managing the ideas. You may not use them now, you may not use them ever, but keeping good track of those ideas are super important. For example did you know that SSL and TLS are not the same thing? TLS is more secure and modern than SSL. I wanted to ensure that Sapphirepack.org was running with the latest security standards for encrypted connections. For the frontend I'm likely to go with Gasts...

What I did: Tiny Nx repo understanding Total time: 56.167 Comments: ...

What I did: Total time: 56.150 Comments: Setup two layers of security with the public/private key, including a hardcoded expiry requirement and list of pubic and private keys (signed with a primary key to authenticate and verify that changes are authorized). Looked at TweetNacl and realized I'm going to have to wrap it along with Base64 because of how it works. Exploring the places that I'm going to need to use the public/private crypto and designing the 'perfect' api so I understand what I ...

What I did: Basic Testing Total time: 54.700 Comments: I got it to successfully generate a shared session secret. However there's a minor problem I just realized, this library just creates a shared session secret but doesn't allow using a long lived public/private key pair to verify the ssl2client is connecting to the correct ssl2server. The use case is to prevent catfishing or hijacking the domain. However I'm coming up against issues that's making me rethink parts of the protocol. ...

What I did: Setting up the mono repo + importing library Total time: 54.200 Comments: I got a MR accepted https://github.com/antontutoveanu/crystals-kyber-javascript!!! This feels so good even though it's a tiny change. The reason that I'm going with a monorepo is to avoid as much software security chain violations. We've seen bad code get injected via a 3rd party dependency. By moving the most critical third party dependency as shared libraries directly managed and controlled within the rep...

What I did: Began dissecting the Public/Private Key Quantm crypto Total time: 53.067 Comments: ...

What I did: Researched public and private key system for over the air and quantum resistant key crypto Total time: 53.033 Comments: Looked at DHole again for NIST-Finalists for Post Quantum crypto. Here is the current realizations: 1) Need to negotiate a secure tunnel using Public/Private Key system that can resist quantum attacks. 2) The session once derived can use XChacha20-poly1305 which even using Grovers Algorithm gives 128 bits of security which is 'enough' for current day. 3)In the ...

What I did: Continued price research and cost analysis Total time: 51.717 ...

What I did: Research encryption and income opportunities Total time: 51.067 Comments: https://soatok.blog/2020/07/12/comparison-of-symmetric-encryption-methods/ I knew what the decision was going to be after looking around, I just needed to come to terms with it you know. It's a beautiful library that's been audited. I've made the difficult decision to AGPL the code because I want access to the beautiful crypto library that SN has built. Furthermore I know it's the right thing to do. Having ...

What I did: Getting stuck on actually implementing this gem of an idea Total time: 49.067 Designing blob storage and wrapper library POC api. The idea is that the blog storage of a file will be seperate than the actual file. There will be a few events such as: A fileID once processed is permanent. However once I realized I was drifting off of the target, which is setup the SSL2 communication I went back to SSL2 communication. Comments: I was focused on figuring out Mocha, then realized my a...

What I did: Began actually writing out code!!!!!! Total time: 48.033 Comments: Designing the keystore, session management and operator system. Setting up Typescript and Mocha (for req testing). ...

What I did: Total time: 46.783 Comments: Costs for security analysis isn't something that I can afford currently and it would be immoral to launch and claim an above standard security level. So I'm left at this weird part having hopefully increased security but not being able to prove it until hopefully 2024 or sooner. Setup a library for Error Code ...

Total time: 46.533 ...

What I did: translated last 4 errors into HTTP and SSL along with researching session token and OWASP security. Total time: 45.783 ...

What I did: HTTP and SSL2 protocol use along with a few confusing and similar ones. This is why I flesh them out like this!!! Total Time: 45.483 ...

What I did: HTTP and SSL2 codes and use cases. researching 2 providers who can do consoluting for TLS along with asking a key exhausting question finally doing a bit of encryption theory to ensure understanding. Total time: 45.183 ...

What I did: Authentication Total time: 44.083 Comments: Discovered XChaChaPoly1305 may be the break we need provides authentication of data and easily swappable encryption protocols as XChaCha is discovered to be weak. Along with developing a security watchlist on both Google SSL and Standard Notes to ensure that Gaya's security pratices stay quite modern, until we're big enough to afford our own security team. ...

What I did: Authentication Total time: 43.683 Comments: Discovered annoying bug in protocol where the SSL2 session is tied directly to the authentication of the user by relying on derived secrets. If have time (have approximately 240 minutes before needing to move on [discovered flex in my roadmap by dropping signing and verification from the first spec). So if I can answer an array of questions, I can then revisit the SSL2 protocol and redesign so that SSL2 is seperate from authentication. ...

What I did: Authentication Total time: 42.667 Comments: Grappling with questions like 'authenticate then encrypt or encrypt then authenticate?' Finding way to minimize the protocol and move session management to a higher level. This level should only be concerned about creating encrypted layer and ensuring the person is authenticated. Session management and tracking should be done at a higher level. Managed to simplify the FSM even more by moving session management to a higher level. Furtherm...

Goal: Finalize features and targets for version 0.0.1 Status: SUCCEEDED Total hours: 38.750 ...

Goal: Install Project Dependencies with Cordova and get a hello world. Status: SUCCEEDED | FAILED Task: - Install WSL2 [Success] - Install Cordova [Success], Typescript [Success], Vue3 [Success], OnsenUI [Failed], - Get Hello World working on Mac[Failed] Realization: I was planning too far into the future and adding needless complexity. In the future I can split the repo's up into mutiple files and pull the 'core' into all the systems. I was substituting theoretical ability to add ...

15 Looking at low poly planets and contemplating designs 45 Beginning to design API for signup/login, along with database and beginning to design threat model 60 Setting up NodeJS14, addressing windows issues, beginning to migrate from WSL1 to WSL2 ...