stardance has been extended another month! the new deadline is october 31 :)

You are browsing as a guest. Sign up (or log in) to start making projects!

Pradhya

@Pradhya

Joined June 7th, 2026

  • 20Devlogs
  • 4Projects
  • 2Ships
  • 18Votes
Just a student in class 9. I have no idea what CBSE is doing atp.
Main project for now is Enclave Messenger
Open comments for this post

10h 14m 50s logged

Haiii again!
Whats done!

Security review of the messenger by Claude and fixes for what it found:

  • the passphrase no longer goes in the URL (it used to end up in logs), it is sent in a header now
  • running with –host lan now needs a one-time access code, and debug mode is forced off there
  • plugins are not run until I explicitly trust them, and the trust is tied to the plugin’s file hash, so editing it cancels the trust
  • addresses that other peers give us are checked before we connect

UI/UX Changes

  • Messages now have clear stats if they were delivered(directly), sent via a peer, or unsent/failed
  • Failed messages now have a retry button to attempt to re send it.
  • Settings menu has a copy user-id/enclave-id and a qr code too to add them to their peers
  • User profiles can now be easily backed up and restored through the web ui
  • Ive tried adding plugins, still need to test it and move everything to a plugin based system…

Misc but important

  • INSTALLATION: you can now use pip/pipx to install it, but youll need to use pipx install . because i want to fix some bugs before publishing it to pypi.

  • DATA MIGRATION: the way that the messenger stores data and where it stores data has been changed so if the pe-em detects any data in the folders that the messenger prev used, then it will move it but not delete the data from the prev dir, which was ~/.enclave-messenger

  • EXECUTABLES: the exeuatables for windows, linux and mac will still be built, but only the linux one will be properly tested because i only have a ubuntu install, i dont have a mac nor enough system resources to test windows or run a mac vm.

  • CHECKS: Claude added like 200 checks and like a ci job that runs them all.

BuGs

  • The lan scanner was looking at the wrong port, ugh
  • The windows executable did not start the bluetooth and sms plugins
  • Profiles were broken on the windows executable. (Ugh i hate windows)
  • set.py (the setup file) did the setup properly, but didnt save the profile stuff like name but that never got noticed because core.py fixed it when either web.py or tui.py was launched.
  • QR Code doesnt render

Website

  • I still kinda have to redo it all,
  • Update the info on the website.
  • Etc
0
0
20
Ship Pending review

So, what ive made is a tool that helps me (yes, mainly me because why not. You can use it too tho!!) develop my other stuff ie enclave messenger, and that has like a LOT of like repetitive stuff which i wanted to reduce likeee python3 ../dev-tools/sigh.py (yes its sigh.py not sign.py . i just wanted some fun tbh) and i plan to add a lot more stuff and improve my messenger so i added a lot of stuff i needed while making this and a clock.

The challenging part was to like package this and like get it to pypi. Andddddd figure out what i wanted to do here. Like… idk D:

Im proud that i managed to like package this and like get it to pypi so i can learn and like package my messenger properly when i redo it… soonnnnnnn

The installation guide/process is in the readme.md
or just run pipx install project-enclave-tools

Try project → See source code →
Open comments for this post

1h 52m 30s logged

Added MORE HELPERS for stuff like

  • Project init
  • Diagnostic
  • Changelog
  • Version
  • Release
  • Asset
    Improved:
  • Signing (that was the only thing i could improve t_t)
  • Config management
0
0
20
Open comments for this post

4h 51m 19s logged

Im finally done with all of the PLANNED docs, i still have to add some docs for stuff like DHT, hosting, etc and i have to make plugins, remove in-built stuff stuff, etc

0
0
19
Open comments for this post

1h 45m 57s logged

So im still not done with all the docs, i have like 5 files left to complete. But, i managed to style my mkdocs site and it looks pretty similar to the messenger site…
I like the installation one the most.
Yay!

0
0
42
Open comments for this post

10h 21m 27s logged

i somehow broke the web ui while trying to add profiles so im also adding a cli and a tui
its not a good idea but its an idea
The tui will probably look like this.

So, the todo is now to fix the web ui, make the tui and add profiles so the reviewers can check it out

The below screenshot is from noterooms cli by me!

0
0
8
Open comments for this post
Reposted by @Pradhya

2h 42m 44s logged

5IR Line Follower Devlog — Day 3
Today we made good progress on the mechanical assembly of our 16IR Line Follower Robot .
We permanently mounted the BTS7960 motor drivers onto the chassis and completed the motor connections. We also installed the caster wheel, but ran into an unexpected problem. The caster wheel we had was around 2.25 cm tall, which made the front of the robot sit higher than required. We searched for a smaller caster wheel on Amazon and other platforms but couldn’t find one that matched our requirements.
Instead of waiting for a replacement, we decided to modify the existing caster wheel ourselves. We carefully trimmed the extra material and reduced its height from 2.25 cm to 1.79 cm, which brought the chassis to the desired level and improved the overall balance of the robot.
With the motor drivers mounted, motors connected, and the caster wheel modified and installed, the robot’s hardware assembly is now much closer to completion. The next step is to complete the wiring between the ESP32, the 16IR sensor array, and the motor drivers before moving on to software testing and calibration.
@chinglen2080.

0
2
144
Open comments for this post
Reposted by @Pradhya

2h 13m 9s logged

Today was the first day of building our 16IR Line Follower robot.

Chinglen and I started working on the initial development and planning of the robot. We worked on writing the first motor control code and preparing the hardware setup.

We soldered the connections for the N20 600RPM geared motors and mounted the 16IR sensor array onto the chassis. We also started planning the complete electronics layout — deciding the positions of the battery, BTS7960 motor driver, and ESP32 38-pin board to keep the design compact, balanced, and easier to wire.

The next steps will be completing the wiring, testing sensors and motors, tuning the control system, and improving the robot’s speed and stability.

This project may take around 1 month to complete because we want to properly test and optimize every part of the robot.

Hardware used:

16IR sensor array
ESP32 38-pin board
2 x BTS7960 motor driver
2 xN20 600RPM geared motors
3d PrintedCustom chassis

What do you think will be the biggest challenge: PID tuning or sensor calibration?

@chinglen2080

Edited - Thanks for the support!

1
2
608
Open comments for this post

1h 21m 7s logged

I need to make these test better on my laptop… TADC ep9 kinda made me go off track but it was good. I think that was the most i cried while watching a movie. Well, leave that behind. Also, i think its all in one line because i can’t make a new line on mobile. And i think i messed up my ears. Ouch

0
0
10
Ship Changes requested

What it is

A fully offline, peer-to-peer encrypted messenger that runs over Bluetooth (RFCOMM) and local network — zero internet required, zero servers. Messages are end-to-end encrypted, and the UI runs as a local web app in your browser.
What was built

Bluetooth node — discovers peers via SDP UUID, connects via RFCOMM

Web UI — a polished chat interface with dark/light mode, animated splash screen, message bubbles, peer list with live scan

End-to-end encryption — passphrase-based, messages show enc/decrypted badges

Multi-transport system — send messages to phone numbers when Bluetooth and LAN isn't available

Plugin system — extensible architecture with manifest-based permissions, security watchdog

Signed update system — RSA-4096 signed manifests + SHA-256 file hashes so updates can be verified without internet

What was challenging

Bluetooth peer discovery without internet — SDP/RFCOMM is finicky, BlueZ on Linux requires careful pairing/trust setup

Coordinating encryption across peers who may be offline — tokens stored locally, decrypted on-demand when passphrase is entered

Plugin security in CPython — no real sandbox exists, so the security model relies on scoped PluginCore objects.

What to be proud of

The UI is genuinely polished — smooth animations, staggered reveals, real-time WebSocket updates

The update system is cryptographically sound for an offline-first app

To test it

Requirements:

Linux (BlueZ), Python 3.11+, Bluetooth adapter

pip install -r requirements.txt

Setup:

python set.py — configure identity + passphrase

python main.py — starts the node + web UI (visit localhost:5000)

Enter your passphrase in the unlock modal to start the Bluetooth node

Click scan network in the peers panel to find other Enclave instances nearby

Open a chat, send a message — it'll show enc if stored encrypted, decrypted once unlocked

Two-device test: Run on two Linux machines with Bluetooth, make sure they’re paired, both run main.py — they should discover each other automatically.

  • 3 devlogs
  • 11h
Try project → See source code →
Loading more…

Followers

Loading…