home.social

#defined — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #defined, aggregated by home.social.

  1. It will be a #fundraising powerhouse! That is one of the points of it. The end of #homelessness. #Nft auctions. #SOL / #ETH. #Artist contributors for network credit. #Buyers help build the #fund to #end #homelessness in some #defined #location. And then nationally. Momentum matters ‼️ 🗽🗽🗽🏄🏻‍♀️🌊🌊😻😻😻

  2. DashioSAMD_NINA (1.2.3) for ARDUINO_SAMD_NANO_33_IOT/defined ARDUINO_SAMD_MKRWIFI1010/defined ARDUINO_SAMD_MKRVIDOR4000 by DashIO Connect

    ➡️ github.com/dashio-connect/ardu

    Arduino SAMD NINA library for communicating with the free Dash IoT dashboard app.

    ARDUINO_SAMD_MKRWIFI1010 ARDUINO_SAMD_MKRVIDOR4000

  3. DashioSAMD_NINA (1.2.2) for ARDUINO_SAMD_NANO_33_IOT/defined ARDUINO_SAMD_MKRWIFI1010/defined ARDUINO_SAMD_MKRVIDOR4000 by DashIO Connect

    ➡️ github.com/dashio-connect/ardu

    Arduino SAMD NINA library for communicating with the free Dash IoT dashboard app.

    ARDUINO_SAMD_MKRWIFI1010 ARDUINO_SAMD_MKRVIDOR4000

  4. #Defined tauchte zum ersten Mal im Protokoll der 189. Sitzung des 20. Deutschen Bundestages am 27.09.2024 auf. Das Protokoll findet sich unter dserver.bundestag.de/btp/20/20

  5. DashioSAMD_NINA (1.2.1) for ARDUINO_SAMD_NANO_33_IOT/defined ARDUINO_SAMD_MKRWIFI1010/defined ARDUINO_SAMD_MKRVIDOR4000 by DashIO Connect

    ➡️ github.com/dashio-connect/ardu

    Arduino SAMD NINA library for communicating with the free Dash IoT dashboard app.

    ARDUINO_SAMD_MKRWIFI1010 ARDUINO_SAMD_MKRVIDOR4000

  6. DashioSAMD_NINA (1.1.0) for ARDUINO_SAMD_NANO_33_IOT/defined ARDUINO_SAMD_MKRWIFI1010/defined ARDUINO_SAMD_MKRVIDOR4000 by DashIO Connect Limited

    ➡️ github.com/dashio-connect/ardu

    Arduino SAMD NINA Classes to support communicating with the free Dash IoT app.

    ARDUINO_SAMD_MKRWIFI1010 ARDUINO_SAMD_MKRVIDOR4000

  7. @puppygirlhornypost yeah, like the first exploits published against NT4 when it came out. On the windows API call to move a window on screen, feed the 64-bit window handle param a 32 bit value (many windows programs had #defined a 32 bit -1 pattern) and BOOM!!! instant dead system.

    They had moved the GUI code into ring zero for performance reasons. 😱

  8. @Sweetshark @mcc Honestly this doesn't seem like good advice to me. I'm not saying #GoLang is perfect, but it does have solid namespacing, and is not vulnerable to anything remotely like someone 30 years ago having #defined Always.

  9. There were also "#define DEVICE_FOO_VID VENDOR_VID" defines, where "VENDOR_VID" was #defined in another .h file, and then drivers used DEVICE_FOO_VID.

    What is the point here? Are we concerned that vendors will suddenly change their pre-registered ID numbers for some (but not all) existing devices?

    It just makes things harder to follow. It probably made sense historically, but after being repeated 50x it's just a mess. Now we're just using the centrally-defined "VENDOR_VID" directly.

  10. @hniemeyer I can see multiple fundamental problems in your problem:

    * you don't use Catch2
    * you don't use modules
    * you use macros

    I can Assert you that there is nothing wrong with macros as long they're in someone else's code.

    Caution: you need to check how I've #defined Assert and possibly other words ...