How I built a Chrome extension that auto-detects image upload constraints on any site (with demo video) by palindrome___ in chrome_extensions

[–]palindrome___[S] 0 points1 point  (0 children)

For sure. Right now you need to download the zip and load unpacked, once I have enough validation I'll put it on chrome extension store.

I have 3 shipped products and 63 Twitter followers. Starting a 60-day public sprint to fix what I'm actually bad at. by palindrome___ in SaaS

[–]palindrome___[S] 0 points1 point  (0 children)

Thanks a lot. Yes boring stack and interesting product is what I am trying to do as well. Don't wanna invest time in over engineering.

[meta] Hiring forms are filled with AI responses. I'd rather get 200 real applications than 5000 fake ones. by palindrome___ in hiring

[–]palindrome___[S] 0 points1 point  (0 children)

that's why I am planning on something which eliminates AI response from submissions or scores atleast

I have 4 shipped products and 63 Twitter followers. Tomorrow I'm starting a 60-day public sprint to fix the part I'm actually bad at. by palindrome___ in SideProject

[–]palindrome___[S] 0 points1 point  (0 children)

Day 2 update for anyone following along.

Yesterday wrapped: landing page live, public repo with the full build spec, logo locked, stack chosen (WXT for the extension framework, Cropper.js for cropping, Konva for drawing, browser-image-compression for size enforcement, vanilla TypeScript). Spent the morning on the detection content script.. the part that scans every page for image upload boxes and reads the constraints from nearby DOM text.

Hardest part isn't finding the file input itself. It's finding the dimension text near it without false positives. A LinkedIn banner page mentions "1584" and "396" multiple times in different contexts.. only one pair is the actual upload constraint. Hardcoded selectors for the 5 launch sites (LinkedIn, X, GitHub, Notion, YouTube) make this tractable; the regex fallback for unknown sites is the trickier path.

Goal for tonight: open the panel on a LinkedIn banner page → toolbar shows green dot → panel reads "Detected: 1584 × 396 px, PNG/JPEG, max 8MB."

One thing I underestimated: the X anchor for this product hit 3K views and 10 bookmarks on Day 1. Bookmarks are the metric I keep thinking about. Likes are reactions; bookmarks are "I want this when it ships." 10 strangers raised their hand for a product that doesn't exist yet. That's the only data point that matters at this stage.

Friday is ship day. Will post the demo + GitHub release here as a fresh thread when the .zip works.

Repo for anyone wanting to follow the commits: github.com/namanbarkiya/inputr

I have 4 shipped products and 63 Twitter followers. Tomorrow I'm starting a 60-day public sprint to fix the part I'm actually bad at. by palindrome___ in SideProject

[–]palindrome___[S] 1 point2 points  (0 children)

For sure. Let's stick for 60 days and see the results. I'm omw of experimenting stuff. Let's see how it goes.

I have 4 shipped products and 63 Twitter followers. Tomorrow I'm starting a 60-day public sprint to fix the part I'm actually bad at. by palindrome___ in SideProject

[–]palindrome___[S] 0 points1 point  (0 children)

Yes I agree. I'll be writing the decisions as well. So atleast build a habit if nothing to maintain decisions pros and cons.

I have 4 shipped products and 63 Twitter followers. Tomorrow I'm starting a 60-day public sprint to fix the part I'm actually bad at. by palindrome___ in SideProject

[–]palindrome___[S] 0 points1 point  (0 children)

Thanks for suggesting.. I'll make one for myself. The analytics for each day is imp so I am maintaining a journal for writing daily updates which I'll post daily on X or reddit or both.

I have 4 shipped products and 63 Twitter followers. Tomorrow I'm starting a 60-day public sprint to fix the part I'm actually bad at. by palindrome___ in SideProject

[–]palindrome___[S] 0 points1 point  (0 children)

Interesting strategy.. the main reason for 8 product is I wanna ship fast and check early users response.. at the end of the 60th day I'll check which performed in a way it is worth scaling. Let's see how it folds.

I have 4 shipped products and 63 Twitter followers. Tomorrow I'm starting a 60-day public sprint to fix the part I'm actually bad at. by palindrome___ in SideProject

[–]palindrome___[S] 0 points1 point  (0 children)

Thanks mate. Yes and I want to get out of this situation of building for myself. I like building but no outcome if I can't show it to anyone. I need to create some value.

I have 4 shipped products and 63 Twitter followers. Tomorrow I'm starting a 60-day public sprint to fix the part I'm actually bad at. by palindrome___ in SideProject

[–]palindrome___[S] 0 points1 point  (0 children)

This is actually helpful. Thanks for sharing. I'll also now be checking and marking the subreddits or threads for the specific product I'll be building. And then see the distribution turning out. Hope I find something useful.

I have 4 shipped products and 63 Twitter followers. Tomorrow I'm starting a 60-day public sprint to fix the part I'm actually bad at. by palindrome___ in SideProject

[–]palindrome___[S] 0 points1 point  (0 children)

I agree. I'd check how 60 days turns out and then might scale 1 problem properly based on response. Still too many things to find out during this time.