I honestly don't quite understand what your offering is about. I have an RTSP (TLS) camera, which streams to my phone. That's end to end encrypted, what am I missing?
1) Usage model: RTSP cameras can be used for on-demand livestreaming. In contrast, the usage model of our camera is similar to a Ring camera: not only does it support livestreaming, but also it detects events (motion, person, pet, etc.), records a video clip, and sends it to the phone.
2) Connection and ease of use: with an RTSP camera, the camera acts as a sever. You can easily connect to it from your phone if your phone is connected to the same LAN. But if you're outside (which is very typical in the case of home security camera), you will need to connect to your LAN from outside. You have several options to achieve this (port forwarding, VPN, reverse proxy, etc.). Some of these options are not very secure. And they all require some non-trivial setup. In contrast, with our camera (again, similar to a Ring camera), the camera sends the videos to a cloud server and the app downloads them. Therefore, there's no need for the phone to access the LAN. (But note that in contrast to Ring, the videos in Secluso are always end-to-end encrypted. Ring supports an optional end-to-end encrypted mode, but you will lose advanced AI features such as person detection if you enable that since that is performed in their servers.) With the cloud-based video relay, we can then make it very easy to set up and use our camera. More specifically, our plug-and-play camera (https://secluso.com) is very easy to use: scan a QR code, pair, and you're good to go.
3) Encryption: Secluso uses MLS, which provides advanced end-to-end encryption features such as forward secrecy (per message) and post-compromise security.
4) Trust in firmware: Our goal with our recent Raspberry Pi camera is to provide a home security camera with a fully open source firmware. In fact, we now support a reproducible build, which allows you to verify that the firmware binary is built from the open source software in our github repo. This is in contrast to IP cameras that come with closed source firmware, making it difficult to assess their trustworthiness.
Hey, please get signal to release all the infrastructure automation code so someone could audit all of signal's infra and even fork if we ever needed to because of U.S. laws or so on.
There's no reason to keep it secret and no reason why signal won't speak to this point.
The signal org does some sketchy things. Like for example, why won't they release all of their infra automation backend code. There's no reason this and all the other tiny bits should be kept a secret!
This is neat work. I noticed on your software page some patches you had to make to get those things to compile. Have you sent those upstream? Eg, I noticed a simple 1 line bash change for example.
Honestly, I have serious FOMO about this. I am never going to run a Mac (or worse: Windows) I'm 100% on Linux, but I seriously hate it that I can't reliably work at a coffee shop for five hours. Not even doing that much other than some music, coding, and a few compiles of golang code.
My Apple friends get 12+ hrs of battery life. I really wish Lenovo+Fedora or whoever would get together and make that possible.
Here's my variation; I can't stand the ergonomics of Apple computers. The screen doesn't tilt back far enough, they're heavy and slippery, and the only thing I could switch to from a Trackpoint is mind control.
I'm a Linux guy too, when I have to use a Mac I turn all the gloss off and it's ok, but without going to Nix I miss a system wide package manager and I like an open-as-possible community OS that runs everywhere. It's a shame Apple doesn't license their chips.
About a year ago I got a maxed out Macbook Pro, but the above combined with the fact I wasn't comfortable travelling with something that cost as much as a good used car made me return it.
Now I'm using a Thinkpad that was ¼ the price and it's great, AMD chip, 64GB of RAM, replaceable storage, fantastic screen, keyboard (and Trackpoint) means it can do just about anything. Yes, battery life is limited, around four hours with the 16" OLED (I haven't put any work into optimizing it, and this isn't a battery-first model), but I can handle it. I'll maybe get a Strix Halo laptop since I like running LLMs, but otherwise x86 has improved enough that it's pretty good. That said, I won't complain if it matches/surpasses Apple chips, and I'd consider running a headless Apple 'server' at home.
I have a 7.5 year old Asus Zenbook UX305CA. It was the perfect laptop for my use case, given I run all heavy stuff on remote servers. 3200x1800 HiDPI screen, 8GB RAM, no fan, rigid aluminium construction (so it feels high quality), and it runs Linux pretty reliably. It used to get at least 6-7 hours of doing actual work, and one night I forgot to hibernate it or plug it in, and it was still running the next morning.
Now, 7.5 years later, the battery is not so healthy any more, and I'm looking around for something similar, and finding nothing. I'm seriously considering just replacing the battery. I'll be stuck with only 8GB RAM and an ancient CPU, but it still looks like the best option.
Another useful thing is that you can buy small portable battery packs that are meant for jump-starting car engines, and they have a 12V output (probably more like 14V), which could quite possibly be piped straight into the DC input of a laptop. My laptop asks for 19V, but it could probably cope with this.
My experience with anything that is not designed to be an office is that it will be uncomfortable in the long run. I can't see myself working for 5 hours in that kind of place.
Also it seems it is quite easily solved with an external battery pack. They may not last 12hours but they should last 4 to 6 hours without a charge in powersaving mode.
> I'm 100% on Linux, but I seriously hate it that I can't reliably work at a coffee shop for five hours. Not even doing that much other than some music, coding, and a few compiles of golang code.
Don't you drink any coffee in the coffee shop? I hope you do. But, still, being there for /five/ hours is excessive.
> I am never going to run a Mac (or worse: Windows) I'm 100% on Linux,
I'm guessing you're well aware, but just in case you're not: Asahi Linux is working extremely well on M1/M2 devices and easily covers your "5 hours of work at a coffee shop" use case.
Despite OP's complaints (which are valid) I run Fedora on my Framework 13 (AMD) and I get 5 hours of work (10 ish Firefox tabs, multiple VS Code instances, terminals and Slack) without issue.
It's not 8-12, and the fans do kick up. The track pad is fine but not as nice as the one on the MacBook. But I prefer to run Linux so the tradeoff is worth it to me.
They’re relatively heavy, take up space and there’s no guarantee there will be an outlet near your table. When connected, the laptop becomes more difficult to move or pack. It’s all doable but also slightly less convenient.
Always found that take fascinating -- are you sitting at a sofa or those inflatable chair-like things in the coffee shop? Are you changing your body's position multiple times, like, significantly so?
At least from my side, if I have to work on a laptop outside, I'll just find a good table, plug it in an outlet and, you know, work on it, with almost no changes of body position.
Not to be dismissive but I genuinely don't understand what's the problem with your laptop being plugged in when working from a coffee shop.
try one of the newer amd or intel (TSMC-made) CPUs. its pretty much the same. keep in mind the battery size too. mbp has a huge and very heavy battery (the mbp is super heavy)
HP has Ubuntu-certified strix halo machines for example.
More like: We‘re announcing to work on a cure in cancer! Isn‘t that aweslme? No, we dont have anything yet. But we started working on it. ETA? When its done. We dont share roadmaps with outsiders.
I've been playing with it, and I've been generally not impressed.
There are both obvious annoying UI bugs (which should be easy to fix unless they vibe coded the whole thing) and the output of the tool isn't very good for anything but the simplest problems.
If the model was really good, I'd love this, but it's not.
Building sovereign systems management with low overhead is an incredibly important goal. For this I salute them for pursuing that path. However their mistake is that it's a hardware problem. It's actually almost entirely a software problem, modulo convincing some hardware vendors to make their ILOM/IPMI implementations not be buggy or suck.
Disclosure, I work in the software automation space.
Our thesis is that it's both a hardware and software problem! Which, as steve said, is why we're doing both. We can look at designs across the whole stack, from chips chosen, FPGA implementations, hubris management and control plane software to accomplish this goal. By doing these together, we can accomplish fundamentally different designs and tighter integration than any one of those multi-company silos can even if they tried to work together.
This article misses the point. The future will be self-hosted (or local community hosted) when automation technology actually matures and shows some real innovations.
reply