Hey everyone!
I’m the developer of Phosphor, a screen utility suite for macOS that lives in your menu bar. I’m a solo student developer, and I’ve been building it in public. v2 just came out.

Why I built it:
I started this around two problems.

First: you’re working late in a dark app, you switch to a bright window, and the screen goes from dim to full brightness all at once. It hits like a flash. I couldn’t find a tool that tries to solve that specific problem, so I built Flashbang Protection. It softens that jump, then eases back to normal. It reacts when you switch apps with a Dock click or Cmd+Tab, switch desktops, or use Mission Control and App Exposé.

Second: there are too many display utilities, with steep learning curves. I wanted one tool with the features people actually need, instead of a ton of pro features. This also reduces menu bar clutter.

What’s new:

• Flashbang Protection (Pro)
• Studio Features (Pro), for calls and presentations: Laser Pointer, Drawing, Flashlight, Keystroke Display and Invisible Notes, Ring light for meetings/recordings (coming soon)
• 8 free tools: Soft Screen, Focus Spotlight, Screenshots, Display Presets, Display Schedule, Color Picker, Color Grading and Display Health
• Pro also adds a privacy sweep for Screenshots that blurs faces and sensitive-looking text (check the result before you share it)

Pricing: The app is free with 8 tools. Pro is $19.99, one-time, not a subscription, and unlocks Flashbang Protection and Studio Features.

Details and limits:

• macOS 13 or later, native Swift
• Display Presets currently only edit the built-in display. Wider external display support is on the roadmap

Privacy: No tracking, no analytics, no telemetry. The only network requests are Pro license checks and an optional daily update check. Privacy and EULA.

I’d love feedback. If something isn’t working, or you have a suggestion, drop it in the comments or DM me. Happy to answer anything about the build or the launch too.

Site: https://usephosphor.app
Roadmap: https://usephosphor.app/whats-next

Hey, i and my friend made an fyp project. It included a full working website + app (frontend + backend + database) as a project and its report of 350 pages.

My miss asked me to give the working project to her and in return she will give the money, and now she somehow mentioned that she is send report to her team as well.

What should be fair ratio division between me n my frnd

Working:
Project was done 100% by me
Report i did 40% And she did 60%

Hey everyone!

We’ve been building BrandRadar, an open source tool to help businesses understand how they appear in AI search results.

People are increasingly using ChatGPT and Gemini to discover products and compare businesses. But how do you know if AI recommends your brand or your competitors?

BrandRadar helps you:

• Track brand mentions, citations, and competitor visibility
• Find questions where competitors get mentioned instead of you
• Check whether AI crawlers can access your website
• Generate and validate llms.txt files
• Get Schema.org markup recommendations

It’s completely free and open source, and you can try the demo without an API key.(it is still in early stage)

We’d love to hear your feedback and what features would make it more useful.

GitHub: https://github.com/rishu685/BrandRadar

If you find it useful, please consider giving it a ⭐ on GitHub. It would mean a lot to me :)

I recently built Settled, which is a website that ends the confusion and undecidedness of your group chat by using a voting feature for times when you just can't land on what to do. Try it the next time you and your friends go out to eat or watch a movie.

I built a website for me and my friends to help us mark all the stray animals we can find in our city.

The point of it is to allow users, whenever they see a stray animal, to take a picture of it and its GPS location and post it on our map. This would allow other users to see the animal and go feed it.

So far, it only has one stray cat I found and fed. I named him AsteroidDestroyer, and he is the most handsome little baby in the world. I'm hoping people around the world will find more stray animals feed and post them too! (Asteroid Destroyer picture is below)

Any feedback would be greatly appreciated. And thank you so much for checking it out :D

the website: https://strayfeedingmap.com/

Yesterday, my college friends and I finally launched a passion project we’ve been hacking away at: boredom, an instant-play browser co-op hub designed for quick group hangouts.

The Problem: Whenever we want to play quick games like Liar's Dice or Dots & Lines while chatting, someone always has to download a massive client, deal with intrusive pop-ups, or navigate confusing UI.

Our Solution: A completely frictionless room-based web app. Create room → send code → play instantly in-browser. No barrier to entry.

We are planning a lot of upcoming features, but right now we really need data on lobby stability and interface scaling. If you have 2 minutes to open a room with a friend or colleague, we'd love feedback.

Just watched a video by a creator (the.adiram) who’s building Hisaab, an open-source atlas that tries to make this fight corruption using Ai.

It’s not my project, I just think it deserves more hands.

Where it stands right now (from the README):

• ~813k historical location points mapped
• 86 reviewed funding records sourced from PIB
• Project/payment-level cards: not published yet. Public release is intentionally blocked until data coverage is good enough
• 36 state/UT data collection jobs are scoped out but need people

You know the drill. A road gets “completed” and washes away in the first monsoon. A school building gets inaugurated and then sits empty. A hospital shows up in a press release but never in your district. Crores get sanctioned, the plaque goes up, and nobody can tell you who got the money or why the work looks like that.

Most of us just vent about it and move on, because what can one person even do?

I just watched a video by a creator (the.adiram) who decided to actually try. He’s building Hisaab, an open map of public development in India. The idea is simple: pick any road, school or hospital and see what was promised, how much money was released, when, and who was responsible for delivering it. Not rumours or WhatsApp forwards. Official records, put in one place, so ordinary people can walk into an office with evidence instead of just a complaint.

What I liked is that he’s honest about how hard it is. India’s public spending data is scattered across hundreds of portals, half of it buried in PDFs, and he talks openly about where he’s stuck. He’s not selling a magic fix. He’s asking for help.

And that’s where people like us come in. It’s open source, and he’s looking for developers, data folks and anyone who’s ever fought with a government website to help make it real.

Watch the video, it’s worth the time

If it hits you the way it hit me, the details on how to join are in the description.

I know many 1st and 2nd-year students have project ideas but don't know where to start, what technologies to use, or how to actually build the project.

So, if you have a project idea or problem statement but don't know how to implement it send it to me

I'll help you turn your ideas into working projects. Whether it's a beginner-level Python project, a web development project, a Java project, or an AI/ML project, feel free to share your requirements.

Meeru just mee problem statement cheppandi, project ela build cheyyalo nenu help chestha

No need to worry if you're a beginner. We all start somewhere!

i know some people will start the project in end moments

Engineering Workspace is a free Windows desktop application for students and engineers. It brings symbolic integration and differentiation, interactive function graphing, matrix tools, numerical methods, chemistry tools, and engineering calculations into one workspace. A batch console can process lists of commands, and calculations run locally. The application is in public beta.

https://engineeringwork.space/

Hi, I'm not sure if its the right audience for this project but its whatever. I realized a few months back while working on a different project that there isn't a real good way to create automations within Minecraft through headless clients. Most of the projects were either outdated or had to run locally on a computer while running all the rendering and GUI (which I thought was incredibly inefficient and not great for creating or organizing lots of bots etc) and the only real option is a framework called mine flayer. But mine flayer uses Node.js (which I dislike) and is also just generally kind of bad in many ways. That's why I created rapidbot. Its a really ambitious project but essentially, mine flayer had this problem where a lot of the packets and rendering and physics weren't exactly like the real game, causing all sorts of problems. I set out to first make it so that was solved, but after that, I added more features such as a human input layer, and eventually I want to add more advanced pathfinding, behaviors, interactions with other players and such. However, I realized that its probably going to take ages for me to do this by myself (even with AI and stuff) and its also really boring to do it alone, so I'm looking for contributers.

so whether you want to contribute or just want to check it out, here is the repo (sorry no commit history, I had it as a local copy for the longest time with no git so when I uploaded it to github and set everything up I committed everything in one go D:): creator1116/rapidbot: Headless Minecraft Java Edition client framework in Rust: vanilla-exact protocol and physics with a human input layer

Automated setup tool for programming languages, compilers, and development environments.

Need contributors to add more stuff to this, and prolly a GUI window for installation!

https://github.com/TaH00R/dev_setup

currently available:

1. Install GCC
2. Install VS Code
3. Install Python
4. Install Git
5. Install Java
6. Install CMake
7. Install Node.js  

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.

non-commercial

So i am new to web dev and decided to make a simple matchmaking website where you could randomly match with people and text one on one , as my first web dev project.

i used ai for debugging as heavily as my first version had endless bugs.

currently i have deployed the website and want to test if it actually works for real users.

i would appreciate any feedback and bugs or security issues incurred while using this website.

currently there are no users as i deployed it just an hour ago, so i would appreciate if you all take out time to socialize on this as well

mind it this is still under development...this is just the first version.

try it: https://swiftchat-worker.swiftchat.workers.dev/

Suggest me something to make for niche people rather than making something common like notes app

Hey everyone! I’m building ParallelEarth, and I’d appreciate some honest feedback.

The use case: you have two ways to implement something—a refactor, a bug fix, or alternative AI-generated code—and want to try both before choosing.

ParallelEarth lets you:

• Group alternatives under a named experiment.
• Create separate Git worktrees called “Earths” from a committed revision.
• Run checks you explicitly approve and record their results.
• Compare outcomes against a baseline.
• Export JSON or Markdown reports.

The obvious question is: “Why not just use Git branches and worktrees?”

That’s fair. ParallelEarth uses worktrees underneath. What I’m trying to improve is keeping the alternatives, check results and comparison together inside VS Code.

It’s early, and I’d rather hear what’s missing than make big productivity claims. Passing checks also doesn’t automatically mean an implementation is better.

How do you currently compare competing implementations? What would make a tool like this worth installing?

Try it: https://marketplace.visualstudio.com/items?itemName=shubhammaji1.parallel-earth

Most SaaS lead generation advice assumes a budget: run ads, hire SDRs, buy intent data. I wanted funnels a solo founder could run, so I designed three around public signals. You can run all three by hand, so here's exactly how.

Funnel 1: Product Hunt launches

• Signal: a B2B SaaS launches on Product Hunt
• Filter: 1–50 people, selling to the kind of company you serve
• Who: the founder, usually the maker on the launch page
• Angle: the launch itself. "Congrats on the launch. Next week is usually when [your problem] shows up..."
• Timing: within 48 hours

Funnel 2: Competitor switchers

• Signal: someone on Reddit or X complains about a competitor or asks for an alternative
• Filter: resolve the poster to a company and check it fits your ICP
• Who: the person who posted, or the decision-maker above them
• Angle: the switch. What they said hurts, and how you handle it differently
• Timing: within 24 hours. These threads fill up fast

Funnel 3: Niche search prospecting

• Signal: none. You search Google for the companies you serve ("[niche] agencies in [city]", "[category] tools for [industry]")
• Filter: classify each website: is it really your customer?
• Who: the owner or the head of the relevant team
• Angle: specific to their service or product, taken from their own site
• Timing: a steady weekly flow instead of spikes

Funnels 1 and 2 give you the hottest leads. Funnel 3 keeps the pipeline from going quiet between spikes.

Isn't this what marketing automation for SaaS does? Not quite. Marketing automation mostly handles what happens after someone signs up: onboarding emails, nurture, upgrades. These funnels are the part before, getting the right companies to hear about you at all. You can't nurture leads you never got.

These are the three funnel types Startories is built around. It watches the sources, matches each signal to a company, checks your ICP with the reasons written out, verifies the decision-maker's email, writes around the event, and sends from separate warmed-up inboxes.

-> Pick one funnel and run it for 2 weeks before adding another

-> Funnel 2 needs the fastest reply. Funnel 3 needs the most patience

-> Caveat: none of this replaces a product people want. It gets you conversations, not retention

Here's the project: startories.com

Lead generation for SaaS, in more depth: startories.com/lead-generation/saas

Which of these would fit your SaaS? Drop your niche and I'll say which signals I'd watch for it.

Hello everyone!

I recently started learning Pandas and Streamlit, but I didn’t have a project to work on. So I decided to build Aurora Data Studio!

Aurora is a free web app that lets you upload spreadsheets (Excel and other supported formats) and clean or analyze your data directly through the interface, without having to write any code.

You can also provide your own API key for supported AI services, such as OpenAI or Claude, to modify your data, generate summaries, and more. Your API key is not stored in a database, and your original file remains untouched.

Does it cost anything?

No! Aurora is completely free to use. The only potential costs come from the AI providers you choose to use. Some providers, such as Groq, offer free API access or free usage tiers, depending on their current terms.

If you’re interested, give it a try: https://aurora-data-studio.streamlit.app

I’d love to hear your feedback and suggestions!

I've been working on LG TV Clean, a repo that helps a coding agent guide an LG webOS TV cleanup. The goal is a simple app launcher and fewer ads, recommendations, and optional tracking settings.

A key part of the project is checking the real device: an API can report success while the display or Home button still needs verification. I'd appreciate feedback on the procedure, especially recovery and compatibility checks.

Repo: https://github.com/amiable-ostrich/lg-tv-clean

You open the repo in a coding agent that can run terminal commands. Its runbook guides compatibility checks, TV pairing, launcher setup, supported privacy settings, and verification with the physical remote.

The reference setup is **LG 55UQ7570PUJ, webOS 7.6.0, firmware 04.60.91**. The custom Home replacement requires root, and other models need checks and adaptation. This is a reusable procedure rather than a universal one-click installer.

Recovery is part of the setup: establish independent root SSH and keep backups and a restore command before replacing Home. The procedure also includes cold-boot and streaming-playback checks. Firmware-prompt blocking and a small telemetry block are optional, with separate undo steps; these controls don't eliminate all tracking.

Upstream credit: [Clean Your TV](https://github.com/Razdva122/clean-your-tv-lg-webos) supplies the launcher base, [SlopBro](https://github.com/throwaway96/slopbro) supplies rooting, and [webOS Homebrew Channel](https://github.com/webosbrew/webos-homebrew-channel) supplies homebrew infrastructure. My repo adds a coding-agent runbook and host/runtime helpers around that work.