montyanne

> That’s because the collapse does not necessarily have to come about from people and communities making a more sustainable society through a more equitable use of the commons.

I don’t think anyone’s base case for The End of Capitalism ™ is for humanity to come together and sing kumbaya.

What part of this looks solid??

The first sentence: > Argus is a self-hosted, multi-tenant security operations platform in which AI agents analyze evidence but never act on the estate.

This is just some slopository of meaningless systems.

50 is steep for parking, but between dinner/drinks/rideshare, you can pretty quickly hit $250 on a nice-but-not-crazy date night in my HCOL city.

Only a matter of time that this research became public.

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

Neat article.

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

I appreciate all the hard work the Graphene team has done all these years with advancing alternative mobile OS and have been following them for years so I hope they don’t take this the wrong way -

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.

Based on current events in the US 10y and 30y bonds, the end is coming quicker than people think or are prepared for.

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.

> instead of selecting the next token randomly, the idea will be to select it pseudorandomly, using a cryptographic pseudorandom function, whose key is known only to OpenAI.

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…

> Suddenly we were spending 90% of our time assembling circuit boards instead of growing the business

> 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?

Northeastern graduates assemble!

Refilling the SPR would’ve required finding money to actually buy some oil. Put simply the SPR is broke/in debt.

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)

Tesla drivers generally use the phone key, which generally comes with its own set of privacy concerns.

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

As a tech literate customer, my willingness to entertain AI chatbot decision trees is rock bottom. I have no patience to try to find the correct incantation to actually fix something (or the, “before I transfer you to a person, let me try to help you first”).

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.

I spent an entire month trying to build something with Reticulum, but there just isn’t great tooling for dealing with the protocol. Makes for a pretty infuriating devex if you’re just trying to build your app.

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.