mwaters

Reading about the Cake Wallet #lightning implementation and back-story. https://blog.cakewallet.com/our-lightning-journey/

LOL @ https://cakewallet.com/ blocking #tor users , meanwhile their https://docs.cakewallet.com/ site is unaffected , #cloudflare of course.

If you want to try a secure messaging protocol based on tried-and-tested mail + gpg. My new #deltachat instance is now up at https://vinculum0.net Powered by Hetzner in Europe. Admin is @mwaters Or install your own instance - https://chatmail.at/doc/relay/index.html

#CBDC will be the next IQ test.

"This rise ensures that consumers can feel confident their money is safe, from the very first penny up to £120,000." Martyn Beauchamp, chief executive of the Financial Services Compensation Scheme (FSCS) https://www.bbc.com/news/articles/c867z63l06vo

If your #NOSTR becomes quiet then check your follow list, a client may have accidentally nuked it.

Does #fiat also cause #Hikikomori ? https://en.wikipedia.org/wiki/Hikikomori https://www.youtube.com/watch?v=_aSLhz00U7s

Digital Euro: The Plot to Enslave A Continent Europe has been quietly planning the rollout of a new CBDC. Terrifyingly, it looks like they're not the only one: global central banks are planning to roll this out everywhere. https://www.youtube.com/watch?v=Xnw5LRVAp0Q #finance #economics #dollarendgame #hyperinflation #federalreserve #banking #macroeconomics #business #investing #peruvianbull

Got a Fevela instance up. http://fevela7vjtbzmlfed45pofwlrkaqrmf66lipqrvdj7b2zcy5ov… https://github.com/dtonon/fevela #selfhosting #nostr #tor #onionservice #toronly

Unbanked https://www.imdb.com/title/tt31329590/ https://yts.mx/movies/unbanked-2025 First comment is by steelrat November 01, 2025 at 04:05 am "The biggest scam in human history" LOL #watching #bitcoin #documentary

Legs as transport , unaffected by Chinese rare earths or Saudi hydrocarbons. #walking #health #fitness #SelfSovereignty

Greetings fellow fascists ! https://kolektiva.social/@pospi/115406214303080180

DEF CON 33 - Stories from a Tor dev - Roger 'arma' Dingledine 10 Oct 2025 What is it actually like to support and balance a global anonymity network, with users ranging from political dissidents to national security analysts? You say it's important to teach law enforcement and governments about privacy and end-to-end encryption, but how do those conversations go in practice? I heard you accidentally got Russia to block all of Azure for a day? Are you ever going to do a Tor talk in China? Wait, who exactly tried to bribe you to leave bugs in Tor to support their criminal schemes? Historically I've tried to downplay some of the excitement from operating the Tor network and teaching the world about Tor, but this year I'm going to try my hand at the "war stories" track. https://www.youtube.com/watch?v=djM70O0SnsY #Tor #TorOnly #OnionServices #DefCon #DefCon33

#walking to the #doctor this afternoon using the same disused railway track as three weeks ago. Trees / leaves look about the same. I love that my default is walking. We just celebrated our thirteenth anniversary of #nocarday @beejay

#primal 2.5.8 crashes for me when I go - Premium, Manage Pro, Media Management. ``` type: crash osVersion: google/panther/panther:16/BP2A.250805.005/2025091000:user/release-keys flags: dev options enabled package: net.primal.android:2627, targetSdk 35 process: net.primal.android processUptime: 57860 + 306 ms installer: org.fdroid.fdroid java.lang.IllegalArgumentException: Key "" was already used. If you are using LazyColumn/Row please make sure you provide a unique key for each item. at A1.a.a(Unknown Source:2) at B1.I.w(Unknown Source:145) at v0.J.a(Unknown Source:29) at n4.u.g(Unknown Source:24) at t0.m.invoke(Unknown Source:877) at B1.N.invoke(Unknown Source:51) at B1.K.measure-3p2s80s(Unknown Source:70) at D1.t.B(Unknown Source:44) at l1.S.f(Unknown Source:0) at D1.y.B(Unknown Source:26) at v0.n.f(Unknown Source:0) at D1.y.B(Unknown Source:26) at l1.S.f(Unknown Source:0) at D1.y.B(Unknown Source:26) at r0.A0.f(Unknown Source:103) at D1.y.B(Unknown Source:26) at r0.v0.f(Unknown Source:32) at D1.y.B(Unknown Source:26) at r0.v0.f(Unknown Source:32) at D1.y.B(Unknown Source:26) at D1.P.invoke(Unknown Source:53) at c1.r.e(Unknown Source:108) at c1.s.a(Unknown Source:55) at c1.t.d(Unknown Source:120) at D1.q0.a(Unknown Source:2) at D1.S.x0(Unknown Source:204) at D1.U.b(Unknown Source:43) at D1.U.m(Unknown Source:109) at D1.U.j(Unknown Source:108) at E1.A.t(Unknown Source:35) at E1.A.dispatchDraw(Unknown Source:14) at android.view.View.draw(View.java:25097) at android.view.View.updateDisplayListIfDirty(View.java:23937) at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:4554) at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:4527) at android.view.View.updateDisplayListIfDirty(View.java:23891) at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:4554) at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:4527) at android.view.View.updateDisplayListIfDirty(View.java:23891) at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:4554) at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:4527) at android.view.View.updateDisplayListIfDirty(View.java:23891) at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:4554) at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:4527) at android.view.View.updateDisplayListIfDirty(View.java:23891) at android.view.ThreadedRenderer.updateViewTreeDisplayList(ThreadedRenderer.java:694) at android.view.ThreadedRenderer.updateRootDisplayList(ThreadedRenderer.java:700) at android.view.ThreadedRenderer.draw(ThreadedRenderer.java:798) at android.view.ViewRootImpl.draw(ViewRootImpl.java:5837) at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:5488) at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:4482) at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:3076) at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:10643) at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1570) at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1579) at android.view.Choreographer.doCallbacks(Choreographer.java:1179) at android.view.Choreographer.doFrame(Choreographer.java:1108) at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1553) at android.os.Handler.handleCallback(Handler.java:995) at android.os.Handler.dispatchMessage(Handler.java:103) at android.os.Looper.loopOnce(Looper.java:248) at android.os.Looper.loop(Looper.java:338) at android.app.ActivityThread.main(ActivityThread.java:9106) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:593) at com.android.internal.os.ExecInit.main(ExecInit.java:50) at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:371) ```

* A former Meta employee sued the company over allegations that its WhatsApp messaging service contained cybersecurity failures that could compromise user privacy. * The former WhatsApp security head claimed he began receiving "negative performance feedback" shortly after his initial disclosure. * A Meta spokesperson disputed Baig's allegations in a statement, and downplayed his role and ranking at the company. An ex-Meta employee sued the social media company on Monday over allegations that its WhatsApp messaging service contained "systemic cybersecurity failures" that potentially compromise user privacy. Attaullah Baig, WhatsApp's former head of security, alleged that Meta retaliated against him after he notified leaders, including CEO Mark Zuckerberg, of security issues at the messaging app. The suit, filed in U.S. District Court for the Northern District of California, claims that after joining WhatsApp in 2021, Baig found security flaws that violated federal securities laws and Meta's legal obligations related to a 2020 privacy settlement with the Federal Trade Commission. During a test conducted with Meta's central security team, Baig alleged he "discovered that approximately 1,500 WhatsApp engineers had unrestricted access to user data, including sensitive personal information" and that the employees "could move or steal such data without detection or audit trail." A Meta spokesperson disputed Baig's allegations in a statement, and downplayed his role and ranking at the company. "Sadly this is a familiar playbook in which a former employee is dismissed for poor performance and then goes public with distorted claims that misrepresent the ongoing hard work of our team," the spokesperson wrote. "Security is an adversarial space, and we pride ourselves in building on our strong record of protecting people's privacy." Baig is being represented by the whistle blower organization Psst.org and the law firm Schonbrun, Seplow, Harris, Hoffman and Zeldes. Although the lawsuit doesn't claim that any user data was compromised, it says that Baig told superiors on multiple occasions that the cybersecurity failures posed a regulatory compliance risk. Some of the alleged security flaws include WhatsApp's failure to maintain a 24-hour security operations center fitting of its size and scale, systems to monitor user data access and a "a comprehensive inventory of systems storing user data, preventing proper protection and regulatory disclosure." Baig's attorneys claim in the suit that there were multiple instances of his superiors criticizing his work, and said that within three days of his initial "cybersecurity disclosure," he began receiving "negative performance feedback." In November, Baig notified the SEC of the alleged "cybersecurity deficiencies and failure to inform investors about material cybersecurity risks," the suit says. A month later, Baig sent Zuckerberg the second of two letters, this time informing the CEO that he "had filed the SEC complaint" and that he was "requesting immediate action to address both the underlying compliance failures and the unlawful retaliation." In January, Baig then filed a complaint with the Occupational Safety and Health Administration, documenting "the systemic retaliation" he claims he received after the security disclosures, according to the lawsuit. Meta said the OSHA complaint was dismissed. The following month, the suit says, Meta fired Baig, citing "poor performance" as part of the company's February round of layoffs affecting 5% of staff. "The timing and circumstances of Mr. Baig's termination establish clear causal connection to his protected activity, occurring in close temporal proximity to his external regulatory filings and representing the culmination of over two years of systemic retaliation for his cybersecurity disclosures and advocacy for compliance with federal law and regulatory orders," the suit says. Baig's lawyers said that he submitted a notice to remove his SEC-related claims to federal court on Monday, and that he has "exhausted his administrative remedies prior to bringing this action." https://www.cnbc.com/2025/09/08/ex-meta-employee-whistleb… #whatsapp #meta #privacy #security

Spending my afternoon #walking to and from the dentist along this disused railway track.

I'm letting Daniel host the #xmpp servers. https://account.conversations.im/domain/

The French banks are criminals. https://www.lemonde.fr/les-decodeurs/article/2025/09/08/a…

I've now gone full circle on messengers. Tried #Session , #DeltaChat , #SimpleX , #Matrix , #Signal and #Threema. Back to #XMPP.