Software Engineer, Linux Enthusiast, OpenRGB Developer, and Gamer

Lemmy.world Profile: https://lemmy.world/u/CalcProgrammer1

  • 0 Posts
  • 288 Comments
Joined 3 years ago
cake
Cake day: June 9th, 2021

help-circle
  • Mozilla sold out a long time ago, they are nothing like they used to be. Everyone should be ditching Firefox for forks if possible. Yes, Firefox is still miles ahead of anything Chromium-based but we can’t trust Mozilla to not screw over their users anymore (and it’s been apparent for YEARS…Pocket, “Sponsored” shortcuts and links, Mozilla VPN popup ads, this behavior is hardly new). What can we trust? Firefox forks with the bullshit stripped out, mostly. I’ve been using LibreWolf for several years on my Linux, Windows, and MacOS systems now. I originally switched because of the Mozilla VPN popups but at the time, complaining about those popups was met with a bunch of Mozilla apologists going “it’s not that bad” “they’re a big company and they need their precious monies”…no. That was ADVERTISING front and center, and it was in Firefox years ago. So was Pocket. So was having Amazon links auto-filled on the new tab shortcuts. Go to something that isn’t run by money. Go to a community-maintained and sanitized fork.








  • I wish these implementations of secure boot were designed more to protect the SOFTWARE against “theft” than the HARDWARE against “tampering”. Let us wipe the secure boot keys, but in the process erase the firmware (or have the firmware encrypted so that erasing the keys renders it unbootable) and then allow new code to run. Blocking third party firmware on consumer devices is a shit move. It just creates more e-waste when the OEM stops updating it and the community can’t make their own replacement firmware.




  • Not really a fan of putting secure boot on. The only purpose that serves is locking the customers out of their purchased hardware. Raspberry Pi is clearly not targeting the maker market with those changes, they want that corporate money and are willing to stick the finger to hackers and makers in the process. Can’t make custom firmware if you can’t boot it.





  • I’m not sure about FF specifically, but 99% of the time you’re connecting a microcontroller to a PC you’re doing so over a serial port (UART) of some sort. It may be a physical COM port or it may be a USB to serial adapter or even a purely virtual serial port over a USB connection, but the methodology is all the same. Unless you are running a serial terminal on that port (as in, a commandline on your PC served on the given /dev/ttyX interface, not a terminal emulator letting you read/write from the port), the microcontroller can’t just run scripts on the PC. Instead, you will want to write a script/program that opens the port and waits for a command to be sent from the microcontroller, then that listener script can execute whatever functionality you require. Note that only one application can have the port active at a time, so if your listener is a separate program from your event handler, you will have to close the port on the listener before running the handler, then reopen the port on the listener once the handler is done so it can start listening for the next event. Better to just make it all one program that is always running on the PC and does both listening for events and handling them so there’s only one program that needs access to the serial port.