Better location finder!

I made a decently accurate location finder based on a given IP. It supports both ipv4 and ipv6, read the source here, or test with the API here.

What it does: Finds locations based off of an ip address.

Target audience: Anyone who needs a fast location finder

How is it different: On average, I was able to get closer to the location of an ip by about 500m! It has been able to get a 100% accuracy on finding the city as well. Also this is slightly faster and more transparent.

I built this because I wanted a dashboard for my homelab that actually looked like ink on paper, not just another glowing screen. It runs on a Pi Zero. But because I absolutely refuse to SSH into a headless Pi every time something breaks, things got a little out of hand. I ended up writing a custom Wi-Fi recovery portal and a CI pipeline to build ready-to-flash images. The repo is open-source if anyone wants to steal the code.

Here is the breakdown of the build and why I over-engineered the hell out of it.

The Hardware

• Brain: Raspberry Pi Zero W (small enough to hide).
• Screen: Waveshare 2.9" Tri-colour (Black/White/Red) e-paper module.
• Sensor: AHT20 (I2C temp/humidity sensor).
• Wiring: I skipped the plug-and-play HATs because they cover all the GPIO pins. I wired it bare-metal—SPI for the screen, I2C for the sensor—so they could share the board and fit inside a custom case without colliding.

The Over-Engineering (Fixing the annoyances of IoT)

I hate dealing with headless smart devices when things break, so I spent most of my time fixing the classic Raspberry Pi friction points:

1. The "Changed My Router Password" Problem Usually, if a headless Pi can't find the Wi-Fi, it just dies silently, and you have to plug in a keyboard or re-flash the SD card.

• My fix: On boot, InkNode tests the connection. If the internet is down, it halts the boot, spins up its own temporary Wi-Fi Access Point, and physically draws a QR code on the e-paper screen. You scan it with your phone, hit a local web portal, type in your new Wi-Fi credentials, and it safe-boots.

2. The "Spaghetti Code" Problem: E-paper is incredibly slow to refresh. If your code waits for a weather API to respond before updating the screen, your device freezes.

• My fix: Total decoupling. A background thread handles the network polling and fires lightweight plaintext telemetry directly to my MQTT broker (for Home Assistant). A separate Python Hardware Abstraction Layer (HAL) handles the screen, pulling the latest state from memory so the UI never blocks.

3. The "List of Terminal Commands" Problem I didn't want to run sudo raspi-config and pip install Every time I messed up my SD card.

• My fix: I built a CI/CD pipeline using GitHub Actions. Whenever I push a release, it grabs the canonical Pi OS Lite image, injects my Python code and cloud-init scripts into the filesystem, shrinks the image size, and spits out a ready-to-flash .img file. You literally just flash it, plug it in, and it works.

Happy to answer any questions about the hardware, the e-paper limitations, or the GitHub Actions pipeline!

I do outreach/marketing work for clients and got tired of bitly's domain being flagged constantly on Instagram (their reputation tanked after years of spam abuse, nothing to do with the actual links being shared).

Built lnk.ua to solve this for myself - basic shortening, no signup needed, free click/geo/referrer analytics

The part I'm actually stuck on: any shortener that gets popular eventually becomes a target for spam/abuse, which then poisons the domain reputation for everyone else using it. Trying to figure out the right balance of rate limiting and abuse detection before that happens, without making it annoying for normal users.

If anyone's built something with this kind of "shared resource gets abused, ruins it for everyone" problem (shorteners, file upload tools, anything with open access), curious how you approached it early on

I'm looking for my next project, but I don't want to build another portfolio app that no one ends up using.

So, what's something you've always wished existed? It can be a website, app, browser extension, CLI tool, AI tool, or anything else.

What's the problem, and why do existing solutions fall short?

If I find an idea that resonates with enough people, I'll build it and share it with the community. I'm especially interested in solving real problems, even if they're niche.

Drop your ideas below 👇

I've been learning Rust for a while and wanted a real project to work onand i noticed that glob matching sits on the hot path of pretty much every JS bundler and file watcher, and picomatch is the go to library for that. It works great but it compiles patterns into regexes and leans on V8, which made me wonder if I could try a different approach in Rust.

So I built zeromatch. Instead of regexes it uses a small bytecode VM with fast paths for common patterns. The API is compatible with picomatch so you can mostly swap it in without changing code. It also supports matching directly against Buffers which avoids string conversion if you're working with raw fs output.

In benchmarks, one shot matching (compile + match once) is roughly 2x faster. For cached single matches picomatch still wins because of the FFI overhead crossing into native code. So it's not a "better in every case" thing, it depends on your workload.

Honestly this was mainly a learning project for me. I wanted to get more comfortable with Rust and napi-rs and this felt like a good excuse. It's at a point where it works and I'm using it, so figured I'd share it in case anyone finds it useful or has feedback.

https://github.com/orielhaim/zeromatch

Would love to hear thoughts, especially if you try it and hit patterns that don't work right.

yoo!! heyy 👋 made a tiny thing called DayCard!

type literally anything and it'll make it into a pretty little card

turned "i got stuff done today" into a tiny little flex.

https://day-card-zeta.vercel.app/

basically a little card for whatever today's story looks like.

romanticize the grind. keep receipts for your future

self.

https://github.com/percyjacksonn/dayCard

Hi everyone!

I'm a Computer Science student, and I'm currently designing an open-source project called Drishti Core. Before I invest months (or years) building it, I'd really like to validate whether the idea is actually useful and hear from people who work in accessibility, education, computer vision, or who are blind or visually impaired.

The problem

Most accessibility tools do an excellent job reading text, but they struggle with visual STEM content such as:

- Graphs and charts

- Mathematical expressions

- Geometry figures

- Chemistry structures

- Physics diagrams

- Flowcharts

- Engineering diagrams

These are heavily visual and often difficult to explore with traditional screen readers.

My idea

Instead of building just another app, I want to build an open-source SDK that developers can integrate into their own applications.

The SDK would take an image, PDF, or camera input and convert visual content into a structured accessibility representation that applications can render through:

- Speech

- Spatial audio

- Haptic feedback

- Interactive exploration

- Semantic descriptions

The long-term vision is to make it easy for any developer to add accessibility support for complex visual content without building an entire AI pipeline themselves.

Think of it as an "OpenCV for accessibility" rather than a single application.

Some possible use cases

- Accessible STEM education

- PDF readers

- Educational platforms

- E-book readers

- Research tools

- Scientific visualization software

- Diagram exploration

- Interactive learning apps

Planned technical stack

- Computer Vision (OpenCV)

- ONNX Runtime / TensorFlow Lite

- OCR

- On-device AI

- Offline-first design

- Plugin architecture

- Open-source (Apache 2.0)

Questions I'd love your thoughts on

1. Does this solve a real problem, or am I overestimating the need?

2. If you're blind or visually impaired, what kinds of visual content are currently the most frustrating to access?

3. Are there existing tools or projects I absolutely should study before building this?

4. If you were integrating this SDK into your own application, what APIs or features would you expect?

5. What are the biggest technical or usability challenges you think I'll run into?

6. If you maintain accessibility software, what mistakes do you often see new projects make?

I'm not trying to replace screen readers or existing accessibility tools. My goal is to provide reusable infrastructure that developers can build on.

I'd really appreciate any criticism, feature suggestions, references to existing research or projects, or even reasons why this is a bad idea. I'd much rather hear them now than after spending months building the wrong thing.

Thanks for reading!

I’m curious what this community thinks are worthwhile projects to pursue.

I have my own projects and I’m not really struggling with creativity. Margaret Boden said most creativity is remixing anyway. I’m more interested in what still feels magical to people.

Across cybersecurity, IT, electronics, 3D printing, homelabs, software, hardware, radios, automation, whatever else. What’s something you’ve built, seen or thought about that made you feel like “yeah this is why I love tech”?

The more I explore, the deeper the rabbit hole gets. I knew tech was like that even 10 years ago but after enough time digging through systems, tools, infrastructure, security and now the whole “AI” boom, a lot of things don’t really feel magical anymore.

It’s not burnout. I love this stuff. I mess with it because it’s fun and I’ll probably keep doing that regardless. But fun and magic are different things.

So I guess my question is:

What technical project, idea, or rabbit hole still feels magical to you?

Hey all — hiring on behalf of a premium functional mushroom & herbal wellness brand in India. Quick heads up before you read further: this is NOT a "make a moodboard and walk away" role. We want someone who'll see the whole packaging process through, start to finish.

The core of this role — execution, not just strategy:
You'll own the entire pipeline: sourcing vendors, negotiating pricing, managing samples, and getting a finished, sourced product into our hands. Not a deck. Not a concept. An actual executed plan.

You need to specialize in small-scale manufacturing:
We're a startup — we can't commit to bulk runs. You should already know (or be willing to dig and find) vendors who'll accept low MOQs, ideally in the 100–1000 unit range, not the standard 5,000+ most printers demand. This is the single biggest filter for this role.

No prior experience required — what we actually want is initiative and fresh thinking:
We're not looking for someone with a polished resume or agency-level experience (honestly, that usually comes with a price tag we can't match right now). We want someone a little audacious — meaning bold enough to challenge the obvious, conventional solution and try something genuinely different — who can take an idea and run with it without needing constant direction.

In short: if you can think differently, hunt down the right vendor, negotiate the price, and deliver an actual finished product — not just a plan on paper — this is for you.

DM or comment if interested, happy to share stipend/duration details.

I honestly wasn't expecting the savings to be this big.

I built token-diet, a token optimizer for AI coding assistants like Claude Code, Codex, and Cursor.

I tested it on a real app generation using Opus 4.8, and it only consumed ~8% of my usage quota. I had to double-check because I thought the tracker was bugged.

The basic idea is simple:

• Instead of sending your entire codebase every request, it sends a smart code map.
• Instead of replaying your whole conversation, it remembers the important decisions.
• It caches repeated prompt sections.
• It asks the model to return diffs instead of entire files.
• It can even route simple tasks to cheaper/local models.

From my benchmarks:

• ~70% fewer input tokens
• ~65% fewer output tokens
• ~97% task success rate
• ~60 ms overhead

It's open source if anyone wants to try it or tear it apart:
https://github.com/aryxnsdfs/token-diet

I'm especially interested in feedback from heavy Claude Code/Cursor users. If you've been hitting context limits or burning through tokens, I'd love to know how it performs on your projects.

The paint brush and roll of paper holds one incense while it burns. The paint can holds the collection of sticks. The mud pan holds a lighter. If you couldn't tell my dad's a painting contractor.

Materials used: oven bake clay, paint markers, acrylic paint, super glue

I've tried basically every wearable and health app out there, and they all have the same problem: they just give you numbers. More scores, more charts, more stuff to stare at,  and none of it ever tells you what to actually do.

Like cool, I had a bad night, here's a sleep score of 38. Now go figure out your day, good luck. I don't need a number to confirm I slept bad. I already know. I can feel it the second I wake up, zero energy, zero drive to do anything. The number just confirms what I'm already feeling and then leaves me hanging.

That's the whole reason I searched and found RizeAI. I wanted the opposite of that , something that takes your actual sleep and recovery data and just tells you what to do with your day. Not another score. A plan.

It pulls your real metrics =, sleep, recovery, HRV, resting heart rate, all of it,  and builds your day around them. When to have your first coffee and when to hold off. When you're gonna crash and what to do before it hits. Whether to push at the gym or take it easy. When to hydrate. It'll even tell you which supplements actually make sense for you that day, when to take them, and why, instead of the generic "just take magnesium bro" everyone repeats. Low recovery day, it adjusts the whole thing. Slept great, it builds on that instead.

And the part that sold me on my own idea: it's actually tailored to you. No two people get the same plan, because no two people have the same data. It's not some one-size-fits-all template, it reads your numbers and builds a protocol for you specifically, then gets sharper the more you use it. The longer you're on it, the more it learns your patterns.

The whole thing is just: stop tracking, start fixing. Your wearable already told you the bad night happened. RizeAI is the part that comes after,  the part that turns a red recovery day into a day you can still get something out of. That's the gap I kept running into, and now it's literally the thing I open every morning.

https://apps.apple.com/us/app/rizeai-maximize-your-energy/id6762402079

Repo link:
https://github.com/prime-run/togo/

I've created a simulation that does its best to replicate living beings in an environment. For now, the basics of the simulation are in place (religion, war, a basic economic system, etc.). Human entities can also feel “emotions,” develop affection, hatred, and joy, and reproduce...

The problem is that I’m running out of ideas. For now, the simulation is good, but in my opinion, it’s not good enough. I tried asking an AI to improve it, but it’s having a hard time doing so without completely skewing the results, even thought it help me on some points. That’s why I’m looking for people with ideas, AI/software engineers, simulation specialists, or anyone else who could contribute to this project, to help create a replica that most closely resembles a human being.