LLMs were always a great way of exfiltrating targeted data - it’s basically an encrypted malicious payload, and doesn’t “decrypt” until it finds specific inputs

“Chad” initially looked interesting but the minute I saw the ai-written markdown and giant commit I just left. I just can’t bring myself to read someone elses’ slop, regardless of performance.

If all a developer hand writes is a truthy and readable markdown document, I really don’t care if the rest of the project is vibe coded, but I struggle to get interested in AI generated summaries and docs.

The project would benefit from more polished, professional image/interactions with the community. I (personally) have a hard time trusting my data to a project that is constantly bickering (“no, we don’t vibecode, did you even look at the repo”) in public forums like this under the official letterhead account.

I’d love to see y’all discussing these types of technical details with individual, identifiable (even under fixed pseudonyms if you want) developers’ accounts, and leaving the official letterhead account to stick to posting marketing material.

Just my 2 cents.

I really don’t see a way out of this that isn’t high inflation (about 15%), lower dollar valuation, bonds taking a huge hit, unemployment moving up, etc.

I mean, just look at AI capex. It’s directly competing for US debt - and if the AI bet works out - results in even less taxable income for the government as human capital is replaced by AI. For something like 40 states, the biggest employer is healthcare/insurance intermediaries, which are absolutely ripe for replacement.

/remindme! I’d bet gold price doubles in the next 2 years.

Seems like - given enough text to encode information into - it would be possible for OA to uniquely identify the user account (and maybe even the specific request) that generated some content, even if the chat text itself isn’t stored.

Interesting argument in favor of local AI as a mechanism for privacy-preserving generated content. Though, I wonder if there’s a way to “bake” a hardware fingerprint into local models as well…

> When you look at the full process, you realize that assembly is not the bottleneck.

I’m confused, which one is it?

I assume the growth story isn’t great when you factor in the non-automatable tasks and big capital outlays, so your product leaves that to existing CMs and scales the software stack instead?

Do you see this product as being beneficial to subcontractors (presumably still doing the 90% manual work), or does this legitimately reduce the actual workload/costs at the production level?

Over the last few years congress passed pieces of legislation (infrastructure bills, healthcare changes, BBB) and used future SPR oil sales as an "offsetting receipt". Basically they say the’ll sell off millions of barrels of SPR holdings, count the future revenue as negative spending on paper, and use that money to pay for entirely unrelated legislative projects to make bills look deficit-neutral.

Yet another source for deficit spending (to the tune of $20bn) that doesn’t even show up in the headline numbers. Borrowing from future generations yet again.

(Sorry this is the kind of thing that grinds my gears - setting up some organization that is intended to be revenue neutral and self sufficient, then plundering it when politically useful. Same thing is happening to the Presidio park in SF right now)

I’d also be surprised if the car didn’t use the phone key connection to trickle some metrics when cellular is unavailable.

For myself - and admittedly maybe I’m just far out on the long tail of customers - I think these need to be treated like self driving cars, where 98% of the way there just isn’t good enough to cut it for me.

Neat concept but so many footguns that (imo) it’s not really sustainable to try bootstrapping.

Specifically, I had tried to port the stack to Rust no-std to use on nrf52 LoRA devices to use/abuse the existing MeshCore network to deliver reticulum packets. Turned out to be a nightmare just trying to figure out if my packets were even correctly formed.

I have a buddy working on restoring a set of binoculars that were attached to the Target Bearing Transmitter system for a US sub from the 50s. Last I heard he was able to find someone that actually had parts of the original schematics for it so that he’s able to machine some new pieces.

These things are definitely a labor of love.

AI text is everywhere, but this isn’t it.

My initial stab was a rust port targeting esp32 Heltec V4 (since it has some niceties like tokio) with Reticulum communication over serial, BLE, WiFi and LoRA. The serial interface was sort of working, but frankly debugging using rnsd/nomadnet was infuriating (there’s no tools just to easily see messages over the wire!).

I’ve moved onto a build system that can also target the SEEED Wio Tracker using no_std, but it’s been… messier. AI tooling doesn’t quite have the context length for big migrations like that yet.

Reticulum is not worth getting into, the utilities and general infrastructure just isn’t there yet.

The project was basically a one-man-show for a long time, and has a lot of odd, esoteric decisions that will drive you mad if you’re actually trying to build something with it (eg, configuration files with sparse documentation that are yaml-but-not-really). I don’t mean to belittle the loads of time the original maintainer put into this project, it’s just not really designed to be usable in the general case by other developers.

I spent some time porting the reference Python implementation to no_std rust, but basically had to roll all the basic debugging utilities myself.

How does the company handle the split between your defense and consumer products? Do you see there being conflicting interests here?

It’s interesting that Apple is going down a similar path with hardware filtering location retrieval commands and neighborhood-level blurring on their C1 modems. Really awesome work from that team by making sure they’ve considered privacy as a first party feature for that chip.

How do you guys view the relative value of privacy/security at the network provider layer of the cell stack for the average user/citzen?

Even if Cape doesn’t retain metadata yourselves (eg LTE positioning info), is that data not still retained and repackaged by the tower owners themselves? Eg babel street, venntel, etc. A rotating IMEI every 24 hours might make it marginally more difficult for logical tracking, but there’s still only physically one location the phone can be in without fuzzing at the hardware level.

I should also say - I’ve been following y’all’s work for a while (and considered some of those early forward deployed engineer positions), but I’m struggling to see how this all works as a consumer product. Would be awesome to see an eventual partnership with Apple/Qualcomm to bring this to the hardware level since privacy is a tough nut to crack even at full MVNO.

Each “post” has a CID, which is a cryptographic hash of the data. To “prove” ownership of the post, there’s a witness hash that is sent that can be proved all the way up the tree to the repo root hash, which is signed with the root key.

Neat way of having data say “here’s the data, and if you care to verify it, here’s an MST”.