Arlinda Eastwood

I just want to say a huge thank you to everyone who tried Planelo after the launch and took the time to share feedback, suggestions, and bug reports.

I ve been going through all of it carefully and I m already working on a new update that focuses on fixing the most painful issues first and polishing the overall experience.
An improved version with these fixes will be live very soon

If you want to be part of shaping Planelo further, I d love to invite you to join our Discord community.
That s where you can:

• share feature ideas and improvements

• report bugs or UX issues

• discuss workflows and use cases

• influence what I build next

Hey folks,
Hope everyone had a good relaxing Happy New Years!

Here's what we're shipped recently:

• Support for select/radio/checkbox fields (more betterments coming soon!)

• Alternate fill modes that trigger superfill.ai autofill directly from form fields & context menu without the need to open extension UI.

I m a solo dev working on API Radar a live feed of leaked API keys and secrets found in public GitHub repos. Later today I m shipping a big rebuild of the search/detection engine, and I d love to sanity check a few things with this crowd before it goes fully live on Product Hunt.

A couple of questions for folks in security, DevOps/SRE, or backend roles:

• What s the most useful way to present this kind of data so it actually helps you fix issues? (per repo view, per provider, timelines, alerts, something else?)

• Where s the ethical line for you? The data is from public repos only, but what would make a tool like this clearly defensive and helpful rather than sketchy or abusable?

Blunt feedback is welcome on the idea, UX, or even whether this should exist at all.