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.
More than 135 open hardware devices flashable with your own firmware
31–40 of 51 posts
Re: More than 135 open hardware devices flashable with your own firmware
#32Re: More than 135 open hardware devices flashable with your own firmware
#33Not commenting on the content itself (others have done it better) but anybody getting tired of seeing the same vibe coded websites over and over again?
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.
Re: More than 135 open hardware devices flashable with your own firmware
#34Two 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.
Re: More than 135 open hardware devices flashable with your own firmware
#35Re: More than 135 open hardware devices flashable with your own firmware
#36Not commenting on the content itself (others have done it better) but anybody getting tired of seeing the same vibe coded websites over and over again?
I actually didn't notice since there weren't gradients. 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.
Re: More than 135 open hardware devices flashable with your own firmware
#37> more than 135 136?
Re: More than 135 open hardware devices flashable with your own firmware
#38Wow, the UX kind of sucks. I just wanted to browse the devices - no way to do that, only option is an 'ai' search. Ok, I type in "Show All Devices" and it canoodles for about 30 seconds (great use of compute resources) only to apparently come up with the phrase "Browse all devices available in the directory without specific project-based filters." that it then seems to feed into the actual search tool... which then s…
Re: More than 135 open hardware devices flashable with your own firmware
#39Earlier quoted context omitted.
This is "Open Hardware" which usually means open PCB or chip schematics, so people can modify or extend the board. OpenWRT is "Open Software that runs on closed 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...
Yeah, that OnePlus phone is defo the very opposite of open hardware...
Re: More than 135 open hardware devices flashable with your own firmware
#40Looks good, but it'll probably take a while until it's anywhere close to the coverage of existing repositories: 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 com…
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.