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.

While this submission may be unaware, Ada did make an announcement[1] a few weeks back that they are exploring Rust for critical applications.

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

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

I get around this by using netlify[1]. It's free, one simple TOML file, and has plenty of features that make it worth the extra.

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

`async`/`await` syntax hasn't been implemented. `std::future` will be stabilized in 1.36. It will be a decently long time until it's as "easy to use as it is in JavaScript".

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

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?

I've been trying to learn the world of GIS for a cycling/pedestrian project I've been working on over the last few months. I'm also working with the local Open Data/Open Government groups. As I've gotten to know the communities I've seen this over and over...even in the Open Data groups.

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.

The first thing I searched for was lemon, but I noticed that it differentiated between lemon, lemon juice, lemon zest, etc. If I have a lemon, I have all of the above. I'm sure there is a lot of work to know that lemon zest is derived from a lemon, but that would make this stand out against other similar ideas.

I'm unsure if having a 'vegetarian' option is the best way to go since there are about 40 different forms of vegetarian (I have been one for 15+ years). Maybe a better approach would be the ability to exclude ingredients and groups of ingredients. To me that solves a much bigger problem that I frequently have...I have three ingredients, but don't have the one that is generally required to go along with them (ie, I have olive oil, lemon, and garlic, but am out of basil).

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.

I feel like this website is missing some critical information. Is this a product? a service? Can I buy it? do I build it? What is this other than a remote garage door monitoring tool?

Between the lulzspeak and the over-my-head jargon I'm not completely clear, but is this sms/twitter/email for ham radio? .... Because that's potentially amazing. Beyond what this could do for communication in the situations it suggests I can think of a lot of fun stuff to do with something like that.

I agree that from a quick look it seems much closer to gGlass than Oculus. As much as we give Microsoft crap these days (I run in a *nix crowd), I think this is great for the sake of innovation. I really hope it's not just defensive, because I like the idea of the future happening soon and nothing will bring that on like some healthy competition.

Maybe I'm the only one, but the wiggling "Early Birds" on this page and the "Top Ten Facts" along with the marquee scroll on the homepage made it difficult for me to concentrate on reading.