Kanashimo

Hello, this is my last devlog! Sooooo, how to say that… the WebAuthn works and setup too. But I threw out every other idea, because there’s no more time for that. I’m planning to add more features to this project later, some of them are

• multiple users
• access control
• TOTP
  etc.

UI is simple but looks good to me. Sorry that I haven’t wrote any devlog for the last 4 hrs but I was locked in. Here is a quick showcase. Oh, and btw I published the whole project as a docker container on ghcr

Hello, I just finished working on WebAuthn business logic and now I’m working on frontend. I’m using simplewebauthn library both for client and server. Being more precise, now I’m implementing the app setup page, so the first user can register and add the first passkey, and ofc one user can have multiple passkeys. Later on I’m going to add settings where you can manage your credentials and maybe I will add some sort of admin panel where you can invite new users, but I don’t know if I will have enough time, because the event ends in 7 hrs. Anyway, see you next devlog!

Hello, I have finished making boilerplate code, this project is my own clone of PocketID but with support for both, TOTPs and WebAuthn. I’m targeting Caddy because that’s my daily-driven http server and reverse proxy. I’m using Caddy’s forward_auth directive to pass every request via my gateway, so later on I can check the session cookie that contains all information about the user, more technically his id, name and public key. For this project I’m using Express with Prisma for the backend and React for the frontend.

I made quite a lot of small changes and the project is now polished and ready to ship!

Changelog:

• Added the container to GitHub Container Registry
• Added lazy loading and removed “flickering” when changing tabs
• Added workflow, so now when I push a new tag, the container is automatically builded and published
• Improved API error messages for authentication
• Fixed various CSS bugs
• Deployed demo
• Other small fixes in logic that are not worth mentioning

Hello again! I’m happy to say that everything is finished, both frontend and backend works perfectly. I still have to setup Docker. Maybe I’ll use GitHub Workflows, I don’t know yet.

Here’s a quick changelog:

• I added search and filters to projects page
• I added project edition page
• Now you can add, edit and remove categories (with fancy modal)!
• Oh, and also I made projects page actually working (before in the other devlogs it was jus a static page)
• I fixed styling, so now everything is nicely aligned
• I added logging for API

I feel like a bot, because I wrote “projects page” 100 like times here, haha

Hello, this is my next devlog! Since the last one I’ve added leaderboard, project creation page and implemented badges on the frontend. Now I’m working on categories! Here is the quick showcase of my work for the last hours

I have been messing around with it for last couple of hours, but finally the login and registration page is finished, getting the AuthProvider took the most time, but now everything works. I also made some of the config’s part available via API so it’s easier to handle it in frontend and I made 404 Not Found page. See you next devlog!

UI responsible for displaying projects is finished. But still I’ve to implement the leaderboard, new project page, edition of them, categories and also login and logout page!

Hello, I just finished the whole API and we can now perform every action of CRUD! Also, I added some new fancy features, including:

• easy configuration via env variables or .env file
• leaderboard (be the best at procrastinating)
• badges (like those from shields.io, you can style your README with them)
• I improved validating input data in requests, the errors now give you the actual message, not only “Invalid input”
• Last but not least, I added categories, so now you can categorize every project

If you don’t want badges and leaderboard you can disable both in config.

Now it’s time for frontend in React. I will replicate the look of killedbygoogle.com (and take some CSS from them) because it’s my main inspiration for this project, so at least I will have to write less CSS than I normally would

Hello! If you are programming things for more than 3 days and maybe a little more creative than AI agent, then you probably have a lot of projects, I MEAN A LOT. But it is what is it and most of them will never be finished. So in short, this is idea of this project, it helps you track your dead projects so at least you will have great memories or maybe one day you will dig them out from the ground? Who knows.

The concept is that basiclly the main page will look the same as killedbygoogle.com, even the logo is the same but the user will be able to costumize it, so instead of seeing Killed by Myself, you will get Killed by John Smith or something similar. Also I want to add some sort of leaderboard, so you can compeat with your friends for number of dead projects.

Now, I’m implementing the backend, my techstack is TypeScript, Express, Prisma and React. Despite that this is the “funny one” type of project I want it to be “robust” and “professional”, so I’m using Zod for validation of literally everything, so later I can catch every error.

I was struggling for 2 hours with making my schema validation middleware, only to learn that it wasn’t my bad. Yeah, I love to code! And also, the database if finished.

See ya.

I fixed a bug which caused to disable Shorts, even when all settings where set to not disable them. The cause of that was I wrongly handled the undefined value. I pushed everything to the repo and made a new release, named v1.1.0. Fun fact: the bug appeared only when you opened YouTube in new tab, when you refreshed the website, everything worked as should.

Everything is finished (or I think so), since the last devlog I added a custom checkboxes that look much much butter (and they have fancy animation!11!!!!1), also I changed the UI font so it looks more like the YouTube one.

From the “boilerplate side” I added README, GitHub reposiotry and MIT license. That’s all.
So the only thing that left to do is… ship, ship, ship, ship!

By the way, you can ask why I haven’t used any bundler like Vite. The answer is that this project is too simple for that, and it would be close to overengineering than.

I made some minor fixes to the logic, and finished a feature that allows you to completely block YouTube Shorts URL, here’s the showcase! See ya

Hello! This is my first Flavortown project and not only that, it’s my first browser extension that I’ve ever made. At the moment, I’ve implemented blocking the shorts itself on YouTube’s website. Now I’m working on this “awesome” (ekhem) UI. Maybe I will say something more about the project, I picked it because it’s kinda easy to create, so I can learn how the whole platform works and also I was looking to start it since the beggining of this year, but I haven’t had enough motivation to do so, but this is the perfect time.