|
29478
|
Spy Qlock by @GiuXo | Stardance
|
GiuXo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Spy Qlock by @GiuXo | Stardance
|
1793270986.6184442
|
1793875786.6184442
|
|
37860
|
Candice by @gauss | Stardance
|
gauss
|
0
|
3.8
|
0
|
[]
|
[{"post_id": 40509, "ts": "202 [{"post_id": 40509, "ts": "2026-08-04T02:59:05Z", "hours": 3.8017, "text": "Prototyping & Schematics I started working on a prototype of the watch on a breadboard, and began designing the PCB for the watch in KiCAD. Watch Schematic I decided to use RP-series MCUs for the watch, so I began developing the schematic for the watch’s PCB with a 3.3V VCC in mind. So far, I’ve attached a USB-C receptacle with nets for data and power. I also added support for 1S LiPo batteries (1S means single-cell in series, which has an average voltage of 3.7V). The 5V power line from the USB and the positive rail from the battery go through a P-channel enhancement-mode MOSFET. The purpose of the MOSFET is to ensure that current doesn’t flow into the battery when the USB is plugged in (at least, not in this part of the PCB/schematic), and that only one power line is responsible for powering the board at a time. Naturally, a buck converter is on the other end to step the voltage down to a nice and friendly 3.3V for the MCU. I also added a safe charging circuit for the LiPo at the end of my session. Breadboarding a Prototype What better way to have an off-grid watch than to use LoRa, a technology that can transmit short segments of data (like text messages or maybe really low-res images) over a kilometer away! I used two regular Pi Picos and connected a Wio SX1262 module to each via SPI. I then created a Pico C project and added RadioLib in CMake. The issue with RadioLib is that it’s targeted for Arduino, using functions like digitalWrite() and all that. To ensure this works in the Pico C SDK, I had to add a hardware abstraction layer, also known as a HAL. Basically, a HAL just translates functions from a different platform into the vernacular (Pico C, in this case), like gpio_put() . I created two executables: one for sending data and another for receiving it. The issue is that only every third send makes it across. This is likely due to some internal blocking mechanisms in RadioLib’s methods, but it can be fixed if I find a way to use interrupts. The issue can be explored in depth here ."}]...
|
Title: Candice by @gauss | Stardance
Devlogs:
Pro Title: Candice by @gauss | Stardance
Devlogs:
Prototyping & Schematics I started working on a prototype of the watch on a breadboard, and began designing the PCB for the watch in KiCAD. Watch Schematic I decided to use RP-series MCUs for the watch, so I began developing the schematic for the watch’s PCB with a 3.3V VCC in mind. So far, I’ve attached a USB-C receptacle with nets for data and power. I also added support for 1S LiPo batteries (1S means single-cell in series, which has an average voltage of 3.7V). The 5V power line from the USB and the positive rail from the battery go through a P-channel enhancement-mode MOSFET. The purpose of the MOSFET is to ensure that current doesn’t flow into the battery when the USB is plugged in (at least, not in this part of the PCB/schematic), and that only one power line is responsible for powering the board at a time. Naturally, a buck converter is on the other end to step the voltage down to a nice and friendly 3.3V for the MCU. I also added a safe charging circuit for the LiPo at the end of my session. Breadboarding a Prototype What better way to have an off-grid watch than to use LoRa, a technology that can transmit short segments of data (like text messages or maybe really low-res images) over a kilometer away! I used two regular Pi Picos and connected a Wio SX1262 module to each via SPI. I then created a Pico C project and added RadioLib in CMake. The issue with RadioLib is that it’s targeted for Arduino, using functions like digitalWrite() and all that. To ensure this works in the Pico C SDK, I had to add a hardware abstraction layer, also known as a HAL. Basically, a HAL just translates functions from a different platform into the vernacular (Pico C, in this case), like gpio_put() . I created two executables: one for sending data and another for receiving it. The issue is that only every third send makes it across. This is likely due to some internal blocking mechanisms in RadioLib’s methods, but it can be fixed if I find a way to use interrupts. The issue can be explored in depth here ....
|
1793270985.7555506
|
1793875785.7555506
|
|
24721
|
SPKSB Lab Website by @vavrup | Stardance
|
vavrup
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: SPKSB Lab Website by @vavrup | Stardance
|
1793270983.9772487
|
1793875783.9772487
|
|
638
|
My first slack bot! by @Shirley | Stardance
|
Shirley
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Shirley | Stardance
|
1793270983.09113
|
1793875783.09113
|
|
24198
|
My first slack bot! by @svara_wase | Stardance
|
svara_wase
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @svara_wase | Starda Title: My first slack bot! by @svara_wase | Stardance...
|
1793270981.2855377
|
1793875781.2855377
|
|
2968
|
Animation Macropad by @DungeonWolf | Stardance
|
DungeonWolf
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Animation Macropad by @DungeonWolf | Starda Title: Animation Macropad by @DungeonWolf | Stardance...
|
1793270980.37393
|
1793875780.37393
|
|
39639
|
My very own WebOS by @frankly2012 | Stardance
|
frankly2012
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @frankly2012 | Stardan Title: My very own WebOS by @frankly2012 | Stardance...
|
1793270977.448789
|
1793875777.448789
|
|
1714
|
GAIA by @Ved | Stardance
|
Ved
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: GAIA by @Ved | Stardance
|
1793270976.5944047
|
1793875776.5944047
|
|
29830
|
My first slack bot! by @leaderofthefuture | Starda My first slack bot! by @leaderofthefuture | Stardance...
|
leaderofthefuture
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @leaderofthefuture | Title: My first slack bot! by @leaderofthefuture | Stardance...
|
1793270974.5708675
|
1793875774.5708675
|
|
5807
|
Untitled by @Kiwiii | Stardance
|
Kiwiii
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Kiwiii | Stardance
|
1793270973.6948533
|
1793875773.6948533
|
|
908
|
My awesome macropad! by @Munnisparkle | Stardance
|
Munnisparkle
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Munnisparkle | Sta Title: My awesome macropad! by @Munnisparkle | Stardance...
|
1793270972.7992368
|
1793875772.7992368
|
|
8033
|
Untitled project by @Hoondy | Stardance
|
Hoondy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Hoondy | Stardance
|
1793270971.9277737
|
1793875771.9277737
|
|
3342
|
My awesome macropad! by @shaurwadhawan | Stardance
|
shaurwadhawan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @shaurwadhawan | St Title: My awesome macropad! by @shaurwadhawan | Stardance...
|
1793270970.1193345
|
1793875770.1193345
|
|
10286
|
Fortran browser by @Maxwell-l-hack | Stardance
|
Maxwell-l-hack
|
0
|
3.78
|
0
|
[]
|
[{"post_id": 10955, "ts": "202 [{"post_id": 10955, "ts": "2026-06-17T23:30:16Z", "hours": 1.7106, "text": "Finally got the window to show up, speeding up compilation has the downside of having to remember to add the function names when calling the module."}, {"post_id": 4604, "ts": "2026-06-07T23:29:57Z", "hours": 1.3908, "text": "I setup the prompt to ask if your in a terminal or in the future GUI browser (hopeful) and fixed the URL input after breaking it. I am still noodling about how to implement the HTML tag stripper so you could view the text on the page as a base from of web browsing."}, {"post_id": 3874, "ts": "2026-06-06T23:17:39Z", "hours": 0.6831, "text": "I made the main program fetch the Hacklub website’s homepage. Here’s part of it."}]...
|
Title: Fortran browser by @Maxwell-l-hack | Starda Title: Fortran browser by @Maxwell-l-hack | Stardance
Devlogs:
I made the main program fetch the Hacklub website’s homepage. Here’s part of it.
I setup the prompt to ask if your in a terminal or in the future GUI browser (hopeful) and fixed the URL input after breaking it. I am still noodling about how to implement the HTML tag stripper so you could view the text on the page as a base from of web browsing.
Finally got the window to show up, speeding up compilation has the downside of having to remember to add the function names when calling the module....
|
1793270969.2261474
|
1793875769.2261474
|
|
6346
|
7th-Hour by @vikasharma | Stardance
|
vikasharma
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 7th-Hour by @vikasharma | Stardance
|
1793270968.3765938
|
1793875768.3765938
|
|
8762
|
spoticker by @akisl | Stardance
|
akisl
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: spoticker by @akisl | Stardance
|
1793270967.514129
|
1793875767.514129
|
|
3325
|
FlorrFanGame by @EricSki | Stardance
|
EricSki
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: FlorrFanGame by @EricSki | Stardance
|
1793270966.6461256
|
1793875766.6461256
|
|
5937
|
My awesome macropad! by @ethan_soh | Stardance
|
ethan_soh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @ethan_soh | Starda Title: My awesome macropad! by @ethan_soh | Stardance...
|
1793270965.750431
|
1793875765.750431
|
|
18012
|
CircuitForge by @leotangyes | Stardance
|
leotangyes
|
0
|
8.44
|
0
|
[]
|
[{"post_id": 9007, "ts": "2026 [{"post_id": 9007, "ts": "2026-06-15T00:49:44Z", "hours": 8.4394, "text": "My team and I built an AI-powered system that converts breadboard prototypes into manufacturable PCB designs. The goal of our project is to help makers and engineers bridge the gap between rapid prototyping and production by automating much of the PCB design process. Our system combines three sources of information: a CubeMX configuration file that specifies the microcontroller and pin assignments, a photo of the breadboard prototype, and a component list. Using the DigiKey API, we retrieve datasheets and product images for each component, which provide additional context for our computer vision pipeline. We then use the Gemini API to reason over all of this information, infer the circuit structure, and generate a schematic and PCB layout. A second Gemini agent is responsible for abstracting away prototyping hardware and extracting only the essential components needed for manufacturing. For example, if the prototype uses an STM32 development board, the agent replaces it with the underlying STM32 microcontroller and its required supporting circuitry. Similarly, if the prototype uses a microphone breakout board, the agent identifies the actual microphone component and removes the breakout hardware. This ensures the final design reflects a real manufacturable circuit rather than a prototyping setup. The final output of our system is a KiCad PCB file that can be opened, edited, and manufactured using the KiCad ecosystem. By combining computer vision, large language models, and hardware design tools, our project streamlines the process of turning a messy prototype into a clean, manufacturable PCB. Next steps for the project include automating trace routing while respecting electrical and layout constraints, improving the reliability of schematic generation, and extending the system to automatically insert necessary supporting components such as decoupling capacitors and other small passive components required for stable real-world operation. These improvements aim to make the system fully end-to-end and production-ready."}]...
|
Title: CircuitForge by @leotangyes | Stardance
De Title: CircuitForge by @leotangyes | Stardance
Devlogs:
My team and I built an AI-powered system that converts breadboard prototypes into manufacturable PCB designs. The goal of our project is to help makers and engineers bridge the gap between rapid prototyping and production by automating much of the PCB design process. Our system combines three sources of information: a CubeMX configuration file that specifies the microcontroller and pin assignments, a photo of the breadboard prototype, and a component list. Using the DigiKey API, we retrieve datasheets and product images for each component, which provide additional context for our computer vision pipeline. We then use the Gemini API to reason over all of this information, infer the circuit structure, and generate a schematic and PCB layout. A second Gemini agent is responsible for abstracting away prototyping hardware and extracting only the essential components needed for manufacturing. For example, if the prototype uses an STM32 development board, the agent replaces it with the underlying STM32 microcontroller and its required supporting circuitry. Similarly, if the prototype uses a microphone breakout board, the agent identifies the actual microphone component and removes the breakout hardware. This ensures the final design reflects a real manufacturable circuit rather than a prototyping setup. The final output of our system is a KiCad PCB file that can be opened, edited, and manufactured using the KiCad ecosystem. By combining computer vision, large language models, and hardware design tools, our project streamlines the process of turning a messy prototype into a clean, manufacturable PCB. Next steps for the project include automating trace routing while respecting electrical and layout constraints, improving the reliability of schematic generation, and extending the system to automatically insert necessary supporting components such as decoupling capacitors and other small passive components required for stable real-world operation. These improvements aim to make the system fully end-to-end and production-ready....
|
1793270964.8490615
|
1793875764.8490615
|
|
36542
|
My very own WebOS by @TheDailyError | Stardance
|
TheDailyError
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @TheDailyError | Stard Title: My very own WebOS by @TheDailyError | Stardance...
|
1793270961.819729
|
1793875761.819729
|
|
11132
|
Fencing Gesture Tracker by @Timmyhuhu | Stardance
|
Timmyhuhu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Fencing Gesture Tracker by @Timmyhuhu | Sta Title: Fencing Gesture Tracker by @Timmyhuhu | Stardance...
|
1793270960.9572198
|
1793875760.9572198
|
|
7312
|
HusKeyboard by @FiferWasHere | Stardance
|
FiferWasHere
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: HusKeyboard by @FiferWasHere | Stardance
|
1793270960.093767
|
1793875760.093767
|
|
22542
|
Untitled by @Thiha | Stardance
|
Thiha
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Thiha | Stardance
|
1793270958.2845852
|
1793875758.2845852
|
|
8103
|
App for students in Czechia to help them prepaire App for students in Czechia to help them prepaire for entrance exams on high schools. by @krdnc | Stardance...
|
krdnc
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: App for students in Czechia to help them pr Title: App for students in Czechia to help them prepaire for entrance exams on high schools. by @krdnc | Stardance...
|
1793270957.4216857
|
1793875757.4216857
|
|
7358
|
Python code by @PTF | Stardance
|
PTF
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Python code by @PTF | Stardance
|
1793270955.1055746
|
1793875755.1055746
|
|
30719
|
New Tab Page by @kablankooo | Stardance
|
kablankooo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: New Tab Page by @kablankooo | Stardance
|
1793270954.2033195
|
1793875754.2033195
|
|
14978
|
My first slack bot! by @Mee | Stardance
|
Mee
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Mee | Stardance
|
1793270950.9175267
|
1793875750.9175267
|
|
31607
|
Vehicle data logger by @danielz | Stardance
|
danielz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Vehicle data logger by @danielz | Stardance
|
1793270950.056158
|
1793875750.056158
|
|
4770
|
My awesome macropad! by @Ryusei | Stardance
|
Ryusei
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Ryusei | Stardance
|
1793270949.1733274
|
1793875749.1733274
|
|
7742
|
Untitled by @richie | Stardance
|
richie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @richie | Stardance
|
1793270947.3910959
|
1793875747.3910959
|
|
5172
|
Personal Website by @CHIef | Stardance
|
CHIef
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Personal Website by @CHIef | Stardance
|
1793270946.4936397
|
1793875746.4936397
|
|
12466
|
My awesome macropad! by @Bestlee | Stardance
|
Bestlee
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Bestlee | Stardanc Title: My awesome macropad! by @Bestlee | Stardance...
|
1793270945.6292558
|
1793875745.6292558
|
|
27256
|
Mathify - AI Maths Test Analyzer by @brijeshkumar7 Mathify - AI Maths Test Analyzer by @brijeshkumar724282 | Stardance...
|
brijeshkumar724282
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Mathify - AI Maths Test Analyzer by @brijes Title: Mathify - AI Maths Test Analyzer by @brijeshkumar724282 | Stardance...
|
1793270944.7462616
|
1793875744.7462616
|
|
8487
|
chronovisor by @subhansh | Stardance
|
|
0
|
18.05
|
0
|
[]
|
[{"post_id": 33951, "ts": "202 [{"post_id": 33951, "ts": "2026-07-24T09:14:45Z", "hours": 7.6253, "text": "Today was about giving the satellite engine a skeleton key. The satellite engine could see, but it couldn’t understand . Day 2 was all about layering context on top of context until patterns start to surface. Environmental Layer First ISRIC SoilGrids v2.0: Pulled clay percentage, sand, silt, pH, and organic carbon. Every number comes with uncertainty bounds because soil data is never clean. USGS Earthquake Catalogs: If a location has had 20+ quakes, that’s active fault territory and anything buried is scrambled. WorldPop Population Density: Tells you whether you’re looking at farmland or wilderness. Water Table Depth: Estimated from elevation. Shallow groundwater rots organic material; deep water means preservation. Archaeological Databases Wikidata & Pleiades: Hit Wikidata SPARQL directly for Pleiades entries—that’s every known archaeological site in the ancient world. GBIF Species Occurrence: Cross-referenced with GBIF data (civilizations cluster near water and arable land, and species distribution proves it). NOAA World Magnetic Model: Plugged in NOAA’s WMM for IGRF magnetic field calculations—buried structures distort local magnetic fields. NASA VIIRS Nighttime Lights (VNP46A2): Added night light data to map modern human activity patterns. Geospatial Helpers: Integrated OpenTopography DEM availability checks, geocoding via Nominatim, and full site suitability scoring based on known site proximity, climate, and magnetic anomalies. Web Archive Evidence Wayback Machine CDX API: Search by place name and coordinates, running archaeological keyword matching across archived pages. OSM Overpass: Querying historic and heritage feature tags. Building Density Analysis: Sparse buildings in a fertile area = something’s off. Cross-Reference Engine Pleiades, Wikidata, GBIF, and VIIRS nightlights all get matched against each other. If an ancient settlement shows up in three sources but the area is now empty, that’s a red flag. Temporal Trends: Pulled temperature trends from Open-Meteo (2020–2023) to analyze climate shifts. Batch Scanning: Built batch capabilities so you can process 20 sets of coordinates simultaneously. Fusion Engine — The Actual Brain Took every data source and wired them into a 7-component weighted scoring system: Satellite Anomaly Score ( 35% ) Signal strength × data quality × inverse correlation bonus when NDVI/NDWI/thermal agree. Soil Preservation ( 20% ) Clay > 350g/kg = +35%, Sand > 600g/kg = -25%, pH 6.5–8.0 sweet spot. Seismic Filter ( 10% ) 20+ quakes = -25%, Moderate = -10%, Quiet = neutral. Water Table Depth ( 10% ) <5m = -20%, >30m = +20%, No data = +30%. OSM Historic Context ( 10% ) Historic features nearby = +30%, Dense = neutral, Sparse = survey opportunity. Temporal Consistency ( 10% ) Significant NDVI trend + $R^2 > 0.3$ = +30%, Change events = +5%/event. Web Archive Evidence ( 5% ) Archaeological content in history = +55%, Multiple hits = +25%."}, {"post_id": 30711, "ts": "2026-07-18T14:53:52Z", "hours": 10.4211, "text": "Chronovisor — Devlog 1 🍓😺 So I had an idea that probably sounds a bit out there at first glance: What if you could point at any spot on Earth and get a read on whether something is buried underneath? And what if you could do it without ground-penetrating radar, drones, or anything physical—just satellite data and a bunch of free APIs? I decided to see if I could actually build it. I’m calling it Chronovisor . What I actually did The core of the project is a satellite data engine that pulls imagery directly from Google Earth Engine. Right now, I’m tapping into Sentinel-2 data (10m resolution, available from 2017 onward) and calculating spectral indices directly from the raw band data. I’m tracking: NDVI (Vegetation health) NDWI (Moisture levels) NDBI (Built-up/urban areas) Plus: BSI, SAVI, and NDMI. The underlying theory is straightforward: buried structures mess with the surface. A stone foundation stops roots from growing properly. Ancient walls alter water drainage. Different materials retain heat differently. If you can read those subtle patterns from orbit over time, you can potentially spot an archaeological site or a forgotten structure without ever setting foot on the ground. For the heavy lifting, I built an anomaly detection pipeline that flags anything sitting two standard deviations away from the mean across the time series. The math isn’t overly complex, but it’s highly effective. When a specific coordinate consistently shows up as “weird” across multiple independent satellite passes, you know you’ve got a real signal. The piece I’m most proud of is the structural probability scoring . I detrend the NDVI and thermal data to strip out seasonal spikes, then check if they’re inversely correlated. If you have uncharacteristically low vegetation right where the thermal signature is unusually high (or vice versa), that’s the classic signature of subsurface interference. The code evaluates this and outputs a score from 0 to 100. It doesn’t declare a definitive “find”—it just screams, “Hey, look closer at this exact spot.” On the infrastructure side, I set up: A FastAPI backend utilizing a two-tier cache (in-memory + disk) with SHA-256 hashing to keep things snappy. A clean CLI entry point for quick scripting. A Leaflet-based frontend styled in a dark theme (obviously). Managing Expectations: What it actually does I want to be completely transparent about what this tool is—and what it isn’t. This system does not tell you what is underground. It analyzes surface patterns and scores how likely it is that something is disrupting them. When the system flags a “possible buried structure,” it is strictly saying that the vegetation and thermal patterns match the footprint of subsurface interference. Nothing more. The signal processor uses real analytical tools—Fast Fourier Transforms (FFT), harmonic detection, and autocorrelation. However, it requires legitimate sensor data to function. It doesn’t conjure findings out of thin air, and the EM field mapping elements are tools for processing input data, not magic discovery engines. What’s next Right now, the satellite engine is great at spotting anomalies, but it has zero context about the ground it’s looking at. Next up, I’m building connectors for: Local soil composition data Seismic activity logs Water table estimates An archaeological database queried via Wikidata SPARQL. The goal is to evolve the output from a basic “this spot has weird NDVI” into something incredibly actionable: “This spot has a strange NDVI anomaly, sits on a clay soil type known to preserve structures, is located within 2km of a known ancient settlement, and suffers from low seismic noise.” That’s the kind of signal that gets interesting. Stay tuned."}]...
|
Title: chronovisor by @subhansh | Stardance
Devlo Title: chronovisor by @subhansh | Stardance
Devlogs:
Chronovisor — Devlog 1 🍓😺 So I had an idea that probably sounds a bit out there at first glance: What if you could point at any spot on Earth and get a read on whether something is buried underneath? And what if you could do it without ground-penetrating radar, drones, or anything physical—just satellite data and a bunch of free APIs? I decided to see if I could actually build it. I’m calling it Chronovisor . What I actually did The core of the project is a satellite data engine that pulls imagery directly from Google Earth Engine. Right now, I’m tapping into Sentinel-2 data (10m resolution, available from 2017 onward) and calculating spectral indices directly from the raw band data. I’m tracking: NDVI (Vegetation health) NDWI (Moisture levels) NDBI (Built-up/urban areas) Plus: BSI, SAVI, and NDMI. The underlying theory is straightforward: buried structures mess with the surface. A stone foundation stops roots from growing properly. Ancient walls alter water drainage. Different materials retain heat differently. If you can read those subtle patterns from orbit over time, you can potentially spot an archaeological site or a forgotten structure without ever setting foot on the ground. For the heavy lifting, I built an anomaly detection pipeline that flags anything sitting two standard deviations away from the mean across the time series. The math isn’t overly complex, but it’s highly effective. When a specific coordinate consistently shows up as “weird” across multiple independent satellite passes, you know you’ve got a real signal. The piece I’m most proud of is the structural probability scoring . I detrend the NDVI and thermal data to strip out seasonal spikes, then check if they’re inversely correlated. If you have uncharacteristically low vegetation right where the thermal signature is unusually high (or vice versa), that’s the classic signature of subsurface interference. The code evaluates this and outputs a score from 0 to 100. It doesn’t declare a definitive “find”—it just screams, “Hey, look closer at this exact spot.” On the infrastructure side, I set up: A FastAPI backend utilizing a two-tier cache (in-memory + disk) with SHA-256 hashing to keep things snappy. A clean CLI entry point for quick scripting. A Leaflet-based frontend styled in a dark theme (obviously). Managing Expectations: What it actually does I want to be completely transparent about what this tool is—and what it isn’t. This system does not tell you what is underground. It analyzes surface patterns and scores how likely it is that something is disrupting them. When the system flags a “possible buried structure,” it is strictly saying that the vegetation and thermal patterns match the footprint of subsurface interference. Nothing more. The signal processor uses real analytical tools—Fast Fourier Transforms (FFT), harmonic detection, and autocorrelation. However, it requires legitimate sensor data to function. It doesn’t conjure findings out of thin air, and the EM field mapping elements are tools for processing input data, not magic discovery engines. What’s next Right now, the satellite engine is great at spotting anomalies, but it has zero context about the ground it’s looking at. Next up, I’m building connectors for: Local soil composition data Seismic activity logs Water table estimates An archaeological database queried via Wikidata SPARQL. The goal is to evolve the output from a basic “this spot has weird NDVI” into something incredibly actionable: “This spot has a strange NDVI anomaly, sits on a clay soil type known to preserve structures, is located within 2km of a known ancient settlement, and suffers from low seismic noise.” That’s the kind of signal that gets interesting. Stay tuned.
Today was about giving the satellite engine a skeleton key. The satellite engine could see, but it couldn’t understand . Day 2 was all about layering context on top of context until patterns start to surface. Environmental Layer First ISRIC SoilGrids v2.0: Pulled clay percentage, sand, silt, pH, and organic carbon. Every number comes with uncertainty bounds because soil data is never clean. USGS Earthquake Catalogs: If a location has had 20+ quakes, that’s active fault territory and anything buried is scrambled. WorldPop Population Density: Tells you whether you’re looking at farmland or wilderness. Water Table Depth: Estimated from elevation. Shallow groundwater rots organic material; deep water means preservation. Archaeological Databases Wikidata & Pleiades: Hit Wikidata SPARQL directly for Pleiades entries—that’s every known archaeological site in the ancient world. GBIF Species Occurrence: Cross-referenced with GBIF data (civilizations cluster near water and arable land, and species distribution proves it). NOAA World Magnetic Model: Plugged in NOAA’s WMM for IGRF magnetic field calculations—buried structures distort local magnetic fields. NASA VIIRS Nighttime Lights (VNP46A2): Added night light data to map modern human activity patterns. Geospatial Helpers: Integrated OpenTopography DEM availability checks, geocoding via Nominatim, and full site suitability scoring based on known site proximity, climate, and magnetic anomalies. Web Archive Evidence Wayback Machine CDX API: Search by place name and coordinates, running archaeological keyword matching across archived pages. OSM Overpass: Querying historic and heritage feature tags. Building Density Analysis: Sparse buildings in a fertile area = something’s off. Cross-Reference Engine Pleiades, Wikidata, GBIF, and VIIRS nightlights all get matched against each other. If an ancient settlement shows up in three sources but the area is now empty, that’s a red flag. Temporal Trends: Pulled temperature trends from Open-Meteo (2020–2023) to analyze climate shifts. Batch Scanning: Built batch capabilities so you can process 20 sets of coordinates simultaneously. Fusion Engine — The Actual Brain Took every data source and wired them into a 7-component weighted scoring system: Satellite Anomaly Score ( 35% ) Signal strength × data quality × inverse correlation bonus when NDVI/NDWI/thermal agree. Soil Preservation ( 20% ) Clay > 350g/kg = +35%, Sand > 600g/kg = -25%, pH 6.5–8.0 sweet spot. Seismic Filter ( 10% ) 20+ quakes = -25%, Moderate = -10%, Quiet = neutral. Water Table Depth ( 10% ) <5m = -20%, >30m = +20%, No data = +30%. OSM Historic Context ( 10% ) Historic features nearby = +30%, Dense = neutral, Sparse = survey opportunity. Temporal Consistency ( 10% ) Significant NDVI trend + $R^2 > 0.3$ = +30%, Change events = +5%/event. Web Archive Evidence ( 5% ) Archaeological content in history = +55%, Multiple hits = +25%....
|
1793270942.7042906
|
1793875742.7042906
|
|
8431
|
Cosmic by @anavshah2008 | Stardance
|
anavshah2008
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Cosmic by @anavshah2008 | Stardance
|
1793270940.6919143
|
1793875740.6919143
|
|
24662
|
Dungeon Caster by @Zave | Stardance
|
Zave
|
0
|
23.62
|
0
|
[]
|
[{"post_id": 25672, "ts": "202 [{"post_id": 25672, "ts": "2026-07-10T02:47:37Z", "hours": 10.2972, "text": "Tiles along with most other sprites have been completed! Most of my time during the process was trying different looking floor and background textures, but I’m okay with where it ended up. I’ll be working on implementing the final two spells as well as creating some of the earlier levels that lead up to the first two. Once those have been completed I’ll be working on the spell animations. The devlogs in the future will hopefully have smaller breaks between them. I wanted to finish the tiles before I made this one, but I was kind of struggling the with designs so it took longer than I would’ve liked."}, {"post_id": 17304, "ts": "2026-06-28T01:05:00Z", "hours": 9.9022, "text": "Player sprites are done! All of the animations and sprites for the wizard have been completed. All current animations have been implemented into the game. The movement has been to tweaked so that it would feel a little better to play. Before it felt too fast and snappy and now it feels a little more controllable, but will still likely need some changing. I was also able to implement a dash! It will likely be the last spell to be added for a bit as art is going to be my main focus going forward. I’d like to make some levels to play around with the current mechanics I have implemented before adding more. In the future the animations for the abilities will have spells going on around the player, but the art for them is yet to be done so for now enjoy the color changing wizard :D"}, {"post_id": 16479, "ts": "2026-06-26T20:32:37Z", "hours": 2.2964, "text": "Devlog #2: Hello! I’ve been mostly working on teaching myself pixel art so that I could make the sprites for the game. I also was able to add in a double jump mechanic and collectable. After this I plan to continue working sprites and focusing on getting the dash implemented."}, {"post_id": 15383, "ts": "2026-06-25T00:36:32Z", "hours": 1.1281, "text": "Devlog #1: Hello! Today I just wanted to get something to start with so I focused on creating an area where I could test mechanics and added in some basic movement. Other than that I spent some time planning the general outline of the game and figuring out what types of spells I could add in for movement abilities. The timelapse below shows some of the planning."}]...
|
Title: Dungeon Caster by @Zave | Stardance
Devlog Title: Dungeon Caster by @Zave | Stardance
Devlogs:
Devlog #1: Hello! Today I just wanted to get something to start with so I focused on creating an area where I could test mechanics and added in some basic movement. Other than that I spent some time planning the general outline of the game and figuring out what types of spells I could add in for movement abilities. The timelapse below shows some of the planning.
Devlog #2: Hello! I’ve been mostly working on teaching myself pixel art so that I could make the sprites for the game. I also was able to add in a double jump mechanic and collectable. After this I plan to continue working sprites and focusing on getting the dash implemented.
Player sprites are done! All of the animations and sprites for the wizard have been completed. All current animations have been implemented into the game. The movement has been to tweaked so that it would feel a little better to play. Before it felt too fast and snappy and now it feels a little more controllable, but will still likely need some changing. I was also able to implement a dash! It will likely be the last spell to be added for a bit as art is going to be my main focus going forward. I’d like to make some levels to play around with the current mechanics I have implemented before adding more. In the future the animations for the abilities will have spells going on around the player, but the art for them is yet to be done so for now enjoy the color changing wizard :D
Tiles along with most other sprites have been completed! Most of my time during the process was trying different looking floor and background textures, but I’m okay with where it ended up. I’ll be working on implementing the final two spells as well as creating some of the earlier levels that lead up to the first two. Once those have been completed I’ll be working on the spell animations. The devlogs in the future will hopefully have smaller breaks between them. I wanted to finish the tiles before I made this one, but I was kind of struggling the with designs so it took longer than I would’ve liked....
|
1793270939.81788
|
1793875739.81788
|
|
13686
|
UE5MCP by @eashanbabber | Stardance
|
eashanbabber
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: UE5MCP by @eashanbabber | Stardance
|
1793270938.9214373
|
1793875738.9214373
|
|
1614
|
Untitled project by @raven | Stardance
|
raven
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @raven | Stardance
|
1793270938.035317
|
1793875738.035317
|
|
7650
|
Project Eclipse by @Nicormu | Stardance
|
Nicormu
|
0
|
24.76
|
0
|
[]
|
[{"post_id": 74252, "ts": "202 [{"post_id": 74252, "ts": "2026-09-27T02:06:11Z", "hours": 1.7828, "text": "Hiiii, Please say hello to the new liquid colorrrr (it also shinesssssss), the new crafting button, the new exit button and finally, the skin for the crafting tableeeeeeeee. Hope you like ittt <3"}, {"post_id": 73390, "ts": "2026-09-25T01:45:53Z", "hours": 2.8564, "text": "Hiiiiiii everyoneeeeee, I think the crafting station is getting a great advancement and is getting really goodddddddddd. I will add a color change when the crafting is available and see what can be improved before starting with quests or the economy of the game"}, {"post_id": 72471, "ts": "2026-09-23T01:10:03Z", "hours": 2.5333, "text": "Hiiiii, I have worked a bit and started a refactor on the crafting system, I still have issues. I dont like how the system is right now, I will think new ideas"}, {"post_id": 67342, "ts": "2026-09-13T12:45:07Z", "hours": 9.1197, "text": "Hi everyoneee, I was busy and stressed out with school and many other things, but I think I will start again with the development of Project Eclipse. By now, I have only organized the project and refactored almost every system."}, {"post_id": 18779, "ts": "2026-06-29T23:54:30Z", "hours": 2.4675, "text": "Devlog #5 I have been struggling with the crafting system. I cannot even describe the problem I have right now. Almost all the time recorded is trying the system and nothing to work. After I gived up with that, I organized the project :D"}, {"post_id": 15416, "ts": "2026-06-25T01:50:42Z", "hours": 0.4908, "text": "#Devlog #4 Hi guysss! I have been very busy these days but I have tried my best. I had added the sprites of the beaker and coal and started with the crafting system allowing dragging (not working completely) from the inventory. I will try all as I can to work more and improve the project :D"}, {"post_id": 10385, "ts": "2026-06-17T02:09:42Z", "hours": 2.705, "text": "Devlog #3 Hi everyone! Over the past few days, I’ve been working on the inventory and recipe system. I ran into some issues with Unity not saving my progress, so I had to rebuild everything multiple times (about 2 or 3 times 😭). On the bright side, I’m really happy with how the Notebook and Post-It sprites turned out. Now that the inventory system is mostly in place, I think I’ll be moving on to the crafting station."}, {"post_id": 7792, "ts": "2026-06-13T00:28:26Z", "hours": 1.9114, "text": "Devlog #2 Hi guys, I have been busy with the school and had work a little this week. The things I added is an inventory system, a recollection system and a prototype of the crafting station. I had problems with the inventory system and panel to make it look as I wanted to. Will keep working"}, {"post_id": 4451, "ts": "2026-06-07T19:33:52Z", "hours": 0.8914, "text": "Devlog #1 - The Beginning Project Eclipse is officially in development. This week I created the Garage scene, implemented player movement, and started working on object interactions. The biggest challenge was getting the interaction system to work correctly, which led to several debugging sessions before objects could be detected properly. Next, I’ll focus on finishing interactions and creating the first machine prototype"}]...
|
Title: Project Eclipse by @Nicormu | Stardance
De Title: Project Eclipse by @Nicormu | Stardance
Devlogs:
Devlog #1 - The Beginning Project Eclipse is officially in development. This week I created the Garage scene, implemented player movement, and started working on object interactions. The biggest challenge was getting the interaction system to work correctly, which led to several debugging sessions before objects could be detected properly. Next, I’ll focus on finishing interactions and creating the first machine prototype
Devlog #2 Hi guys, I have been busy with the school and had work a little this week. The things I added is an inventory system, a recollection system and a prototype of the crafting station. I had problems with the inventory system and panel to make it look as I wanted to. Will keep working
Devlog #3 Hi everyone! Over the past few days, I’ve been working on the inventory and recipe system. I ran into some issues with Unity not saving my progress, so I had to rebuild everything multiple times (about 2 or 3 times 😭). On the bright side, I’m really happy with how the Notebook and Post-It sprites turned out. Now that the inventory system is mostly in place, I think I’ll be moving on to the crafting station.
#Devlog #4 Hi guysss! I have been very busy these days but I have tried my best. I had added the sprites of the beaker and coal and started with the crafting system allowing dragging (not working completely) from the inventory. I will try all as I can to work more and improve the project :D
Devlog #5 I have been struggling with the crafting system. I cannot even describe the problem I have right now. Almost all the time recorded is trying the system and nothing to work. After I gived up with that, I organized the project :D
Hi everyoneee, I was busy and stressed out with school and many other things, but I think I will start again with the development of Project Eclipse. By now, I have only organized the project and refactored almost every system.
Hiiiii, I have worked a bit and started a refactor on the crafting system, I still have issues. I dont like how the system is right now, I will think new ideas
Hiiiiiii everyoneeeeee, I think the crafting station is getting a great advancement and is getting really goodddddddddd. I will add a color change when the crafting is available and see what can be improved before starting with quests or the economy of the game
Hiiii, Please say hello to the new liquid colorrrr (it also shinesssssss), the new crafting button, the new exit button and finally, the skin for the crafting tableeeeeeeee. Hope you like ittt <3...
|
1793270935.6192386
|
1793875735.6192386
|
|
2024
|
My first slack bot! by @fianko | Stardance
|
fianko
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @fianko | Stardance
|
1793270934.7241666
|
1793875734.7241666
|
|
15999
|
My awesome macropad! by @achu | Stardance
|
achu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @achu | Stardance
|
1793270932.6148129
|
1793875732.6148129
|
|
3958
|
My awesome macropad! by @Allura | Stardance
|
Allura
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Allura | Stardance
|
1793270930.3203452
|
1793875730.3203452
|
|
40038
|
My own site! by @eyosyas | Stardance
|
eyosyas
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @eyosyas | Stardance
|
1793270928.200428
|
1793875728.200428
|
|
483
|
Coeur Cafe Website by @Lolo | Stardance
|
Lolo
|
0
|
0.48
|
0
|
[]
|
[{"post_id": 8679, "ts": "2026 [{"post_id": 8679, "ts": "2026-06-14T12:48:16Z", "hours": 0.4764, "text": "Started making website"}]...
|
Title: Coeur Cafe Website by @Lolo | Stardance
De Title: Coeur Cafe Website by @Lolo | Stardance
Devlogs:
Started making website...
|
1793270923.9973798
|
1793875723.9973798
|
|
17540
|
My awesome macropad! by @akshaya | Stardance
|
akshaya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @akshaya | Stardanc Title: My awesome macropad! by @akshaya | Stardance...
|
1793270922.2453291
|
1793875722.2453291
|
|
6498
|
Untitled by @tautikghosh | Stardance
|
tautikghosh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @tautikghosh | Stardance
|
1793270921.3867812
|
1793875721.3867812
|
|
31216
|
My very own WebOS by @Nodirbek | Stardance
|
Nodirbek
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Nodirbek | Stardance
|
1793270919.5780058
|
1793875719.5780058
|
|
31742
|
My own site! by @theyoungengineeer | Stardance
|
theyoungengineeer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @theyoungengineeer | Starda Title: My own site! by @theyoungengineeer | Stardance...
|
1793270918.6925335
|
1793875718.6925335
|
|
29856
|
My awesome macropad! by @sevi | Stardance
|
sevi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @sevi | Stardance
|
1793270917.5440662
|
1793875717.5440662
|
|
10682
|
Movement Shooter by @balu | Stardance
|
balu
|
0
|
73.89
|
0
|
[]
|
[{"post_id": 16878, "ts": "202 [{"post_id": 16878, "ts": "2026-06-27T12:13:45Z", "hours": 7.3047, "text": "Implemented proper client-side interpolation, made everything tickrate independent so you can host servers with 30hz, 64hz and even 128hz tickrate. Also changed the adaptive buffers to handle the worse internet connections, you can barely notice the rubberbanding now on a bad 4G connection for example. Here’s a test of peeker’s advantage on LAN, I measured about 15-20ms of latency for a player’s actions showing up to all other players on a stable 0ms connection"}, {"post_id": 15421, "ts": "2026-06-25T01:57:52Z", "hours": 4.8883, "text": "MASSIVE NETCODE IMPROVEMENTS I made changes to how the client adjusts its input clock, instead of targeting discrete ticks, it targets time now so we can get even less latency and allows to provide a better experience for both players with a stable and poor internet connection!! This is the same system that CS2 uses"}, {"post_id": 12655, "ts": "2026-06-20T17:56:38Z", "hours": 2.5706, "text": "Movement fixes and new weapon sway system I had to fix so much of issues with the movement script that I ended up turning hackatime off for a day so it doesn’t look like fraud I swear to god this took so much time"}, {"post_id": 11599, "ts": "2026-06-18T21:47:21Z", "hours": 11.5161, "text": "I was so lost in the old movement code because I didn’t full understand it and the janky workarounds have started to limit the customizability of the whole thing Sooo I spent 12 hours rewriting the entire thing so that I have it entirely like I want it to be: Source style air-strafing, Titanfall 2-like wallrunning, Apex-like slides etc Will be interesting to build maps around this"}, {"post_id": 10629, "ts": "2026-06-17T14:11:50Z", "hours": 4.5156, "text": "Did some refactoring and code cleanup Lag compensation visualization: Blue capsule: client hitbox, Red capsule: server hitbox"}, {"post_id": 10282, "ts": "2026-06-16T22:27:50Z", "hours": 3.0403, "text": "Lag compensation test with friend Works So far I have optimized netcode with: server authoritative model, remote entity interpolation, lag compensation It’s already a solid base for a tactial first person shooter"}, {"post_id": 10080, "ts": "2026-06-16T17:38:02Z", "hours": 6.2219, "text": "Weapon test, sway and bob didn’t learn how to design and model weapons yet so I used the Phantom from VALORANT as a test"}, {"post_id": 9477, "ts": "2026-06-15T20:37:37Z", "hours": 10.6408, "text": "I’m done with client side prediction and reconciliation, input buffers etc. I think I got it to work really well, on localhost you get about 3 frames of peeker’s advantage with 120fps clients which is around ~25ms, which is close to what CS2 gets - with 64 tick rate servers, you can’t really get lower than this I’m moving onto implementing lag compensation Here’s a video showing the peeker’s advantage"}, {"post_id": 8072, "ts": "2026-06-13T14:08:30Z", "hours": 12.0517, "text": "so uh turns out netcode is hard it took me a lot of time to get the movement working on poor network conditions i also reworked the movement the game can withstand ping jitter and packet loss i tested with 100ms ping, 30ms jitter and 10% packet loss, it functions amazingly"}, {"post_id": 5752, "ts": "2026-06-09T17:31:12Z", "hours": 7.7203, "text": "finally implemented client side prediction and reconciliation i first tried doing this 3 years ago with no success now the server doesnt trust clients blindly with their position, the client first predicts its position, sends its input to the server, the server performs the same inputs, sends back the position that it thinks the player is at, client checks if its at the same position, if not, it corrects itself this was very hard in the video the red capsule shows the latest position the client has received from the server. once i enable 50ms simulated ping (100ms rtt) you can see that the server position falls behind while the client continues moving immediately thanks to prediction"}, {"post_id": 4998, "ts": "2026-06-08T17:22:56Z", "hours": 3.4197, "text": "started working on my multiplayer movement shooter first i implemented TCP and UDP connections between clients and a dedicated server i followed Tom Weiland’s old networking tutorials for the basics, but fixed a few things because i felt there were some design issues with the original implementation after that i added my own modified version of Dani’s Karlson FPS controller from an old fangame i made right now players can connect to the server and see each other moving around correctly"}]...
|
Title: Movement Shooter by @balu | Stardance
Devl Title: Movement Shooter by @balu | Stardance
Devlogs:
started working on my multiplayer movement shooter first i implemented TCP and UDP connections between clients and a dedicated server i followed Tom Weiland’s old networking tutorials for the basics, but fixed a few things because i felt there were some design issues with the original implementation after that i added my own modified version of Dani’s Karlson FPS controller from an old fangame i made right now players can connect to the server and see each other moving around correctly
finally implemented client side prediction and reconciliation i first tried doing this 3 years ago with no success now the server doesnt trust clients blindly with their position, the client first predicts its position, sends its input to the server, the server performs the same inputs, sends back the position that it thinks the player is at, client checks if its at the same position, if not, it corrects itself this was very hard in the video the red capsule shows the latest position the client has received from the server. once i enable 50ms simulated ping (100ms rtt) you can see that the server position falls behind while the client continues moving immediately thanks to prediction
so uh turns out netcode is hard it took me a lot of time to get the movement working on poor network conditions i also reworked the movement the game can withstand ping jitter and packet loss i tested with 100ms ping, 30ms jitter and 10% packet loss, it functions amazingly
I’m done with client side prediction and reconciliation, input buffers etc. I think I got it to work really well, on localhost you get about 3 frames of peeker’s advantage with 120fps clients which is around ~25ms, which is close to what CS2 gets - with 64 tick rate servers, you can’t really get lower than this I’m moving onto implementing lag compensation Here’s a video showing the peeker’s advantage
Weapon test, sway and bob didn’t learn how to design and model weapons yet so I used the Phantom from VALORANT as a test
Lag compensation test with friend Works So far I have optimized netcode with: server authoritative model, remote entity interpolation, lag compensation It’s already a solid base for a tactial first person shooter
Did some refactoring and code cleanup Lag compensation visualization: Blue capsule: client hitbox, Red capsule: server hitbox
I was so lost in the old movement code because I didn’t full understand it and the janky workarounds have started to limit the customizability of the whole thing Sooo I spent 12 hours rewriting the entire thing so that I have it entirely like I want it to be: Source style air-strafing, Titanfall 2-like wallrunning, Apex-like slides etc Will be interesting to build maps around this
Movement fixes and new weapon sway system I had to fix so much of issues with the movement script that I ended up turning hackatime off for a day so it doesn’t look like fraud I swear to god this took so much time
MASSIVE NETCODE IMPROVEMENTS I made changes to how the client adjusts its input clock, instead of targeting discrete ticks, it targets time now so we can get even less latency and allows to provide a better experience for both players with a stable and poor internet connection!! This is the same system that CS2 uses
Implemented proper client-side interpolation, made everything tickrate independent so you can host servers with 30hz, 64hz and even 128hz tickrate. Also changed the adaptive buffers to handle the worse internet connections, you can barely notice the rubberbanding now on a bad 4G connection for example. Here’s a test of peeker’s advantage on LAN, I measured about 15-20ms of latency for a player’s actions showing up to all other players on a stable 0ms connection...
|
1793270915.2398782
|
1793875715.2398782
|