jerknextdoor

I'm not sure it says much, but I met the person who wrote the post you linked to at ATmosphere this year. To me that says that maybe they're not as worried as you about ATProto's PQ exposure. I overheard lots of discussions about the topic, but I'm not an expert so I can't give much more insight than that.

From the article:

> "What does this mean for you as a Signal user? First, when it comes to your experience using the app, nothing changes. Second, because of how we’re rolling this out and mixing it in with our existing encryption, eventually all of your conversations will move to this new protocol without you needing to take any action. Third, and most importantly, this protects your communications both now and in the event that cryptographically relevant quantum computers eventually become a reality, and it allows us to maintain our existing security guarantees of forward secrecy and post-compromise security as we proactively prepare for that new world."

I was curious to try this out as it might actually solve a minor problem of mine right now, but it crashed as soon as I tried to open a PDF.

Installed from git using cargo 1.80.1 on Ubuntu 22.04 on an AMD Framework laptop if that's of any help.

I only have 32 karma and I have the ability to flag.

I'm not sure that the real target is vegans/vegetarians. I don't eat, nor desire, that many of these substitutes and neither do the friends I've had for 20+ years of this diet. I believe these products are more for people who aren't committed to making a full lifestyle change, but just want to have 'meatless Mondays' or the like.

I am so glad that I am not the only person that has this frustration. I wish I could remove other apps or give them lower priority in the dash, but this is absolutely the worst.

ESP is cheap and good enough for a lot of things...but there are plenty of projects where we need something smaller, lighter, faster, more power efficient, etc. If I don't need WiFi, why have it sucking up battery? Most (nearly all) of the projects we do use other long range wireless protocols. WiFi is just nice for prototyping. There are lots and lots of reasons to move from one board to another or to build your own.

As far as MicroPython goes, same thing. It's great for prototyping, but it's still somewhat hackey, slow, not that memory efficient. It doesn't need to be for its use case...but for production ready sensors I need to be sure to work the best they can off the shelf, I'm gonna write that in C/C++ or most likely Rust (if there is an LLVM backend for the chipset).

I'm not an EE on our team, so I can't be sure, but I do know it happens. I don't know what they do to keep quality up. Even if they do fail, they're cheap enough that its not a problem to replace the whole sensor. There are also fail-safes so that nothing mission critical can happen if a few things go down.

We use the ESP8266 and ESP32 at my company for really quick, cheap prototypes. It started out as a way for us to add wifi to a microcontroller, but now we just use it as the microcontroller itself. We use it for all kinds of small hardware devices, sensors, and actuators. Its pretty fantastic to be able to prototype cheaply in microPython and then later port the board and code to C/C++/Rust when we need to go to production.

I'm not sure what issues you've been having, but I've been using, OpenCV with 3.5 for over a year with no problems. The docs are out of fate, but that's because the code is all auto-generated.

I'm not seeing a license anywhere. What gives the impression that it's open source?