Two thoughts - (1) is your device list some state secret that you have to hide behind a search functionality? Because it would be nice to be able to browse through it without needing to engage in some sort of 'search'. (2) can you provide another option besides an ai search that is so intelligent that it has superseded the ability to do wildcard searches?
Edit: same feedback, but for the projects section as well.
- no, the search list is not secret.. you can even convert any page to markdown https://openhardware.directory/devices/md - you just have to add /md to any page
- also, you can browse it with llms.txt (https://openhardware.directory/llms.txt)
I'm open to new ideas on how to improve the search experience
Based on the title, I like the idea. It would be cool if manufacturers are more deliverable with their releases of firmware and developer tools. Like... if you're selling refurbished versions of a product, it makes sense that it's internals and firmware are open source.
On one side what you are saying it's true but on the other side it rings like "it was better when it was worse" which I always despised in the past. It's hard to accept when it's your own craft that is being automated but we must move on. Otherwise we'll be like the mechnical clockmakers complaining about Casio watches.
but i'm open to feedback so we can make a better experience for all of you ;)
Feels more like AI slop list of "a bunch of hardware that you can buy from hobbyist electronic stores" which has no idea what it wants to be, shiny on surface but deeper you look less sense it makes. Not surprised, the company who made it (likely single person) describes itself as "We're crafting interesting tools to speed up software development using Artificial Intelligence."
Good chunk of that stuff is not open hardware by any definition -> neither the hardware design being open nor the firmware not even community written firmware for proprietary hardware.
If you ignore the poor description of the site is the parametric search at least good? The values in parameter dropdowns seem to be filled based on currently displayed items, that might be fine for narrowing down once you already made a search but for initial search it means you get random subset of available values. The fact that whole thing is non-categorized, random mix of mismatched type of hardware doesn't make the parametric search better. Good parametric search needs well curated and structured database of descriptions made by people who understand corresponding product category, otherwise it's garbage in garbage out.
Having to wait half a minute while AI is reticulating splines even when you used quite specific keywords isn't a good search experience either.
So if it's not a good list of open hardware, not a good list of hardware you can flash open firmware, not a good search for electronic components what is it good for? Only value I see is as a fuzzy set of links and ~~tags~~ for exploring a subset of related hardware topics.
Edit: not tags those are broken. #tags return error, other tags(uses cases) and other other tags(compatible firmware) in many cases returns only 1-2 results which doesn't even include the item where you clicked on tag even though there are a lot more items using it.
[1] https://openhardware.directory/devices/slamtec-rplidar-a1
I've contributed some work to it. Improved the pulsometer so it could also be used as an asthmometer which I really needed. Also improved the TOTP auth apps a bit. I was even one of the maintainers for a while.
It's an awesome project to hack on. Lots of nice people in the community. Highly recommended.
Can I give it a link to my weird (but open) hardware?
After checking a couple, Kind of seems like a lot of boards on this "open hardware" list might not actually be open hardware?
Here's an example of what open hardware is supposed to be: https://github.com/greatscottgadgets/ubertooth/tree/master/h...
136?
https://templates.blakadder.com/ has almost 3,000 devices flashable onto Tasmota firmware.
For older Tuya devices there's https://github.com/tuya-cloudcutter/tuya-cloudcutter
OpenBeken https://github.com/openshwprojects/OpenBK7231T_App covers 800 of the newer generation Tuya devices.
And there's a large community adapting ESP32 devices onto https://esphome.io/
Also, I'm curious — how do you think we can make the device pages even better? My personal problem is that I want to find devices for a specific use case, and the issue is that it's pretty hard to extract real-life use cases for all the scraped devices. We will need a way to extract these insights from the internet.