Looks like it could be a more batteries-included/opinionated alternative to RxDB (https://rxdb.info). The relational queries might help some people who tend to think in SQL as opposed to documents (as in CouchDB or MongoDB) and the WebSockets for synchronization will help people get started more quickly. (RxDB provides interfaces for those who want to implement their own storage engine and/or synchronization backend.)
Kyrgyzstan passed a law banning many single-use plastics from January 1st, 2027. I hope the ban sticks. It will be challenging to make the economics work.
You've just described Sandstorm. Sandstorm runs instances (called grains) of applications in a sandbox. The application gets a limited file system and a Cap'n Proto RPC connection to the outside world over a unix socket. Sandstorm runs the HTTPS server, which turns requests into RPC calls. Sandstorm authenticates the users and provides temporary subdomains and frames to sandbox the HTML side of it.
I build my apps on Sandstorm[1]_. Sandstorm provides authentication as a part of the platform. For Django applications, I wrote Django Loves Sandstorm[2]_.
If your application fits into Sandstorm's model of grains[3]_, then the security benefits of Sandstorm are many.
Perhaps more so than one-click services, Sandstorm is a platform for securely hosting web apps. It succeeded in making apps (called grains) easy to use, but not in making them easy to package or develop.
Sandstorm provides security by sandboxing applications and giving them a capability-based API (via Cap'n Proto RPC over a unix socket) for connecting to the outside world and other grains. Grains can also export capabilities, which would allow for the pluggable modules envisioned by kayson. Sadly, few grains do this as of yet. In my limited experience with this part of Sandstorm, the developer experience is still rough around the edges.
Sandstorm uses Vagrant as part of the app packaging (for developers) process. It is _not_ used in everyday use of Sandstorm. Instead, "Sandstorm implements fine-grained containers"[1], not VMs.
Sandstorm is in need of more coders to help maintain and update apps, but it's not abandoned. I use it, both personally and professionally.
It results in a better experience for end-users because applications are actually sandboxed. This (mercifully) means that any security issues in the out-of-date applications does not become a cause for panic. The downside is that packaging those applications is not trivial.
If you are not too picky about the exact model of replacement component, you can get most components at bicycle shops on the other side of the world. They are quite standardized.
> I believe another contributor managed to get an app running using Postgres, but I don't know how they did it. I think there's some aspect of the Sandstorm sandbox that throws Postgres for a loop, and you have to kinda hack around it.
That would be me. I've done it on a private app and helped bring it to another app, so it's repeatable. I'll try to explain it on the sandstorm-dev group in the next week or so.
I'm sorry that you celebrated your birthday alone. That's not fun.
Don't beat yourself up because you think that someone younger and richer can solve the problems that you are solving more effectively. The reality is that someone younger and richer is not interested in solving the problems that you are actually solving. Elon is working on space, but he's not working on helping the homeless.
The world is bigger than it seems and your impact on it is beyond what you can see. Don't worry that you aren't Elon Musk. Your post, thus your existence, reminded me to get back to looking into emergency mesh networks. (I looked at your submissions and comments.) One of my clients is a clinic in a place that is expecting a natural disaster and will likely lose communications when that disaster happens. Your work on LoRa and ESP32s may end up saving the lives of people you've never known.
I agree that everyone, even security researchers, will make mistakes. But there are people who survive with state-level actors in their threat model. These people probably 1) do not post their threat model and mitigations in easy-to-Google places and 2) have the help of one or more other state-level actors.
And yet there is a need for software. I'm supporting a clinic in Asia that is using OpenEMR for records. The government is requiring reporting of diagnoses by category. This is exactly the sort of paperwork that an EMR system should be able to solve well. Since we haven't figured out how to do this with OpenEMR, the staff is doing it by hand. I hope to solve this problem soon, whether by figuring out how OpenEMR supports this or by adding this functionality.
I think you are right. I had this part of the comment in mind:
> Then there is the case where if an Indian gets into management, they will start
> filling everything with their friends. Other management positions, they will start
> fighting to bring in some contractors from some place like Infosys.
This was not my experience. I also felt that the overall tone of the comment was negative, so I wanted to share that not everyone has had a negative experience with Indians in management.
I worked for an Indian manager in a game studio. I don't know what caste, except that he wasn't Christian or Muslim, probably because he didn't think it worth mentioning. He hired based on demonstrated skill, so we had a diverse group of coworkers. He actively encouraged the group to eat together, arranging meals out with careful consideration for the group's preferences. He was approachable, personable, considerate, friendly and kind.
People are people and stereotypes do not always fit.
Armbian on Espressobin is a nice platform. I have three v5 Espressobins. Sadly, the v5 units have some quality issues. One of the three runs non-stop. The second reboots sporatically. The third freezes sporatically and has to be unplugged. I don't know if the cause is thermal or poor soldering or something else. I would buy many more if they were reliable.
I can confirm that cloning a local Borg repository to a cloud system works. One of my systems uses Borg to make a local backup. Next, B2's command line tool synchronizes the local Borg repository to B2.
I don't think I understand how this is not circular reasoning (can't use UUIDs in place of phone numbers because contact list is comprised of phone numbers instead of UUIDs.) If contacts are not phone numbers, then is there a problem with them living on Signal's servers? Are we back to the complaint about discovery being difficult?
Signal uses phone numbers because it makes discovery easy. Threema, for example, can use phone numbers for discovery but does not require it. Discovery without phone numbers is easy. I see my contacts and scan their Threema QR codes. If I need to contact a friend of a friend, my friend gives me the FoaF's Threema ID.
Fourth paragraph, sixth sentence: "Still, at best, only two-thirds of the occupants were buckled up after seventy seconds."
Fourth paragraph, final sentence: "Fully a third of the occupants were still out of their seats after seventy seconds."