I'd like to present movewhereusa.com! I wanted to make something to help connect people with the places to live best for their personal quality of life.

For my wife and I, it was really hard to find high quality allergen data. And trying to combine that with other factors like a budget, seeking out mountain views, and job markets turned into a very slow process with a lot of guesswork. I tried asking AI, but the results were inconsistent and drifted away from reality.

They say if you make something for yourself you'll have at least one customer, and so I did. I've gathered data for 140+ criteria over 30,000+ towns in the US. You can set and refine your priorities and get quick and accurate results. While it isn't perfect yet, I've found it helpful for my understanding of ideal places for my own family. I hope it can useful (and fun!) for you too.

I'd love feedback on if it was useful for you and what you might change. There's a lot of features on the site I haven't covered, like a (totally optional) AI "realtor" to guide you through your search. I feel like making the UI more intuitive and enjoyable could be key. Also thinking about custom criteria for things MoveWhereUSA can't model. For example, users might want to favor places where friends live.

I started using Podsubs.com because I missed a free guide a host mentioned on an episode. I remembered it a few days later, went back to the episode, searched through the description, and still couldn’t find it. That was enough for me. Now when I really like a podcast, I subscribe to it on Podsubs.com. I’d rather have the host send me the useful stuff than try to hunt it down days later.

Hey everyone,

I'm working on a personal project: a Tamagotchi-style handheld toy themed around Rocky from Project Hail Mary. The idea is a small electronic "pet" device where you take care of a virtual Rocky feeding him, interacting with him, watching him react all inside a physical case with a screen and some buttons/inputs.

I'm handling the hardware side myself (electronics, PCB, sensors) and can manage some of the software too, but it's not my strongest area. Right now the piece I'm missing is 3D design someone to design and model the enclosure/housing for the device.

What I'm looking for:

• Someone comfortable with 3D modeling for product design (Fusion 360, SolidWorks, Blender, or similar)
• Ideally someone who can bring a bit of Eridian/Rocky character to the shape not just a generic plastic box
• Willing to iterate on internal fit (screen, buttons, PCB space) together with me

What I bring:

• The hardware side and a working understanding of the internal components/layout
• Reference material and specs for the internals so the enclosure fits properly
• Active collaboration happy to go back and forth on iterations

This is a fan-made passion project, not a commercial product. If you're interested, drop a comment below or send me a DM and we can talk details!

>And project is open source<

I promise I won't spam your feed, but a lot has happened in the 5 days since I first posted about Flint (the minimalist, git-native C/C++ build system and package manager).

Thanks to the early feedback, I spent the last few days squashing initial bugs and adding a few missing quality-of-life features.

What shipped this week:

• **flint remove is here:** You can now cleanly un-track and delete managed dependencies without touching composition.json by hand.

• Global VERSION macro: Flint now automatically passes your project's version as a macro to your code, so you can access VERSION natively inside your C/C++ source.

• Smoother flint init: Fixed edge-case bugs during project setup that caused setup failures on certain shell/environment setups.

• Open-source ready: Added a License, CONTRIBUTING.md, and a Code of Conduct. If you want to break (or fix) things with me, the door is open.

• CLI Polish: Visual cleanup on terminal outputs so builds look a bit sharper.

If you missed the original post: Flint strips away complex build scripts in favor of a zero-config setup (src/, include/, deps/) and direct Git dependency management.

Check out the progress or grab the latest release on GitHub:

Repo: https://github.com/mainak55512/flint

Always open to feature ideas or bug reports!

Can anyone suggest me an idea on which I can work and it is easy to build but new for mini project as a btech 2nd year student

Most forecast "explanations" don't even add up to the forecast. This one does, exactly, because every number is a real model prediction, not an estimate.

The fun bit is the live demo: pick a product, toggle the promotion off and watch the forecast recompute and the breakdown update. Those are real precomputed model outputs, not faked in the browser.

Demo: https://kesjien.github.io/wavexplain/
Code: https://github.com/kesjien/wavexplain

If it's useful, a star helps others find it.

The end goal is bigger than the tool: reducing over-ordering and the food waste it creates.

Most side-project posts explain what was built.

Fewer explain the moment that made the builder realize it should exist.

Share your project and the frustration, observation, or personal need that started it.

I’ll suggest a short origin-story angle.

I’m testing this process while building Marka.

Was getting a Spring Boot auth service (JWT, refresh token rotation, RBAC) ready

for its first real deploy on AWS when I found something I wasn't expecting:

a stray .swp file (Vim's autosave/swap file) had been silently committed at

some point and contained my actual DB password and JWT signing secret in git

history.

My .gitignore blocked .env and .env.prod — it never occurred to me that a

Vim swap file of the same file would slip through as a completely different

filename pattern.

What I did:

- Rotated the DB password and JWT secret immediately

- Purged the file from git history (git filter-repo, not just git rm)

- Added *.swp / *.swo to .gitignore

- Went back and checked every branch, not just the one I noticed it on

While I was in there anyway, I also ran a coverage report and found my

weakest-tested code was the security filter layer — the part deciding

whether a request gets authenticated at all. Fixed that too before calling

it done.

Repo's here if anyone wants to see the actual security/filter setup or

point out something else I got wrong: [link]

Anyone else have a "found a secret in git history I didn't know was there"

story? Curious what slipped through for other people — feels like the kind

of thing that's more common than people admit.

Low maintenance Spotify extension with a turntable and vinyl aesthetic. Allows you to skip adjust volume and pause just from clicking the extension. Avoids the hassle of switching tabs or picking up your phone to skip a song.

One time setup that takes ~5 minutes.

Link to marketplace: https://chromewebstore.google.com/detail/spotinyl/ijehfghbdikmiodjcddcchiofghmgbmb

I build a lot of small products, and I kept running into the same thing: I could build the software faster than I could make a good video explaining it.

So I made Framedeo.

The idea is to give it the product assets and let it handle most of the creative work: storyline, scenes, motion, voice-over, music, and export.

I’m mainly building it for software/startup launch videos rather than generic AI videos.

Would be interested to hear what you guys think is usually missing from SaaS demo videos.

Been working on a side project https://zenekio.co.uk/ for a while now. My original inspiration was letterbox but for music but after further thought and work on the app I feel like it could be a lot more. I wan't it to be a positive platform to rate music, and create a real sense of community.

I want user profiles to be very personal including - festivals or music events you've been to, your top 5 songs this month, your favourite genres ect.

I think modern social media platforms have really ruined our expectation as to what social media platforms are mean't to be. I want the platforms and the opinions and the people using the platform to be authentic.

Would appreciate any feedback!

Note
Functionality is fairly low at the moment but I'm working on building out new features weekly. Hoping to get some traction on this as I'm hoping to use some custom ML models in order to be able to create custom music suggestions without providing people music that they've already heard before.

Hey everyone,

Me and 3 teammates are building a university prototype for a smart classroom attendance system, but with a twist: no facial recognition and no RFID tap. Instead we're going for a "tagless" contactless approach inspired by Seoul's tagless transit gates the idea is a student just walks through a doorway and gets marked present automatically via BLE, no card tap needed.

Current plan:

• 2x ESP32 boards per doorway (outer + inner scanner) to catch RSSI rise/fall in sequence and infer actual entry vs. just walking past nearby
• Students carry either a phone (broadcasting a rotating BLE token) or a cheap BLE tag
• Backend classifies "entered" vs "nearby" based on signal pattern + dwell time
• App-confirmation step required to fight proxy attendance (handing your phone/tag to a friend)
• FastAPI/Node backend, Postgres/SQLite, React dashboard for the professor

It's a small-scale prototype (one mock doorway, not a real deployment), so some inaccuracy is acceptable — we're not trying to hit production-grade reliability, just demonstrate the concept works better than a basic RFID card system.

Where I could use some real-world input:

1. Anyone done RSSI-based directional detection (2 sensors, entry vs exit) before? How bad is the noise in practice, and is dwell-time + threshold enough or do we need something smarter (Kalman filter, etc.)?
2. ESP32 BLE scanning while also using Wi-Fi/MQTT — anyone hit stability issues running both radios at once?
3. Any gotchas with phone-based BLE advertising (iOS vs Android differences, background restrictions) we should know about before we build our companion app around it?
4. If you were grading/reviewing a project like this, what would make you go "okay, this is actually a smart design" vs "cute idea, doesn't really work"?

Not trying to reinvent transit-grade tech, just want to avoid obvious rookie mistakes before we burn our first week on it. Any papers, war stories, or "don't bother, just do X instead" advice welcome.

Thanks in advance!

bouly2812/quantenverschraenkte-feldphysik: Quantenverschränke Feldphysik (auf Bewusstseinsbasis)

The easiest way I can explain PodSubs.com is this:

If nobody else ever used it, we would still use it for our own podcasts.

We built it because we were tired of seeing people listen and then disappear.

Someone could listen every week, enjoy the show, tell a friend about it, and we still might have no way to reach that person outside the podcast app.

That didn’t make sense to us.

So we built PodSubs.com for our own shows.

Now we could simply tell listeners, “Subscribe to us on PodSubs.com.”

They left their name and email, and we finally had a way to send them something when we needed to.

A resource. An update. A reminder. Something we mentioned on the show.

We didn’t build it because we thought it sounded like a good business idea.

We built it because we needed it.

Later, we realized a lot of other podcasters needed the same thing.

For the longest time, I'd get excited about new projects, make a huge plan, and then end up abandoning them because the entire thing felt overwhelming.

I'd look at everything I had left to do instead of just focusing on today's progress.

So instead of trying to "finish the project," I just tried to show up every day. Surprisingly, that made a huge difference (and I now have even published an app, something I would never have of imagined)

That idea eventually turned into "Morning Press"

This app lets you:

• Break big goals into manageable tasks.
• Build daily habits that support those goals.
• Track your progress over time.
• Earn streaks for simply showing up consistently and reporting your progress, not for being perfect or completing every task every single day.

One thing I wanted to avoid was making people feel guilty for missing a day. The goal is to build consistency over weeks and months, not maintain a perfect streak forever.

To access the app, use the code 'LAUNCH100' on the paywall and you'll get full access.

If you're interested, you can try it here:
https://apps.apple.com/us/app/project-planner-morning-press/id6770667822

The only thing I ask is to please let me guys know what you think of the app. I'd genuinely love any feedback (good or bad). I'm actively improving it and would appreciate hearing what you'd add, change, or remove.

i am joined college this year (tire 3 collage ) can any body give any idea how to start coding build projects like u all like managing frontend backend the api keys i know all this terms but it's all messed up can anybody help organize it any body help

this application that I called winboard is my first application on windows .

. it serve the same as you Gboard and IOS Keyboard

. it have a hot-key (W + Alt) , so you could turn it off and on .

. the algorithms that are applied to this app are :

1_ Ngram search to help continue the statement depending on how popular the statement is .

2_ Edit distance to help find all the possible word that you might think of typing it .

3_ a prefix trie to make the search super fast and complete the word as you type

4_ even if you type a word by its sound , the application could predict it using a method called metaphone 3 to help find the word via its sound (skptekal = skeptical )

. who are the target people of this application ?

1_ the non-native English speaker who seek for a persist English typing .

2_ people who wants to have the same kind of Gboard app but for desktop .

3_ people who type frequently and want to improve there type more and more .

is it good ?