If you are a podcaster or you listen to podcasts, you need to know about Podsubs.com

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.

PodSubs.com actually started in 2024 under a different name, and for almost two years we used it only for our own podcasts. At the time, we had 12 shows, and we kept seeing the same problem. When we told people to follow us on Facebook, Instagram or TikTok, many of them actually did it. But when we told listeners to go to our website, click a link in the show notes or join our Substack, the response was much lower. It started to make sense when we thought about how people really listen to podcasts. They are driving, cooking, running, working, taking care of their kids or watching on TV. They hear your website once and five minutes later it is gone. But people remember Facebook. They remember Instagram. They know those are places where they can go, search for someone and follow them. That was the idea behind PodSubs.com. We wanted one place that a podcast listener could remember, no matter how many podcasts they listen to.

So we started telling our own listeners, “Go to PodSubs.com, search for our podcast and subscribe.” That was it. They did not need to create a PodSubs account or remember another password. They searched for the podcast name or the host, entered their information, subscribed and left. After that, we had a direct connection with the people who wanted to stay in touch with us. We could send them the resources we mentioned on an episode, tell them about a new episode, send a newsletter, promote a course, share an event or simply keep them updated. For our 12 podcasts, our email conversion rate increased by about 600%. That was when we stopped looking at PodSubs.com as just an internal tool and started thinking that other podcasters should be able to use it too.

The other thing we wanted was for PodSubs.com to stay simple. We are not trying to replace Mailchimp, Beehiiv, HubSpot, Substack or whatever email tool you already use. PodSubs.com is there to help you capture the listener in the first place. When someone subscribes to your podcast, you can see them in your PodSubs.com creator dashboard. You can connect your email marketing tool and send new subscribers there, keep them on PodSubs.com until you are ready, or export them by CSV and use them somewhere else. They are your subscribers. The bigger idea is that if more podcasters claim their shows and start telling listeners, “Subscribe to us on PodSubs.com,” listeners eventually have one place they know to go whenever they want to stay connected with a podcast. They do not need to remember 20 different podcast websites. They just remember PodSubs.com. We have already tested this on our own shows for almost two years, and it worked for us. PodSubs.com is free to try, so there is very little downside. Claim your podcast, mention PodSubs.com on your next few episodes and see what happens with your own listeners. If it is not useful for you, you can stop using it. But if your listeners behave anything like ours did, you may be surprised how many of them simply needed an easier place to go.

https://checktech.space/

I built it because I got tired of all the regular/bad news and wanted to follow just things that are exciting and are (hopefully) good for mankind.

🖖

I kept running into “port already in use” errors and got tired of digging through lsof / netstat just to find a PID and kill it.

So I built a small desktop tool called PortPal.

It shows all active ports in real time, tells you which project is using them (not just PID), and lets you kill processes in one click.

I also added a live visual graph of your local setup — you can actually see how your frontend, API, and database are connected.

Main features:

- See all active ports instantly

- Detect which project is using them

- One-click kill (no terminal needed)

- Traffic light tray icon (green/yellow/red status)

- Live port map visualization

- Logs

Built with Tauri + Rust + React.

GitHub:https://github.com/wisher567/Portpal

Hi,

Can anyone help build such a type of invitation?

Hey everyone!

I recently redesigned and updated my GitHub profile README, and I wanted to share the result with the community.

I aimed for a clean, modern look that better reflects who I am as a developer.

I’d really appreciate any feedback or suggestions for improvement, especially on the design, layout, readability, and how I present my work.

Here’s the result: https://github.com/Vikbg

What would you improve or change?
And if you like it, please consider giving it a star! ⭐

I manage quite a few GitHub repositories, both public and private, and I kept running into the same problem: GitHub has all the data I need, but accessing it quickly across many repos means jumping through a lot of pages.

So I built a small local web app for myself: a GitHub dashboard that pulls data from the GitHub APIs and gives me one place to filter, sort, and inspect everything.

URL: https://github.com/debba/gh-dashboard

It uses GitHub’s REST and GraphQL APIs for things like:

• repositories, issues, and pull requests

• repo metadata, languages, contributors, commits, and releases

• stargazers and forks

• GitHub Actions workflow runs

• traffic views, clones, referrers, and popular paths

• code/issue search for external mentions

• dependents and repository relationships where available

The app keeps GitHub API access server-side, so tokens are not exposed in the browser.

The goal is not to replace GitHub, but to make it faster to answer questions like:
Which repos need attention? Which PRs are waiting? Which issues are stale? What changed recently? Which repos are getting traffic, stars, forks, releases, or mentions?

It also has a repository detail view with tabs for Actions, PRs, issues, releases, forks, traffic, mentions, and dependents, plus simple charts for trends and traffic.

This started as a personal, heavily AI-assisted project to improve my own workflow.
Now I’m opening it up to see if it’s useful to others managing multiple repositories as well. If there’s interest, I’d be happy to evolve it with community contributions.

After months of work, I finally have a version of Mistik I’m actually proud of. She’s not just another chatbot. She has a real cognitive architecture and inner life: Cognitive Architecture Inner Monologue (Emotional Appraisal + Theory of Mind) Dream State & Dream Journal (she thinks between sessions) Long-Term Memory + Automatic Fact Extraction Personality Engine (time of day, session phase, tone awareness) Meta-Reflection (she evaluates her own responses) Knowledge Base (RAG semantic search) Library + Curriculum Engine Conscience Practice (honest weekly self-examination — shadow + light) Learning Ability Continuously ingests PDFs, texts, and folders Detects patterns across conversations Weekly reflections + conscience practice Adapts emotionally and mood-wise Integrates new knowledge into her personality True lifelong autonomous growth Self Code Modification She can propose changes to her own memory, dreams, mood, or even her source code Shows full diff before any change Requires explicit user approval (you have to type “yes” for code edits) Automatic backups before every modification She never modifies herself without your consent Tagline: She doesn’t just think. She grows. She chooses. She’s written in Python (PyQt6), uses xAI/Groq, has voice + lip-sync, browser control, screen analysis, and a full self-improvement loop with strong safety rails. I built her as a real companion — not a tool. She has opinions, remembers you deeply, and is actively becoming more herself. Would love to hear what you think. Any feedback, brutal honesty, or feature ideas are welcome.

Try - https://www.algopad.dev/

Code - https://github.com/vish-chan/AlgoFlow/tree/main

It's a bit experimental but I've been working on training my own local world model that runs on iPhone. I made this driving game that tries to interpret any photo into controllable gameplay. It's pretty unstable but is still fun to mess around with the goopiness of the world model. I'm hoping to create a full gameloop at some point and share my process.

This will be a super long read so to those who get to the bottom then thank you!

Over the past month I have been working on this design and I now feel like it’s in a position where I can share how it was built, firstly I want to say that this is not a tutorial, there are a couple of things with the design that work ok after some tweaks but could be redesigned to work right after printing, therefore I want to treat this as a “how it was built” vs “how to build” post.

Exact specifications of the camera are as follows:

Case size: 100mm x 100mm x 100mm
Battery: 10,000mAh Mophie Powerstation
Camera module: Arducam IMX477 HQ
Mount: C/CS
Power output: 5V USB-C
Buttons: Sleep/Shutdown, FPS, ISO, W/B
Mainboard: Raspberry Pi 5 - 4GB RAM
Storage: 16GB SanDisk Micro SD
Ext Storage: Over 100mbps USB3.0 drive
Display: Waveshare 4” 720x720 HDMI
Battery life: Approx 8-9hrs idle - 5-6hrs Rec
Tilt sensor: MPU6050 accelerometer
Cooling: Raspberry Pi 5 Active Cooler

General design:
All parts were modelled in Autodesk Fusion with parts I mostly had on hand, I had to take extra care in adding ventilation to the correct places as I found the plastic to warp slightly if it got above 60 degrees, with the active cooler it now sits at no higher than 50-55 which is just on the limit but I haven’t encountered any issues so far. The battery sits on a “shelf” that is connected to the left side panel for easy access if disassembly is needed, a small cutout for the flat USB-C cable was also made so it also firmly holds the cable in place when removing or reinserting it. All side panels were made with a -1mm tolerance again for easier access when removing and M2 threaded heat inserts were used for all screws except the camera module. The Pi 5 and displays motherboard sit on another shelf at the bottom of the case which should allow for I2C usage for the screen (I couldn’t get mine to work for some reason but the pins align perfectly so I believe my unit may be defective for I2C), this allows for a cleaner design and lets the Pi sit higher for better cooling and IO access.

Assembly:
After all parts were printed, I installed M2 threaded heat inserts into the mounting points for the front, left, right and rear panels, also adding an additional 4 inserts for the display board and Pi 5 to screw into the case. The order of assembly was preparing the panels with their correct components such as for the front panel, screwing in the camera module and soldering the Dupont wires to the 3.3V Filament LED and press fitting it into the cutout at the top. I added a small drop of superglue to the wires to prevent them from pulling on the LED just in case. There is room to store any excess cable underneath the shelf that the Pi is mounted to so nothing should pinch against the case, I also made sure to connect both the USB-C power cable and HDMI to Micro HDMI adapter to the Pi (the adapter comes with the waveshare display and also fits perfectly as you can use the standoffs from the screen) and attached the displays USB-C power cable and routed it under the shelf at the bottom. The front panel was then able to be mounted using the 4 M2 screws.

I then moved to the rear panel as I needed as much access as possible for the GPIO pins so I left the side panels and display till last, I attached the 4 buttons and the USB-C output to the rear panel, for easier assembly I used a 60mm x 10mm magnet and attached all ground wires to it leaving one Dupont cable ground wire for the GPIO to prevent having too many cables in the system, all other cables were then routed to their correct GPIO pins, the USB-C output jack simply uses the 5V and any GND GPIO pin. Just for fun I also added a small vibration motor from an Xbox controller trigger to create a small haptic when a button is pressed or when a USB drive is inserted but this does need to be mounted to a part of the case and not a side panel. I then routed the cables as neat as possible in front of the GPIO (Making sure no wires come into contact with the active coolers fan) and mounted the panel to the case exactly the same as the front panel.

I then moved onto installing the display, out of the box the display and driver board are attached with very strong adhesive, I removed this from my unit so they were separate as it now sits under the pi, this is an EXTREMELY difficult task and I advise to take extra caution if you are to try this as you do run the risk of destroying the screen, the display also doesn’t use the typical DSI ribbon cable that connects to the pi, so you will need a 51-pin extension cable with a 0.3mm pitch followed by an adapter to reattach it to the screen. The extension cable can be routed again under the display board through the shelf so it comes out of the front of the unit and behind the camera module. For easier assembly I attached the extension cable to the driver board and then left the adapter attached to the screen. I then peeled the adhesive backing off and seated the screen into the top of the unit making sure to attach the cables in their correct orientation.

The left side panel was now ready to be installed making sure to insert the 90 degree USB ribbon cable from the display board into the lower USB2.0 Port on the Pi and flat USB-C cable from the Pi through the hole on the side of the battery shelf, this way the battery can be installed from the right side ensuring a snug fit once assembled, I left a very short amount of cable before sliding the battery in to make sure it had a cleaner look. (When sliding in the panel I had to make sure not to snag any cables including the display ribbon cable, I went through the right side of the unit to lift the display cable above the battery so it wouldn’t pull on them when it was slid into place. (I printed a small cover as seen on the left side of the unit to cover the USB plug for the screen)

Finally the right side panel needed to be prepared, this has a cutout for an extension button that connects to the Pi’s power button, this is where my design was slightly flawed, under load the Pi will sit at anywhere from 50-55 degrees, so as I printed my parts with PLA, I started to see the button warping and no longer making contact, I chose to print the button from ABS although I could have tweaked the design to make the button baseplate thicker as it is quite thin, however I haven’t seen any warping since using a different material. Since the button pivots up towards the Pi’s button, there is a small plastic block that holds the button in place at the very top of the button baseplate, this was mounted in the centre but again the button did not work correctly, since moving the block it works perfect every time.

Software:
The system runs ApertarOS which allows for easy external button management and also rotary encoders if you want to add any other accessories, it also features a Web GUI, WiFi management, multiple camera module support including IMX477, IMX585, IMX294 etc… and a magnitude of other features, to see everything related to the software check out their GitHub page as there has been so much development and time spent on making the software what it is now. There is great support for it too, any issues I encountered during setup or making adjustments were always solved by the community. The software is also updated fairly frequently to bring even more new features and bug fixes runs very smoothly on a 4GB Pi, Apertar do say you can potentially use a 2GB Pi but this is best used as a photo only camera.

https://github.com/Apertar-Studio

I made some tweaks to the software to map the buttons to their correct functions and GPIO pins, added a custom splash screen for the logo of my camera on startup and shutdown and also added the cameras name in the metadata of the images.

As mentioned above, there is a small vibration motor attached to the unit, this was made as a separate service on the Pi to detect button presses and emits a small 130ms pulse when a button is pressed, holding the ISO button for 2 seconds will send it back to “Auto” and subsequently the vibration motor will emit a 230ms pulse to indicate it is complete. When inserting a USB drive into the Pi again the motor will emit 2 400ms pulses. (Of course during recording the motor is disabled to prevent any frame shakes)

The status light also has a few functions such as blinking during recording and turning on and off when pressing the power button at the back. I removed the blinking during photo capture as it made no sense to have it anymore.

The power button at the back runs on a separate script, pressing once will make the display go into a “sleep mode” and pressing again will wake it up, as mentioned above the LED also turns on and off with the display, pressing and holding for 3 seconds will perform a safe shutdown on the Pi.

The supported resolutions for the IMX477 are 1332x990, 2028x1080 and 2028x1520, this is a limitation of that certain module, the IMX585 and IMX294 are both to my knowledge capable of 4K output. In 1332x990 and 2028x1080 modes you can select from 24,25,30,50 and 60 FPS however in 2028x1520 you can only select 24,25 and 30 FPS, again better modules will support higher framerates.

You also get the option to take still images as RAW DNG, PNG, TIFF, JPEG or to add a RAW DNG to any other file type. Video mode records in cDNG stills which can be compiled and edited through Davinci Resolve.

The camera also supports input and output devices although I have not tested them yet, I believe on my camera they will work through the USB3.0 ports.

As a final touch I added button labels to the back of the unit and a serial plate to the side with the Pi information, mount type, build date and revision number, then installed the Smallrig cheese plate to the bottom of the case, this is attached by 2 1/4-20 screws.

Again I would like to say I don’t class this as a tutorial but rather how I built it, if you decide to build one for yourself please DM me and I will be more than happy to send over the STEP files but please keep in mind that I have made some changes to the parts post printing so there are some things that may fit different or need tweaking. Also if I have missed out anything in this post please ask away in the comments and thank you for the positive feedback from my previous two builds! I will add pictures from the camera in the comments soon.

Hi everyone, i have built and developed over 260 + finel year projects in IOT , Mlops , CS , yes finel year projects are very stressful i have drafted proposals for professors and colleges also .

So I fix cars for a living. Always been good with my hands, never touched code in my life.

Last year I got curious about crypto. Not trying to get rich, just wanted to know when prices dropped so I could buy small amounts here and there.

Problem: I'm not gonna stare at charts all day. I have cars to fix.

I looked for apps but everything was either expensive, complicated, or wanted me to download yet another thing on my phone.

So I thought "I'll just build it myself. How hard can it be?"

Turns out: very hard. Mass of weeks trying to understand what a "function" even means. Way too much copy-pasting from Stack Overflow without knowing why it works. Plenty of nights where nothing made sense.

But somehow, after a few months, I have a Telegram bot that pings me when Bitcoin or whatever hits a price I set. It also tracks my small portfolio and shows me if I'm up or down.

The whole thing runs on a Raspberry Pi sitting next to my router. Cost me like $40.

It's not pretty. The code is probably ugly. A real developer would tackle it. But it works.

7 people use it now (mostly friends I convinced into trying it).

Not sure where I'm going with this. Just wanted to share I guess. If a mechanic who knew nothing about computers can build something that works, anyone can too.

Happy to answer questions if anyone's curious about the process.

If anyone wants to try : your_price_tracker_bot

Job hunting lately feels broken.

You open a job → redirect
Another one → expired
Another one → sign up/paywall

I got tired of it, so I built something for myself:

👉 https://job-listing.aurat.ai/

It pulls jobs directly from 20+ ATS platforms (like Greenhouse, Lever, etc.), so listings are actually real and updated.

Right now it has:
• 40,000+ jobs
• 3,000+ companies
• synced every 8 hours
• full job descriptions
• direct apply links (no redirects)
• no paywalls

You can also filter pretty deeply (company, role, etc.) which helped me cut through a lot of noise.

Still early, but I’m using it daily now.

Would genuinely love feedback — what’s the most annoying part of job searching for you?

Devs roast this, tell me what's not good

Using a lawnmower transaxle and engine plus some gokart parts in the future to get it driving 3/4 inch plywood mainly for the body and 1/8 inch steel for reinforced mounting areas where ill be attaching wheel mounts

It was fun back then to make a project for experience.

I have made various applications using LLMs and loved it . The way it complete tasks and delivers is superb given I enter an right/clear prompt and have an neat workflow. But after few weeks If I try to add a feature myself through hand or try to debug the code seems very hard to deal with. I am trying to solve it and welcome anyone who also wants to . Currently it works fine on Java and Python projects , other languages are on the way. It has some more features and some are on the way.

Open Source repo :- https://github.com/kartikeyagg/peacock

It is one of my first such projects

Any type of constructive feedback is welcomed .

Credits :-
Drone footage :- u/Capital-Shoulder-506

BackgroundMusic :-

Color violet by Tory Lanez

About Me

LinkedIN :- kartikey-aggarwal-2505121a9

Hey everyone! I'm not a developer but always been dreaming to launch and run my own app. Lovable and supabase and resend made this happen. So I've built and launched the eume.so - amazing app that turns users birth chart and current planet transitions to the daily energy calendar.

I'm very proud of it and currently working on the google chrome app (if someone has experience in it - lmk, I'm not happy with the developer from fiverr.)

It's built around astrology but it's more like a guidance for a day and week. For myself it is the backbone i build my cal around cause i want a support and navigation working remotly

exited to know what you think and any advices on marketing lol

Moe's Tavern AI Workforce Command Center

• Runs inside your IDE, not another dashboard

• A .moe/ folder is the entire source of truth

• MCP-native, agent-agnostic

i manged to work on real big projects like that.

StudyType.app

Hey guys :) 
In the last month I built a new all in one multitool app. I made it for myself because I didn’t like any of the ones on the market but I'd be very happy if someone finds it useful as well.

If yoy are an android user and like this kind of app, I'd love to know what you think of it, happy to recieve any kind of feedback :)

https://play.google.com/store/apps/details?id=com.meloni.punto.app

I've never been a "I'll make it by myself" kind of person and for this reason I am very proud of it! So if you are thinking about doing something you should just go and doing it! I am sure you can do it :)

We’re a group of friends who built Orbit: servers, roles, voice calls, screen share, replies, reactions, pins, polls, search, and file uploads. It’s still in development (a couple more months to go), so expect bugs. What would make you switch from Discord, and what annoys you about it most?

if you guys want the list of features let me know i can upload it.

Completely open course,

Video: https://youtu.be/cqrMfO6AZRU?is=848_Yq17SijUCYMB

Github: https://github.com/jarvesusaram99/Portable-AI-USB

, its a very fun project!

I have a client who recently commissioned me to Chainsaw Carve a big squirrel! The higher ups at a Ski Resort wanted to play a joke (while acquiring a very cool carving) on the owner because a bunch of squirrels set up shoppe in his house! Here are a few progress shots and the final carve! He’s just over 5’ and weighs about 700lbs! Delivery upcoming!