sam.vandenabeele.09

I have added a way to enable/disable the blocker in the extensions window

I have implemented the blocker for youtube shorts, instagram reels and tiktok. It definitly works best on youtube, tiktok just shows a black page, and instagram works, but when you look up an account, the normal posts don’t get a new place, so you just get a grid with here and there a post.

It both blocks all buttons to reels/shorts, and it automatically reroutes reel and shorts links to the homepage.

I edited the docker configurations. Everything is now way more streamlined, and I don’t have to manually build the frontend before I build the docker image anymore.

I added even more things to the mock server, and have completed the styling. I’m not really happy with it though. I’m no good at ui design.

I know it’s been a long time, but I’ve been really busy lately for CanSat, but with things that don’t track time. We have submitted our report 2 weeks ago, and have received the news that we have been selected for the semi-finals!

Since then, I’ve streamlined the sensor management, and created an easy way to write all of our data to the sd card in csv format, using a dynamic filename system.

I’ve also finished the pcb, which has been sent out for chipment.

I have finished the pcb, as well as the GETTING_STARTED.md, as well as the pcb (I’ll revise it though)

Also, my teammates took my phone, so that’s the bonus picture.

I have created a mock server. This way I can test everything without needing to spin up my backend every single time, and I can clearly see if something is a backend or frontend problem.

I did this using MSW, and it connects natively in my frontend, so I don’t even have to spin up a mock server. It’ll just look in the environment variable to see if I’m running dev or prod, and based on that the mock will intercept it or not.

I have added some more styling (I don’t rely on chatgpt/google anymore for that :), jippie!). I have also revised my way of authorisation in favor of React’s native AuthContext, instead of passing around useState variables to everywhere which was super messy and led to unreadable code.

I have added tailwind to the website, and have styled most of it. Tailwind is really nice, but the code gets bloated fast, it surely doesn’t increase readability.

On the software side, I am creating all of the drivers that my teammate will need in order to get started (he’s less of a geek, with no experience, so I handle the more complex stuff because of our limited time). I will then write a GETTING_STARTED.md file for him, that’ll hopefully save him a lot of time.

I have managed to get all power circuitry in place, as well as the central MCU and the microSD-card. This has proven challenging, but easier than expected.

electrical design best practices followed: 0
DRC rules broken: my pc exploded before DRC was done (I haven’t run it yet, and my pc is fine, I joke too much)
sanity left: 0
times I declared myself crazy for doing this: 12

Also, I’ve been able to keep this project one sided for now, nice!

Also, someone liked my previous devpost, thank you :)

I have routed all individual ‘blocks’, but some things really aren’t the way they should be (see picture). I will try to clean up a little, and after that I’ll try to bring all these blocks together.

I also noticed (far to late) that all my trace width calculations were done for 2 oz copper, so I guess the pcb will be a little more expensive than previously planned.

I am working on the pcb. It ain’t easy, and I keep doubting mself :). I’m rather confident that I’ll have to make a V2 with a lot of changes.

I have split the pcb up in ‘blocks’, components with the same function. I will now try to route all of them, and after that I’ll try to bring these blocks together on the final pcb. I am trying to stay in one layer, but it’s proving very difficult.

I have created a good(?) README.md file that explains the project etc. I will now try to use tailwind to make the website beautiful, or at least usable.

NOTE: I started this project before I entered in hack club. This means that it’s already done for a big part. Unfortunatly without the time tracking, so no coockies :(.