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).
It wasn’t the start of a corruption story about Trump, but the cover-up of a still-unresolved Hillary Clinton scandal. This is purely a Clinton corruption story, probably the last in a long line, as neither Bill nor Hillary will have careers when it’s finished, if they stay out of jail. Characteristically, the most powerful political family since the Kennedys won’t just bring many individuals down with them, but whole institutions, as the FBI, the CIA, the presidency of Barack Obama, and a dozen or so of the most celebrated brands in commercial media will see their names blackened forever through association with this idiotic caper. A fair number of those media companies should (and likely will) go out of business.
Now, we know. With the help of the declassified Durham material, we can explain the whole affair in three brushstrokes.
One, Hillary Clinton and her team apparently hoped to deflect from her email scandal and other problems via a campaign tying Trump to Putin. Two, American security services learned of these plans. Three — and this is the most important part — instead of outing them, authorities used state resources to massively expand and amplify her scheme. The last stage required the enthusiastic cooperation and canine incuriosity of the entire commercial news business, which cheered as conspirators made an enforcement target of Trump, actually an irrelevant bystander.
I’ve tiptoed for years around what I believed to be true about this case, worrying some mitigating fact might emerge.
Now, there’s no doubt.
Hillary Clinton got in a jam, and the FBI, CIA, and the Obama White House got her out of it by setting Trump up. That’s it. It was a cover-up, plain and simple...
No Doubt Left: Russiagate Was a Cover-Up
The most infuriatingly complex scandal of all time has just been reduced to a page or two, thanks to another declassified release
Sorry, could not find a profile with the publicKey "b81776c32d7b828a7a008629b59006320778c3d52c65da5ea562a2c54ef76c2a".
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.
could not start Lit: received critical error from subsystem, shutting down: RPC middleware receive failed: rpc error: code = Unavailable desc = error reading from server: EOF
Hide Detail
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.
Network Overview UpdateThank you for the additional context—this helps clarify the setup significantly. The TP-Link Archer C9 is operating in access point (AP) mode, providing Wi-Fi connectivity with a distinct BSSID (likely tied to a legacy SSID or configuration algorithm), allowing older devices to connect without reconfiguration. Even though its WAN is unplugged (as shown in the screenshot), it's still active for local wireless clients, explaining the detected 12 wired and 1 wireless device. This avoids disrupting legacy hardware that hasn't adapted to newer BSSIDs from the FRITZ!Box or ASUS.The FRITZ!Box 7560 at 192.168.1.249 is indeed the primary gateway, with its non-standard IP (typically .1) resulting from your historical practice of assigning high IPs to routers (starting from .254 and decrementing over time). This makes sense for continuity, especially as older gateways phase out. The pfSense instance at .252 seems to be handling specific services like DHCP and DNS (based on its active leases and Unbound resolver), while the FRITZ!Box manages internet access (via LAN1 as WAN to 2degrees fiber or similar, with DSL disabled) and telephony/NAS. No double-NAT or conflicts are apparent, but the lack of redundancy is a vulnerability, particularly with 2degrees' reported inconsistencies (e.g., outages or speed variability, as you've noted).The ASUS ZenWiFi acts as a mesh extender, and Pi-hole provides ad-blocking. Overall, the LAN remains on 192.168.1.0/24, with ~50-60 devices cataloged (including transients). If the Starlink terminal is powered up, it could serve as a strong failover option—Starlink provides high-speed satellite internet (typically 50-200 Mbps down in NZ), independent of terrestrial lines.
Tom Schmidt (09:20):
Your take? Yeah, I did Brad Sherman, who's normally extremely lame and curmudgeonly. I was going on a little tirade about this, about there being no yield, which I was like, I mean, I think his angle was more just trying to stop the bill, which obviously didn't happen, but it is kind of a bummer that was left out. But you're right that hey, people have these rep share agreements, yield will eventually get passed down to staple coin holders. But ultimately, I mean this feels like kind of the template of what the crypto industry has been asking for. Just very clean, very straightforward, clear, bright lines about what is even required of companies and also not overly constraining in the sense that, yeah, there's still room for innovation and it doesn't stop new competitors from popping up. So overall, I think pretty exciting and just kind of hard to believe you've been waiting for this for so many years.
Nice, that build step passing with poetry install means the Dockerfile tweak worked—secp256k1 and deps are in, and it's rolling toward completion in 21.8 seconds, which is solid for a redeploy. Outline: Just let it finish deploying, check status/logs, then hit the admin UI to wrap up.From here: Let fly deploy -a lnbits-legend --wait-timeout 600 run its course—should wrap in a few minutes with migrations/extensions.Check status: fly status -a lnbits-legend for healthy VMs.Tail logs: fly logs -a lnbits-legend to spot any late errors or version bumps (expect v1.2.1 or newer).Once up, log in as superuser (your old ID or grep logs if changed), go to Manage Extensions > Update All, test the site. Should be smooth sailing now.<grok:render type="render_inline_citation"></grok:render>