3 ms·
Storing 2 bytes of data in your Logitech mouse
- kstrauser 7mo agoThat’s a beautiful writeup. Why did I do this ridiculous and impractical thing? To learn how to do it! Well done.
- netsharc 7mo agoWritten by AI? The whole text smells like it, this sentence near the end is the most suspicious: "The 2 bytes were never the goal. The goal was to see how far in I could get."
- andy99 7mo agoI stopped reading at “ 2 bytes on a 64GB stick is embarrassing. 2 bytes in your mouse is art.” No way to know for sure, but worth flagging.
- _uajh 7mo agoSo yea fair enough for being skeptical. That’s just how I write. I normally don’t do technical blog posts and in my free time I tend to write more in a bookish way. Especially since it’s not my first language. Thanks for checking the post out and this helps me
- llbbdd 7mo agoWrite it yourself. This comment is fine, it didn't matter if your English isn't perfect. I got you. LLMisms sour the whole post with a bad tone and I and others won't stomach it. The impression of effort is more important.
- atomlib 7mo ago> That’s just how I write. You aren't answering the question. Did you use AI to write this text? How much of the text was generated by AI? I see the text is edited, and I no longer can find the fragments the people above complain about. Why did you edit the text?
- _uajh 7mo agoAI did help me outline. I didn’t use generated text. I edited because the criticism was fair. After saying it out loud the phrases sounded weird. That’s useful feedback and I’d rather fix it than argue about it.
- llbbdd 7mo agoI hit "No rounding, no validation, not a "that's not a real DPI" error." and stopped. Garbage
- NooneAtAll3 7mo agois this comment written by Ai? the first sentence is the most suspicious - too many comments accusing blogposts of being made by Ai for basically no reason
- llbbdd 7mo agoIt's really not that hard to tell
- Joyfield 7mo agoGuess I should start buying mice instead of expensive RAM-sticks.
- 0x38B 7mo agoI laughed at this bit, because I've also tried to debug things only to find it wasn't telling me what was wrong with my code (my own error, perhaps - a forgotten --verbose or -v): > Turns out macOS's IOHIDManager silently blocks the longer HID++ report format you need to actually write to it. The OS just drops the packets. No error, no explanation, nothing. I found this out after writing a pile of probe code and staring at empty responses for longer than I'd like to admit.