> "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."

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

[1] https://blog.adacore.com/adacore-and-ferrous-systems-joining...

[1] https://www.netlify.com

You can follow the progress here: https://areweasyncyet.rs/

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've come to the conclusion that it's not malicious (or even 'Not Invented Here' syndrome), but ignorance and a complete misunderstanding of the FOSS world. It seems that a lot of the people and groups involved come from a corporate background where they had to build and keep everything in house. Whenever I mention not reinventing the wheel, building on others work, collaborating with other groups, or opening up our the data I'm met with mostly blank stares. (I could go on and on about this disconnect and why I think it's happening, but it's not directly relevant to your comment.)

I think the major issue is that non-developers (and even some developers) have no idea how to work with others. It isn't that they don't want to or are refusing to, they fundamentally just don't know how to. The idea of working with more than the fifteen people that are present in the room is mind-boggling, let alone the idea of working with people all around they world they may never meet. On top of that simple issue you have the same concerns you do with any person outside the Open* communities: security, trust, liability, etc. Have you ever seen a layperson look at a software/data license? It's beyond overwhelming, so they all go back to whats safe, even if it's not the right thing for their goals or the community as a whole.

To begin to remedy this I think we have a lot of work ahead of us...starting with making the ideas and principles of Openness more accessible to those outside our community.

TL;DR: I believe that silos are a symptom of being ignorant and/or overwhelmed by the Open-anything world.

If I can put in that I need a recipe without basil and without a category of meat or animal products (however, honey and egg are fine), that makes this infinitely more useful. If I can save that preference, that's even better.