Thanks for the wiki -- I have always been interested in hardware hacking but I have always felt overwhelmed as I didn't know where to start. I believe this kind of resource can greatly help with that, especially the case studies. However, I can't help but feel that a major part of the content is LLM-generated, or at least LLM-rewritten. It feels off and uninteresting to read, honestly. Is it the case? To support my c…
I created an open-source Hardware Hacking Wiki – with tutorials for beginners
21–30 of 126 posts
Re: I created an open-source Hardware Hacking Wiki – with tutorials for beginners
#22Earlier quoted context omitted.
I just don't want anyone to copy the content and sell it. It's meant to be freely accessible to everyone.
That's fine. It's just not open source. Don't call it open source if it's not. Definition: https://opensource.org/osd
Re: I created an open-source Hardware Hacking Wiki – with tutorials for beginners
#23Earlier quoted context omitted.
I just don't want anyone to copy the content and sell it. It's meant to be freely accessible to everyone.
That's fine. It's just not open source. Don't call it open source if it's not. Definition: https://opensource.org/osd
I generally think of open source as where I can see the code and freely modify it, not necessarily freely commercialize it on my own.
Re: I created an open-source Hardware Hacking Wiki – with tutorials for beginners
#24Earlier quoted context omitted.
Wait and see. You're not paying attention now, but it's not too late to start. Go to your favorite programming puzzle site and see how you do against the latest models, for instance. If you can beat o1-pro regularly, for instance, then you're right, you have nothing to worry about and can safely disregard it. Same proposition that was offered to John Henry.
Please reformulate your argument, and I will check back tomorrow: https://www.youtube.com/watch?v=aNSHZG9blQQ LLMs are rules based search engines with higher dimension vector spaces encoding related topics. There is nothing intelligent about these algorithms, except the trick ones play on oneself interpreting well structured nonsense. It is stunting kids development, as students often lack the ability to intuitively…
Otherwise, you're going to spend the rest of your career saying things like, "Well, OK, so the last model couldn't count the number of Rs in 'Strawberry' and the new one can, but..."
Personally, I dislike being wrong. So I don't base arguments on points that have a built-in expiration date, or that are based on a fundamental misunderstanding of whatever I'm talking about.
Re: I created an open-source Hardware Hacking Wiki – with tutorials for beginners
#25Earlier quoted context omitted.
That's fine. It's just not open source. Don't call it open source if it's not. Definition: https://opensource.org/osd
>Free and open-source software (FOSS) or free/libre and open-source software (FLOSS) is openly shared source code that is licensed without any restrictions on usage, modification, or distribution. Confusion persists about this definition because the "free", also known as "libre", refers to the freedom of the product, not the price, expense, cost, or charge. For example, "being free to speak" is not the same as "free…
what you're describing is usually called "source-available".
Re: I created an open-source Hardware Hacking Wiki – with tutorials for beginners
#26Backstory: at one point I was trying to use elixir/nerves on an rpi to manipulate a few sensor modules to try and produce a race lap timer for motorcycles: https://github.com/whalesalad/rabbit/blob/master/lib/rabbit/...
I bit off more than I could chew: learn elixir, learn i2c, and produce a novel library for controlling the ublox chip since nothing existed for Elixir.
But when it comes to managing the state of the device, reading/writing memory, etc.. that is all very foreign to me (I am used to sockets, http apis, etc) like request/response style interactions.
Re: I created an open-source Hardware Hacking Wiki – with tutorials for beginners
#27Earlier quoted context omitted.
I just don't want anyone to copy the content and sell it. It's meant to be freely accessible to everyone.
That's fine. It's just not open source. Don't call it open source if it's not. Definition: https://opensource.org/osd
Re: I created an open-source Hardware Hacking Wiki – with tutorials for beginners
#28Unfortunately not Open Source, in the common definition of the word. From the license.md [0] page, under "Terms": > Exemptions: Commercial Use: For inquiries regarding commercial use, please contact the author. [0] https://github.com/f3nter/HardBreak/blob/fd3d2d4cd17624a3f62...
Re: I created an open-source Hardware Hacking Wiki – with tutorials for beginners
#29Re: I created an open-source Hardware Hacking Wiki – with tutorials for beginners
#30Earlier quoted context omitted.
>Free and open-source software (FOSS) or free/libre and open-source software (FLOSS) is openly shared source code that is licensed without any restrictions on usage, modification, or distribution. Confusion persists about this definition because the "free", also known as "libre", refers to the freedom of the product, not the price, expense, cost, or charge. For example, "being free to speak" is not the same as "free…
the FSF/OSI are big on emphasizing that "free/open" means more than exposing the designs and mechanisms; it means guaranteeing certain freedoms and rights to the users of your software. what you're describing is usually called "source-available".