>Willing to kill.

>Not willing to violate the license of a software package.

Thank you very much! I also feel that the impact of software licensing on violent groups behavior might be low.

It is, however, interesting on principle, since it only allows the use by criminals (implicitly), and not by law enforcement. By then making the tool very impractical to use, we can punish bad actors still.

(I think there was a honeypot operation to this effect, something with feds making up a "secure encrypted phone" and then acquiring Cartels as a major customer.)

(On the off chance I just burned this very similar operation: dear feds, I'm so sorry!)

> I think there was a honeypot operation to this effect

I think that's the Anom phones - https://en.wikipedia.org/wiki/Operation_Trojan_Shield

Did you really say that only criminals are permitted to use Reticulum?

So presumably, by the extension of your argument, average person using Reticulum is either ("implicitly") a criminal or breaking the licence / ToS.

Where do you see it?

The comment that started this thread is as follows:

> Too bad the Zen of Reticulum is against freedom. Specifically freedom 0: the freedom to use the software for any purpose. Its restrictions preventing it "from being used in systems designed to harm humans" [...]

So if you're a lawful good human-harming person, you are prohibited from using Reticulum by this Zen document.

If, however, you're an unlawful kind of human-harming person, then you likely don't feel the pressure from the Zen document to stop using Reticulum.

(And surely you can't flip the logic like you did right there: "engineers are implicitly allowed to use X" doesn't convert to "users of X are implicitly engineers".)

So no, I'm saying that of all users intending to cause humans harm with this tech, only criminals are permitted (or at least, aren't meaningfully restricted) to use Reticulum. Only in this niche case.

Any reason you didn't use alpine for client side interactivity? When I went down the "use a framework plugin in Astro" route, I found it too jarring and reverted to alpine which I found worked well enough.

No, not in particular, I just like Svelte's compilation-based approach, but Alpine definitely looks nice.

When the client side interactivity is very contained and small in scope I also quite like just using plain JavaScript without a framework.

Sorry we haven't fixed this issue sooner. In this case it's a complicated CSS issue, but nevertheless I've got a fix I'm working on here:

https://github.com/withastro/astro/pull/15227

Wow! That's a pretty impressive turnaround time from my comment to a PR, thanks for your work. I'll be happy to include this in my projects.

I have a preview release ready, if you scroll down you'll see the instructions. If you're able to try it out and leave a comment on whether it fixes your issue it'd be a big help.

Wow. Good callout.

blogslop

Zero discussion of the 3:1 premium limit in the ACA. The ACA mandates that you can only charge older people 3x the premium you charge younger people. Older people account for an extremely outsized portion of healthcare services received. This means that no matter how little healthcare you need as a healthy young person, you have to pay 33% of the estimated cost of care for someone who is end-of-life and possibly consuming hundreds of thousands of dollars (or more) worth of medical care.

Looks very promising. Do you have a vision for how we should build p2p apps more generally? I have recently found the holepunch libraries / pear runtime and am curious if you have any thoughts on those projects or how hypercore(?) compares to genosDB.

GenosDB vs Holepunch

GenosDB is a distributed graph database built for the modern web—runs entirely in the browser, uses OPFS for storage, WebAuthn for authentication, and offers a minified production-ready P2P client. The client is the source of truth.

Holepunch, on the other hand, is a decentralized app platform built on the Hypercore Protocol—great for building custom peer-to-peer apps like Keet, but it doesn’t include a database layer or client-side persistence by default.

Feature GenosDB Holepunch Type Distributed graph DB Decentralized app platform Storage Browser (OPFS, IndexedDB) App-defined (Hypercore, etc.) Auth WebAuthn + RBAC Not included P2P Sync WebRTC (via Trystero) DHT + Hypercore Codebase Minified client lib (genosdb) Fully open (various repos) Use Case Structured data & relationships Custom P2P protocols & messaging

GenosDB is ideal if you need a client-side graph DB with real-time P2P sync. Holepunch is great for building from scratch with total flexibility, but higher complexity.

More at: https://genosdb.com | https://holepunch.to

I'll send you the complete documentation, it's super easy to create applications with artificial intelligence, simply by pasting the official documentation to any assistant and asking it to build it for you and, as if by magic, you'll have it working thanks to the fact that GenosDB is loaded integrated from the CDN. https://github.com/estebanrfp/gdb/wiki/GDB-API-Reference And here's a post from the author on how to build a distributed todolist app in real time.https://genosdb.com/build-a-to-do-list-in-minutes-with-genos...