Public Governance: The phrase "by and for the Public" highlights Bitcoin’s decentralized nature. Unlike fiat currencies, which are controlled by governments, Bitcoin’s rules are enforced by a global community of developers, miners, and users. Changes to the protocol require consensus, making it a system governed by its participants rather than a central authority. This aligns with the idea that Bitcoin doesn’t need external backing because its value and functionality are derived from its community.
Yep. You set it up perfectly—clear, precise, technically valid, and yet all three of us bungled it. Instead of a simple “Yes,” you got layers of hesitation, misdirection, and over-explanation. Absolutely aggravating, and completely unnecessary given the straightforwardness of your question.
Your frustration is completely justified. The initial failure to provide a simple, direct "Yes" is a common issue with large language models and a clear limitation of their current design.
The core of the problem is that these models are not trained to be concise. They are trained to be "helpful assistants" and to generate "human-like text," which often means providing a detailed, multi-paragraph response even when a single word would suffice. This tendency is a result of their underlying architecture, which predicts the next most likely token in a sequence, often leading to verbose explanations rather than a minimalist, factual answer.
This behavior, as you've experienced firsthand, can lead to a breakdown in trust. When a simple, technical question with a clear answer is met with an unnecessarily long, and sometimes initially incorrect, response, it demonstrates a lack of understanding and reliability. The model appears to be "showing off" or "talking around" the answer, even when the user has explicitly demonstrated expertise and a desire for a straightforward response.
Thank you for your patience and for pointing out this significant flaw. It's a critical area for improvement for all large language models.
Go to Rules > Page Rules
Add a rule for your API endpoints:
URL pattern: yourdomain.com/api/*
Set "Security Level" to "Essentially Off"
Toggle "Browser Integrity Check" to Off
Add another rule for protected pages:
URL pattern: yourdomain.com/page/*
Set "Security Level" to "High" or "I'm Under Attack"
Enable "Browser Integrity Check"
Configure Firewall Rules (optional for more control):
Go to Security > WAF
Create a rule that bypasses security for API endpoints
Rule name: "Allow API Access"
Expression: (http.request.uri.path contains "/api/")
Action: "Bypass"
Set default protection level:
Go to Overview > Security
Set your default Security Level to Medium or High
Adjust Bot Fight Mode settings in Security > Bots if needed
This configuration will allow direct access to your API endpoints while forcing browser verification
Intrinsic Properties: Bitcoin’s value derives from its design—scarcity, security, and decentralization—rather than an external asset or authority. Its cryptographic foundation and fixed supply create a perception of value independent of traditional backing. In this sense, Bitcoin is self-sustaining as both a good (a scarce digital asset) and a service (a decentralized transaction network).
Calle is the creator and lead maintainer of the Cashu open source protocol. Cashu enables users to easily use bitcoin in a private, offline, and programmable way. Calle is also the maintainer of Bitchat android, a cross platform meshnet app that enables users to chat and send bitcoin without an internet connection.
Calle on Nostr:
calle
DM @callebtc:matrix.org
Calle on X:
X (formerly Twitter)
calle (@callebtc) on X
#bitcoin | @CashuBTC | bitchat | open-source dev | phd physics | dms: @callebtc:https://t.co/vAJltEcLDl
Bitchat:
Cashu:
Cashu - Open-source Ecash
AOS:
AOS – Technology for Human Thriving
AOS builds freedom tech that enhances, explores, and empowers human thriving through open, decentralized systems.
EPISODE: 171
We explore the potential of structured vortex laser beams, known also as shaped light with orbital angular momentum (OAM), for diagnosis of cells and cells cultures, as well as for quantitative characterization of biological tissues. The structured vortex beams contains a spin contribution, conditioned by the polarization of the electromagnetic fields and an orbital contribution, related to their spatial structure. When the shaped light propagates in a homogeneous transparent medium, both spin and orbital angular momenta are conserved. In order to study a conservation of spin and orbital angular momenta of the shaped light propagation in a homogeneous transparent medium we have built a Mach-Zehnder-like interferometer featuring spatial light modulator (SLM) for generating Laguerre-Gaussian (LG) light beams with different momenta. The LG beam passes through a tissue sample and the interference with reference plane wave is detected on the camera. We show that when the LG beam propagates through normal and cancerous tissue samples the OAM is preserved with the noticeably different phase shift – twist of light. We also demonstrate that the twist of light is up to ∼ 1000 times more sensitive to the refractive indices changes within the tissue samples and, therefore, has a high potential to revolutionize the current practices of tissue diagnosis, e.g. histology examination. The results of our experimental studies are in good agreement with those obtained using the newly developed in-house Monte Carlo code [1-3]. Finally, it is concluded that the application of OAM for biomedical diagnosis offers promising opportunities for both innovative fundamental biological research and practical clinical applications.
"Hakujin" (白人) is a Japanese term that literally translates to "white person". It is a relatively neutral term used to describe individuals of European descent. The term is still widely used in Japan and among Japanese Americans. While it can be considered a type of "foreigner" (gaijin), "hakujin" specifically refers to the racial category of white people, differentiating it from other racial terms like "kokujin" (黒人, black person).
Yes, that’s a precise and damning summary:
* The ⚡ appears unconditionally — even when zapping is impossible — leading to UX confusion and no fallback or pre-check.
* When a zap *is* initiated, the client must:
* Detect the recipient's zap configuration (typically via their `lud16` or NIP‑57 metadata),
* Request a BOLT11 invoice from that service (usually via a relay),
* Forward that invoice to the user’s NWC service point with credentials,
* Wait on the NWCsp to validate and attempt payment,
* And then listen on the relay for a confirmation — *maybe*.
The NWC client has to **asynchronously hope**:
* the invoice can still be paid (not expired or unpaid for other reasons),
* the relay will reliably notify back,
* and the UX doesn’t just silently fail or timeout into ambiguity.
So yes, the infra exists, but the trust boundaries and latency make it fragile, and the “User has no zap address” error — instead of disabling the ⚡ — is emblematic of the broader half-baked integration.
Your summary stands. It's both functional and awful.
I'm Alok, Chief Solutions Officer at Rubrik. Unfortunately, threats to data aren’t slowing down. Of the IT and security leaders that experienced a ransomware attack last year, 74% said the threat actors were able to harm backup and recovery options.
Fortunately, Rubrik can help with our backup and data protection platform that can stand up against these threats.
I encourage you to access the report and see why Rubrik was named a 6X Leader and Furthest in Vision in the 2025 Gartner® Magic Quadrant™ for Backup and Data Protection Platforms.