|
11351
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792925621.8326108
|
1793789621.8326108
|
|
11352
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792950561.7000818
|
1793814561.7000818
|
|
11353
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792929208.9408612
|
1793793208.9408612
|
|
11354
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792954160.222202
|
1793818160.222202
|
|
11355
|
FloatHub by @seven | Stardance
|
seven
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: FloatHub by @seven | Stardance
|
1792795685.7843769
|
1793400485.7843769
|
|
11356
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792922008.436799
|
1793786008.436799
|
|
11357
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792896521.0720665
|
1793760521.0720665
|
|
11358
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792885691.548487
|
1793749691.548487
|
|
11359
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792946906.3536656
|
1793810906.3536656
|
|
11360
|
My awesome macropad! by @lakkey | Stardance
|
lakkey
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @lakkey | Stardance
|
1792784903.8943126
|
1793389703.8943126
|
|
11361
|
Untitled by @AceTech101 | Stardance
|
AceTech101
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @AceTech101 | Stardance
|
1793235322.4627268
|
1793840122.4627268
|
|
11362
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792921786.6257303
|
1793785786.6257303
|
|
11363
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792957700.6240013
|
1793821700.6240013
|
|
11364
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792925674.990174
|
1793789674.990174
|
|
11365
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792929044.1128957
|
1793793044.1128957
|
|
11366
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792921829.2587748
|
1793785829.2587748
|
|
11367
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792925567.1636367
|
1793789567.1636367
|
|
11368
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792940054.007078
|
1793804054.007078
|
|
11369
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792943537.8283184
|
1793807537.8283184
|
|
11370
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792954462.420088
|
1793818462.420088
|
|
11371
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792946971.4063904
|
1793810971.4063904
|
|
11372
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792947262.4115598
|
1793811262.4115598
|
|
11373
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792929076.6391938
|
1793793076.6391938
|
|
11374
|
My awesome macropad! by @AdvikG | Stardance
|
AdvikG
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @AdvikG | Stardance
|
1793156145.0597563
|
1793760945.0597563
|
|
11375
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792882154.865024
|
1793746154.865024
|
|
11376
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792918471.642374
|
1793782471.642374
|
|
11377
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792932812.9010153
|
1793796812.9010153
|
|
11378
|
Untitled by @ryananderson1036972 | Stardance
|
ryananderson1036972
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @ryananderson1036972 | Stardanc Title: Untitled by @ryananderson1036972 | Stardance...
|
1793483858.421425
|
1794088658.421425
|
|
11379
|
Untitled by @ryananderson1036972 | Stardance
|
ryananderson1036972
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @ryananderson1036972 | Stardanc Title: Untitled by @ryananderson1036972 | Stardance...
|
1793386429.8565025
|
1793991229.8565025
|
|
11380
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792896806.919002
|
1793760806.919002
|
|
11381
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792947302.4303923
|
1793811302.4303923
|
|
11382
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792885681.8620715
|
1793749681.8620715
|
|
11383
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792943422.6713247
|
1793807422.6713247
|
|
11384
|
Holos by @caasion | Stardance
|
caasion
|
0
|
10.71
|
0
|
[]
|
[{"post_id": 6920, "ts": "2026 [{"post_id": 6920, "ts": "2026-06-11T16:26:36Z", "hours": 0.9211, "text": "Some more fixes to really get the plugin to be useable by other people! v4.0.5 Add ability to change track effective dates in Workbench Change how track effective dates work Only 1 interval of active dates No longer dependent on its internal project contents Remove old, unused settings options"}, {"post_id": 4935, "ts": "2026-06-08T15:30:19Z", "hours": 1.1261, "text": "Releasing and shipping something for other to use really isn’t about just pushing code. After writing up my release, I thought I would be done, but when it actually came to test the plugin out on my vault, I ran into some issues that made the plugin really unusable, so I’ve been working towards fixing that. Here’s what I addressed: Added the ability to create projects and tracks (After the redesign, I forgot to add a button to create these basic things!!) Removed directly style sheet injection (Obsidian doesn’t like it when I add css using javascript) Added the ability to define start and end date for projects with 1 phase I still got some bugs to fix and production issues to address!"}, {"post_id": 4567, "ts": "2026-06-07T22:14:29Z", "hours": 1.5069, "text": "I’ve been working on the actual v4 release of the plugin. But it’s been taking a lot longer than I thought. While testing the plugin in my test environment, the plugin runs quite smoothly. However, when testing it in my actual vault, it is a lot slower and less performant than I expected. Waiting 9 seconds just to switch a view is such a deal-breaker. Regardless, here is what I did since the last devlog: Added a panel to edit tracks in the “Workbench” view (When redesigning the views, I forgot to provide a place for people to edit their tracks) Fixed styling of the Gantt chart view Attempted to optimize performance with rendering tweaks and by removing some debounce conditions"}, {"post_id": 4433, "ts": "2026-06-07T19:09:26Z", "hours": 0.5228, "text": "I added the capability for partial task completion. At first, I thought it would be a super simple task, but because of how tightly integrated everything is in the project, it took me a little longer than I thought it would."}, {"post_id": 4366, "ts": "2026-06-07T17:47:14Z", "hours": 6.6358, "text": "Hey everyone! I’ve been building Holos, a productivity plugin that connects big-picture life planning to daily execution, all inside Obsidian. The core idea: a three-tier system where Tracks define what you’re focusing on in a phase of life, Projects drill into specific areas, and a grid planning view turns everything into executable daily tasks. All stored in plain markdown files in your vault. I built it because I kept overcommitting and losing the thread between my seasonal goals and what I was actually doing day to day. It’s been my daily driver for a while now. This project has gone through many iterations, and I’ve recently started reworking the UI to make the plugin truly usable and intuitive for new users. I would appreciate any feedback on the UI. Meanwhile, I am working on the task and rendering logic to make sure things are working as intended!"}]...
|
Title: Holos by @caasion | Stardance
Devlogs:
Hey Title: Holos by @caasion | Stardance
Devlogs:
Hey everyone! I’ve been building Holos, a productivity plugin that connects big-picture life planning to daily execution, all inside Obsidian. The core idea: a three-tier system where Tracks define what you’re focusing on in a phase of life, Projects drill into specific areas, and a grid planning view turns everything into executable daily tasks. All stored in plain markdown files in your vault. I built it because I kept overcommitting and losing the thread between my seasonal goals and what I was actually doing day to day. It’s been my daily driver for a while now. This project has gone through many iterations, and I’ve recently started reworking the UI to make the plugin truly usable and intuitive for new users. I would appreciate any feedback on the UI. Meanwhile, I am working on the task and rendering logic to make sure things are working as intended!
I added the capability for partial task completion. At first, I thought it would be a super simple task, but because of how tightly integrated everything is in the project, it took me a little longer than I thought it would.
I’ve been working on the actual v4 release of the plugin. But it’s been taking a lot longer than I thought. While testing the plugin in my test environment, the plugin runs quite smoothly. However, when testing it in my actual vault, it is a lot slower and less performant than I expected. Waiting 9 seconds just to switch a view is such a deal-breaker. Regardless, here is what I did since the last devlog: Added a panel to edit tracks in the “Workbench” view (When redesigning the views, I forgot to provide a place for people to edit their tracks) Fixed styling of the Gantt chart view Attempted to optimize performance with rendering tweaks and by removing some debounce conditions
Releasing and shipping something for other to use really isn’t about just pushing code. After writing up my release, I thought I would be done, but when it actually came to test the plugin out on my vault, I ran into some issues that made the plugin really unusable, so I’ve been working towards fixing that. Here’s what I addressed: Added the ability to create projects and tracks (After the redesign, I forgot to add a button to create these basic things!!) Removed directly style sheet injection (Obsidian doesn’t like it when I add css using javascript) Added the ability to define start and end date for projects with 1 phase I still got some bugs to fix and production issues to address!
Some more fixes to really get the plugin to be useable by other people! v4.0.5 Add ability to change track effective dates in Workbench Change how track effective dates work Only 1 interval of active dates No longer dependent on its internal project contents Remove old, unused settings options...
|
1792806753.7211792
|
1793411553.7211792
|
|
11385
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792936034.0458
|
1793800034.0458
|
|
11386
|
My first slack bot! by @ayithapranav1 | Stardance
|
ayithapranav1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @ayithapranav1 | Sta Title: My first slack bot! by @ayithapranav1 | Stardance...
|
1793389842.835091
|
1793994642.835091
|
|
11387
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792943376.2567985
|
1793807376.2567985
|
|
11388
|
Enclave Messenger by @Pradhya | Stardance
|
Pradhya
|
1
|
54.05
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-18T12:15:31Z", "hours": 11.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "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.", "repo": "https://github.com/Project-Enclave/Enclave-Messenger", "demo": "https://messenger.projectenclave.dev/"}]...
|
[{"post_id": 78709, "ts": "202 [{"post_id": 78709, "ts": "2026-10-11T11:25:29Z", "hours": 10.2472, "text": "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"}, {"post_id": 73096, "ts": "2026-09-24T11:35:52Z", "hours": 4.8553, "text": "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"}, {"post_id": 67969, "ts": "2026-09-14T09:17:27Z", "hours": 1.4697, "text": "Added more stuff for future stuff and plans for the messenger Its sad that this challenge is ending soon…"}, {"post_id": 65316, "ts": "2026-09-10T11:55:12Z", "hours": 1.7658, "text": "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!"}, {"post_id": 63779, "ts": "2026-09-07T18:54:46Z", "hours": 0.9619, "text": "Yay! I got the guide up and reachable at https://messenger.docs.projectenclave.dev/ hosted on vercel The only issue is that its not complete D: And i cant add this to the projects details because its being reviewed :("}, {"post_id": 63533, "ts": "2026-09-07T13:28:12Z", "hours": 0.8214, "text": "Docs looking pretty good I still have to turn this into a site…."}, {"post_id": 61566, "ts": "2026-09-04T15:23:48Z", "hours": 1.4228, "text": "Got a LOT of assets to finallyyyy make the docs and guide! Yay!"}, {"post_id": 60417, "ts": "2026-09-02T18:35:48Z", "hours": 0.9247, "text": "I finally did the read meeeeee"}, {"post_id": 59750, "ts": "2026-09-01T17:58:49Z", "hours": 7.6833, "text": "I FINALLY GOT IT TO WORK!! i still have to fix the web ui… At least i got the router to get working and the tui HURRAY!"}, {"post_id": 27613, "ts": "2026-07-13T10:59:30Z", "hours": 10.3575, "text": "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!"}, {"post_id": 12577, "ts": "2026-06-20T15:19:07Z", "hours": 1.3519, "text": "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"}, {"post_id": 11910, "ts": "2026-06-19T12:26:36Z", "hours": 1.1892, "text": "Finally made the installation a one liner! Enclave Messenger"}, {"post_id": 11209, "ts": "2026-06-18T10:50:01Z", "hours": 8.7239, "text": "Dev-log 3 What has been done Made the settings look a bit better Added better plugin support Added a built-in Bluetooth support on Linux(Ubuntu) Fixed a security bug where if the host/core was already unlocked, any password was allowed Made the onbording process easier Added a reset file for development and to delete all chat, config, etc made by any files in the repo. Moved the web page to a file in ./templates from ./web.py . The entire file was just a string… Kinda fixed the message bubbles. Made a tool to verify if the files you have are by me for p2p updates What is in progress as of now Make a plugin manager Create documentations Add cross support for apps like blechat and silence Make the UI/UX better Etc also, for why im doing this, see this"}, {"post_id": 5573, "ts": "2026-06-09T12:19:44Z", "hours": 1.3175, "text": "i fixed the networking and transport and i also ditched the logo sorry for the poor quality. cant do higher without i3/ubuntu crashing."}, {"post_id": 4761, "ts": "2026-06-08T07:11:49Z", "hours": 0.5481, "text": "First devlog Almost done with crypto and networking and the UI Made whatever this is as the logo for now"}]...
|
Title: Enclave Messenger by @Pradhya | Stardance
Title: Enclave Messenger by @Pradhya | Stardance
Devlogs:
First devlog Almost done with crypto and networking and the UI Made whatever this is as the logo for now
i fixed the networking and transport and i also ditched the logo sorry for the poor quality. cant do higher without i3/ubuntu crashing.
Dev-log 3 What has been done Made the settings look a bit better Added better plugin support Added a built-in Bluetooth support on Linux(Ubuntu) Fixed a security bug where if the host/core was already unlocked, any password was allowed Made the onbording process easier Added a reset file for development and to delete all chat, config, etc made by any files in the repo. Moved the web page to a file in ./templates from ./web.py . The entire file was just a string… Kinda fixed the message bubbles. Made a tool to verify if the files you have are by me for p2p updates What is in progress as of now Make a plugin manager Create documentations Add cross support for apps like blechat and silence Make the UI/UX better Etc also, for why im doing this, see this
Finally made the installation a one liner! Enclave Messenger
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
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!
I FINALLY GOT IT TO WORK!! i still have to fix the web ui… At least i got the router to get working and the tui HURRAY!
I finally did the read meeeeee
Got a LOT of assets to finallyyyy make the docs and guide! Yay!
Docs looking pretty good I still have to turn this into a site….
Yay! I got the guide up and reachable at https://messenger.docs.projectenclave.dev/ hosted on vercel The only issue is that its not complete D: And i cant add this to the projects details because its being reviewed :(
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!
Added more stuff for future stuff and plans for the messenger Its sad that this challenge is ending soon…
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
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
Ships:
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....
|
1793274687.5595064
|
1793361087.5595064
|
|
11389
|
My awesome macropad! by @srisailaasyamadala | Star My awesome macropad! by @srisailaasyamadala | Stardance...
|
srisailaasyamadala
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @srisailaasyamadala Title: My awesome macropad! by @srisailaasyamadala | Stardance...
|
1793303317.2106814
|
1793908117.2106814
|
|
11390
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792896678.5476131
|
1793760678.5476131
|
|
11391
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792922005.97644
|
1793786005.97644
|
|
11392
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792950534.1869483
|
1793814534.1869483
|
|
11393
|
ASTRO FLORA by @AshishPatel | Stardance
|
AshishPatel
|
0
|
11.75
|
0
|
[]
|
[{"post_id": 11139, "ts": "202 [{"post_id": 11139, "ts": "2026-06-18T06:52:17Z", "hours": 7.0169, "text": "Devlog #2: Systems Architecture & Circuit Map Complete! Hey everyone! 🚀 After a massive coding sprint yesterday, I have successfully locked down the core codebase for Astro-Flora and finalized the official hardware circuit schematic! Since Astro-Flora is designed to be an industrial-grade, multi-zone life support system for extreme space environments, I needed to make sure the hardware layout perfectly matches the decoupled state-machine architecture of my code. 🌌 Hardware Subsystem Breakdown I have organized the system architecture into four dedicated operational blocks: Sensor Array Inputs: Dual capacitive soil moisture sensors (Zone A on A0, Zone B on A1) set to monitor a desiccation threshold of 450, an atmospheric thermistor on A4, and a fluid reservoir level unit on A5 to prevent dry-pumping. User Interface & Audio Alerts: A 16x2 LCD display running via I2C (0x27) displaying live metrics alongside custom-rendered hex glyphs (Sprout, Sun, Moon, and Critical Warning). A master piezo buzzer sits on Pin 7 for cascading acoustic transaction tones. Digital Security Interlock: A biometric badge-swipe simulator connected to Pin 10 using internal pull-up resistors to log crew entries and exits seamlessly. Isolated Relay Actuators A 5-channel opto-isolated relay array connected to digital pins 2, 3, 4, 5, and 6 to safely drive high-power external loads (Solenoid water valves, grow lights, radiant heaters, and CO2 circulation fans). 🛡️ Critical Engineering Safeties Added While drafting the final blueprint, I made sure to add flyback diodes across the solenoid water valve channels. Since pumps and solenoids create heavy inductive voltage spikes when collapsing their magnetic fields, these diodes will keep the relay module and the Arduino Mega completely protected from back-EMF damage. The schematic is officially mapped, the code compiles flawlessly, and I’m ready to advance from the Design Phase to the Building Phase as soon as the review clears! Check out the full schematic below! 👇"}, {"post_id": 5591, "ts": "2026-06-09T13:22:46Z", "hours": 4.7361, "text": "🌿 Astro-Flora: Automated Martian Greenhouse Module Devlog #1 – Building a Smart Greenhouse for Space Hello everyone! I’ve started working on Astro-Flora, an automated life-support greenhouse designed for extreme environments such as Mars and the Moon. The goal of this project is to create a system that can monitor plant health and environmental conditions while minimizing human intervention and conserving resources. What I’ve completed so far ✅ Designed the overall system architecture ✅ Developed the core Arduino software framework ✅ Implemented dual-zone soil moisture monitoring ✅ Added autonomous irrigation control for multiple growing zones ✅ Implemented climate regulation logic using temperature thresholds ✅ Added simulated day/night lighting cycles ✅ Built a crew access monitoring and logging system ✅ Added LCD-based telemetry display and status indicators ✅ Implemented reservoir monitoring and emergency safety alerts. Current Progress I estimate the project is around 50% complete. The software side is largely functional, and I am currently working on integrating and testing the hardware components. Challenges Managing multiple subsystems simultaneously without conflicts Designing a realistic space-habitat workflow Creating a modular code structure that can be expanded later. Why Astro-Flora? Future space missions will need reliable food production systems. Astro-Flora explores how automation, sensing, and resource management can help sustain crops in hostile environments."}]...
|
Title: ASTRO FLORA by @AshishPatel | Stardance
De Title: ASTRO FLORA by @AshishPatel | Stardance
Devlogs:
🌿 Astro-Flora: Automated Martian Greenhouse Module Devlog #1 – Building a Smart Greenhouse for Space Hello everyone! I’ve started working on Astro-Flora, an automated life-support greenhouse designed for extreme environments such as Mars and the Moon. The goal of this project is to create a system that can monitor plant health and environmental conditions while minimizing human intervention and conserving resources. What I’ve completed so far ✅ Designed the overall system architecture ✅ Developed the core Arduino software framework ✅ Implemented dual-zone soil moisture monitoring ✅ Added autonomous irrigation control for multiple growing zones ✅ Implemented climate regulation logic using temperature thresholds ✅ Added simulated day/night lighting cycles ✅ Built a crew access monitoring and logging system ✅ Added LCD-based telemetry display and status indicators ✅ Implemented reservoir monitoring and emergency safety alerts. Current Progress I estimate the project is around 50% complete. The software side is largely functional, and I am currently working on integrating and testing the hardware components. Challenges Managing multiple subsystems simultaneously without conflicts Designing a realistic space-habitat workflow Creating a modular code structure that can be expanded later. Why Astro-Flora? Future space missions will need reliable food production systems. Astro-Flora explores how automation, sensing, and resource management can help sustain crops in hostile environments.
Devlog #2: Systems Architecture & Circuit Map Complete! Hey everyone! 🚀 After a massive coding sprint yesterday, I have successfully locked down the core codebase for Astro-Flora and finalized the official hardware circuit schematic! Since Astro-Flora is designed to be an industrial-grade, multi-zone life support system for extreme space environments, I needed to make sure the hardware layout perfectly matches the decoupled state-machine architecture of my code. 🌌 Hardware Subsystem Breakdown I have organized the system architecture into four dedicated operational blocks: Sensor Array Inputs: Dual capacitive soil moisture sensors (Zone A on A0, Zone B on A1) set to monitor a desiccation threshold of 450, an atmospheric thermistor on A4, and a fluid reservoir level unit on A5 to prevent dry-pumping. User Interface & Audio Alerts: A 16x2 LCD display running via I2C (0x27) displaying live metrics alongside custom-rendered hex glyphs (Sprout, Sun, Moon, and Critical Warning). A master piezo buzzer sits on Pin 7 for cascading acoustic transaction tones. Digital Security Interlock: A biometric badge-swipe simulator connected to Pin 10 using internal pull-up resistors to log crew entries and exits seamlessly. Isolated Relay Actuators A 5-channel opto-isolated relay array connected to digital pins 2, 3, 4, 5, and 6 to safely drive high-power external loads (Solenoid water valves, grow lights, radiant heaters, and CO2 circulation fans). 🛡️ Critical Engineering Safeties Added While drafting the final blueprint, I made sure to add flyback diodes across the solenoid water valve channels. Since pumps and solenoids create heavy inductive voltage spikes when collapsing their magnetic fields, these diodes will keep the relay module and the Arduino Mega completely protected from back-EMF damage. The schematic is officially mapped, the code compiles flawlessly, and I’m ready to advance from the Design Phase to the Building Phase as soon as the review clears! Check out the full schematic below! 👇...
|
1793404276.57841
|
1794009076.57841
|
|
11394
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792929258.533734
|
1793793258.533734
|
|
11395
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792925393.0973346
|
1793789393.0973346
|
|
11396
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792889614.245475
|
1793753614.245475
|
|
11397
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792921740.3865452
|
1793785740.3865452
|
|
11398
|
F1 Strategist by @Vasco | Stardance
|
Vasco
|
0
|
18.32
|
0
|
[]
|
[{"post_id": 41930, "ts": "202 [{"post_id": 41930, "ts": "2026-08-06T13:32:48Z", "hours": 2.8669, "text": "I created a system that uses probability to determine when an event will occur. I also made another system where a variable increases from 0 to 20, incrementing by 1 every second. When the variable reaches the event’s assigned value, it sends a message indicating that the event has occurred."}, {"post_id": 39551, "ts": "2026-08-02T16:10:04Z", "hours": 2.1456, "text": "I created these pop-ups so the user can have more information and better control at the start of the race. Now the user can say their name and which tires the car should start with (according to the weather). I’m going to make one of these so the player knows if it’s a red flag, yellow flag, safety car, etc…"}, {"post_id": 39177, "ts": "2026-08-01T23:29:27Z", "hours": 1.4797, "text": "I created buttons called Pit Stop so that each team’s drivers know when they need to go into the pits. I’ll be adding more features later."}, {"post_id": 38524, "ts": "2026-07-31T23:15:35Z", "hours": 1.0733, "text": "I switched monitors and noticed that the formatting was extremely distorted! With Claude’s help, I managed to get it to look good on practically all devices, but the problem is that the simulator looks terrible on mobile phones."}, {"post_id": 37786, "ts": "2026-07-30T18:22:18Z", "hours": 0.4853, "text": "I’ve made it look better. Now each driver’s row displays their team’s color."}, {"post_id": 37759, "ts": "2026-07-30T17:49:09Z", "hours": 3.4772, "text": "I created a starting grid. It was difficult, but at least it works.Now I’m working on making it look better, and after that, the only thing left is to implement the main part of the website."}, {"post_id": 35996, "ts": "2026-07-27T20:00:01Z", "hours": 0.3394, "text": "I created the custom team section."}, {"post_id": 35956, "ts": "2026-07-27T18:49:55Z", "hours": 1.8694, "text": "Spent 2 hours debugging a bug… turns out I just forgot to save the code."}, {"post_id": 17650, "ts": "2026-06-28T15:12:23Z", "hours": 1.1458, "text": "I’m trying to make the website look better"}, {"post_id": 16914, "ts": "2026-06-27T13:58:05Z", "hours": 1.0503, "text": "I have started the back end, it’s taking a while, but at least is working"}, {"post_id": 16289, "ts": "2026-06-26T14:16:42Z", "hours": 0.4289, "text": "I’m going the 2 page, and the back-end"}, {"post_id": 16277, "ts": "2026-06-26T13:48:10Z", "hours": 0.4236, "text": "I’m making the first page user interface better because it wasn’t looking like i wanned"}, {"post_id": 15688, "ts": "2026-06-25T14:43:49Z", "hours": 0.2508, "text": "I’m now working in 2 second page, i’m going to make the back-end later"}, {"post_id": 15682, "ts": "2026-06-25T14:26:33Z", "hours": 0.5331, "text": "Finaly finished the main page User Interface"}, {"post_id": 15664, "ts": "2026-06-25T13:55:20Z", "hours": 0.4664, "text": "I’m working in a new User Interface, and later i’m going to to the back-end of the site"}, {"post_id": 15082, "ts": "2026-06-24T14:45:26Z", "hours": 0.2836, "text": "Spend 15 minutes trying to find a good font, is it cool?"}]...
|
Title: F1 Strategist by @Vasco | Stardance
Devlog Title: F1 Strategist by @Vasco | Stardance
Devlogs:
Spend 15 minutes trying to find a good font, is it cool?
I’m working in a new User Interface, and later i’m going to to the back-end of the site
Finaly finished the main page User Interface
I’m now working in 2 second page, i’m going to make the back-end later
I’m making the first page user interface better because it wasn’t looking like i wanned
I’m going the 2 page, and the back-end
I have started the back end, it’s taking a while, but at least is working
I’m trying to make the website look better
Spent 2 hours debugging a bug… turns out I just forgot to save the code.
I created the custom team section.
I created a starting grid. It was difficult, but at least it works.Now I’m working on making it look better, and after that, the only thing left is to implement the main part of the website.
I’ve made it look better. Now each driver’s row displays their team’s color.
I switched monitors and noticed that the formatting was extremely distorted! With Claude’s help, I managed to get it to look good on practically all devices, but the problem is that the simulator looks terrible on mobile phones.
I created buttons called Pit Stop so that each team’s drivers know when they need to go into the pits. I’ll be adding more features later.
I created these pop-ups so the user can have more information and better control at the start of the race. Now the user can say their name and which tires the car should start with (according to the weather). I’m going to make one of these so the player knows if it’s a red flag, yellow flag, safety car, etc…
I created a system that uses probability to determine when an event will occur. I also made another system where a variable increases from 0 to 20, incrementing by 1 every second. When the variable reaches the event’s assigned value, it sends a message indicating that the event has occurred....
|
1793210209.0966518
|
1793815009.0966518
|
|
11399
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792921971.6296873
|
1793785971.6296873
|
|
11400
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792885861.1733315
|
1793749861.1733315
|