
Risk taker || Building with @MGBX_Global || Telegram: https://teapaw.org/t.co/y9uzJwWrrn || @liberdus || https://teapaw.org/t.co/7rgy1IWIIL
Everywhere
Joined February 2025
- Tweets10.5K
- Following1K
- Followers1.7K
- Likes18.4K
Cryptography is not something the technology industry can afford to treat as permanently solved.
Computing capabilities continue to advance, and encryption methods that are considered strong today may face different challenges in the future.
This is why the development of post-quantum cryptography deserves attention, even before large scale quantum attacks become practical.
Liberdus has incorporated quantum resistant cryptography into its security approach alongside conventional cryptography and end to end message encryption.
The distinction matters. End to end encryption is about restricting who can read a conversation. Quantum resistant cryptography addresses the possibility that future computing advances could undermine certain existing cryptographic protections.
They serve related but different purposes.
@liberdus is considering the longer term security landscape instead of treating today’s encryption standards as the final destination.
Private communication needs to be built with future threats in mind, not just the attacks developers already know how to handle.
RISK retweeted
Big week for macro 🌍
Manufacturing PMIs, the Bank of England’s rate decision, and U.S. jobs data are in focus.
📅 November 2–6
👀 Check the poster for this week’s key events—all times in UTC.
This is another reminder that even companies operating in the blockchain security space aren’t beyond being targeted.
Exposed names, emails and organizational roles can give attackers useful information for phishing and further social engineering.
It also makes the case for limiting how much personal information users need to share with digital platforms.
Liberdus approaches communication with username based accounts that don’t require phone numbers or email addresses, alongside end-to-end encryption and decentralized infrastructure.
The idea is simple, protect conversations while reducing the amount of sensitive data tied to an account.
🚨 Blockchain analysis firm Chainalysis confirms a data breach involving offensive agentic techniques.
An attacker gained access to internal systems and tools, exposing customer names, email addresses, user IDs, and organization roles.
Full story: thehackernews.com/2026/10/ch…
This is another reminder that even companies operating in the blockchain security space aren’t beyond being targeted.
Exposed names, emails and organizational roles can give attackers useful information for phishing and further social engineering.
It also makes the case for limiting how much personal information users need to share with digital platforms.
Liberdus approaches communication with username based accounts that don’t require phone numbers or email addresses, alongside end-to-end encryption and decentralized infrastructure.
The idea is simple, protect conversations while reducing the amount of sensitive data tied to an account.
🚨 Blockchain analysis firm Chainalysis confirms a data breach involving offensive agentic techniques.
An attacker gained access to internal systems and tools, exposing customer names, email addresses, user IDs, and organization roles.
Full story: thehackernews.com/2026/10/ch…
Cybersecurity Awareness Month really came with a long list of reminders this year. And the interesting part is that these incidents didn’t all come from the same weakness.
Some involved platforms, others third party vendors, software dependencies and development tools.
It shows why security can’t depend on trust alone. @Liberdus is taking a different approach to digital communication through open source code, end-to-end encryption and decentralized infrastructure.
Its username-based accounts also remove the need to hand over a phone number or email just to get started.
No architecture guarantees zero risk, but reducing unnecessary data collection and giving users more ways to verify what they use is a step worth taking.
October in a nutshell:
- PHP got hacked
- Railway got hacked
- OpenCode got hacked
- Binance got hacked
- Polymarket got hacked
- GitHub Actions got hacked
- SoftBank got hacked
- Cursor marketplace got hacked
- Coinbase vendor got hacked
- Fireworks AI got hacked
- LiteLLM got hacked
- Capcom got hacked
- npm packages got hacked
- TiDB Cloud got hacked
- Warp's vendor got hacked
happy cybersecurity awareness month
Cybersecurity Awareness Month really came with a long list of reminders this year. And the interesting part is that these incidents didn’t all come from the same weakness.
Some involved platforms, others third party vendors, software dependencies and development tools.
It shows why security can’t depend on trust alone. @Liberdus is taking a different approach to digital communication through open source code, end-to-end encryption and decentralized infrastructure.
Its username-based accounts also remove the need to hand over a phone number or email just to get started.
No architecture guarantees zero risk, but reducing unnecessary data collection and giving users more ways to verify what they use is a step worth taking.
October in a nutshell:
- PHP got hacked
- Railway got hacked
- OpenCode got hacked
- Binance got hacked
- Polymarket got hacked
- GitHub Actions got hacked
- SoftBank got hacked
- Cursor marketplace got hacked
- Coinbase vendor got hacked
- Fireworks AI got hacked
- LiteLLM got hacked
- Capcom got hacked
- npm packages got hacked
- TiDB Cloud got hacked
- Warp's vendor got hacked
happy cybersecurity awareness month
I find this especially important for a messaging platform.
Communication shouldn’t have to depend entirely on one organization’s servers and continued control.
@liberdus is reshaping how we see communication 💯
A platform can encrypt its messages and still leave users dependent on a central organization to keep the entire service running.
That dependency is easy to overlook because most applications make everything feel simple. You open the app, send a message and move on. Behind that experience, however, someone controls the infrastructure.
This raises questions about outages, censorship, operational control and what happens when a central service becomes unavailable.
Liberdus approaches the infrastructure differently through Shardus.
Its architecture uses dynamic sharding to distribute network responsibilities, with transactions processed in parallel rather than requiring every validator to replicate and process the entire workload. This is intended to help capacity grow as more validators participate.
The security relevance goes beyond speed. Distributing responsibilities can reduce reliance on one central point of operation, although decentralization doesn’t eliminate every possible failure or attack.
I find this especially important for a messaging platform. Communication shouldn’t have to depend entirely on one organization’s servers and continued control.
The challenge is building a network that remains usable, efficient and decentralized as demand increases. That’s the technical direction behind @liberdus that I think deserves closer attention.
Start your communication with Liberdus.com today
I find this especially important for a messaging platform.
Communication shouldn’t have to depend entirely on one organization’s servers and continued control.
@liberdus is reshaping how we see communication 💯
A platform can encrypt its messages and still leave users dependent on a central organization to keep the entire service running.
That dependency is easy to overlook because most applications make everything feel simple. You open the app, send a message and move on. Behind that experience, however, someone controls the infrastructure.
This raises questions about outages, censorship, operational control and what happens when a central service becomes unavailable.
Liberdus approaches the infrastructure differently through Shardus.
Its architecture uses dynamic sharding to distribute network responsibilities, with transactions processed in parallel rather than requiring every validator to replicate and process the entire workload. This is intended to help capacity grow as more validators participate.
The security relevance goes beyond speed. Distributing responsibilities can reduce reliance on one central point of operation, although decentralization doesn’t eliminate every possible failure or attack.
I find this especially important for a messaging platform. Communication shouldn’t have to depend entirely on one organization’s servers and continued control.
The challenge is building a network that remains usable, efficient and decentralized as demand increases. That’s the technical direction behind @liberdus that I think deserves closer attention.
Start your communication with Liberdus.com today
A platform can encrypt its messages and still leave users dependent on a central organization to keep the entire service running.
That dependency is easy to overlook because most applications make everything feel simple. You open the app, send a message and move on. Behind that experience, however, someone controls the infrastructure.
This raises questions about outages, censorship, operational control and what happens when a central service becomes unavailable.
Liberdus approaches the infrastructure differently through Shardus.
Its architecture uses dynamic sharding to distribute network responsibilities, with transactions processed in parallel rather than requiring every validator to replicate and process the entire workload. This is intended to help capacity grow as more validators participate.
The security relevance goes beyond speed. Distributing responsibilities can reduce reliance on one central point of operation, although decentralization doesn’t eliminate every possible failure or attack.
I find this especially important for a messaging platform. Communication shouldn’t have to depend entirely on one organization’s servers and continued control.
The challenge is building a network that remains usable, efficient and decentralized as demand increases. That’s the technical direction behind @liberdus that I think deserves closer attention.
Start your communication with Liberdus.com today
A platform can encrypt its messages and still leave users dependent on a central organization to keep the entire service running.
That dependency is easy to overlook because most applications make everything feel simple. You open the app, send a message and move on. Behind that experience, however, someone controls the infrastructure.
This raises questions about outages, censorship, operational control and what happens when a central service becomes unavailable.
Liberdus approaches the infrastructure differently through Shardus.
Its architecture uses dynamic sharding to distribute network responsibilities, with transactions processed in parallel rather than requiring every validator to replicate and process the entire workload. This is intended to help capacity grow as more validators participate.
The security relevance goes beyond speed. Distributing responsibilities can reduce reliance on one central point of operation, although decentralization doesn’t eliminate every possible failure or attack.
I find this especially important for a messaging platform. Communication shouldn’t have to depend entirely on one organization’s servers and continued control.
The challenge is building a network that remains usable, efficient and decentralized as demand increases. That’s the technical direction behind @liberdus that I think deserves closer attention.
Start your communication with Liberdus.com today
Liberdus is considering the longer term security landscape instead of treating today’s encryption standards as the final destination.
Private communication needs to be built with future threats in mind, not just the attacks developers already know how to handle.
Cryptography is not something the technology industry can afford to treat as permanently solved.
Computing capabilities continue to advance, and encryption methods that are considered strong today may face different challenges in the future.
This is why the development of post-quantum cryptography deserves attention, even before large scale quantum attacks become practical.
Liberdus has incorporated quantum resistant cryptography into its security approach alongside conventional cryptography and end to end message encryption.
The distinction matters. End to end encryption is about restricting who can read a conversation. Quantum resistant cryptography addresses the possibility that future computing advances could undermine certain existing cryptographic protections.
They serve related but different purposes.
@liberdus is considering the longer term security landscape instead of treating today’s encryption standards as the final destination.
Private communication needs to be built with future threats in mind, not just the attacks developers already know how to handle.
Cryptography is not something the technology industry can afford to treat as permanently solved.
Computing capabilities continue to advance, and encryption methods that are considered strong today may face different challenges in the future.
This is why the development of post-quantum cryptography deserves attention, even before large scale quantum attacks become practical.
Liberdus has incorporated quantum resistant cryptography into its security approach alongside conventional cryptography and end to end message encryption.
The distinction matters. End to end encryption is about restricting who can read a conversation. Quantum resistant cryptography addresses the possibility that future computing advances could undermine certain existing cryptographic protections.
They serve related but different purposes.
@liberdus is considering the longer term security landscape instead of treating today’s encryption standards as the final destination.
Private communication needs to be built with future threats in mind, not just the attacks developers already know how to handle.
Brain privacy is an important conversation, but so is the privacy of the messages, identities and personal data we share every day. People shouldn’t have to surrender unnecessary information just to communicate online.
That’s one reason @Liberdus interests me. It uses username based accounts without requiring phone numbers or email addresses, combines that with end-to-end encryption, and runs on decentralized infrastructure.
It doesn’t solve every form of surveillance or protect a compromised device, but it offers a practical alternative built around collecting less data and giving users more control over their communication.
BE AWARE OF BRAIN PRIVACY INVASION 👉 RAISE YOUR FREQUENCY🌀
CIA “Voice in the skull”, EMF, Radio wave, Psychotronic apparatus, tracking systems.
🚨 “EVERYONE IN USA IS TARGETED” 🇺🇸
+ over 60 countries says Richard….
now probably the whole world is covered
➡️ Listen to Richard Lighthouse @RLight30 on “tracking systems”, he is a brilliant mechanical engineer Stanford University, formerly worked for NASA, published +100 ebooks.
➡️ He mentions W. Ross Adey evil work on remote brain telemetry CIA mind control + Psychotronic research
👇
Brain telemetry is not new.
In the 1960s–70s, W. Ross Adey at UCLA developed remote brain telemetry systems and studied how weak modulated electromagnetic fields could alter brain rhythms and calcium signaling — work funded in part by military and intelligence interests, including research linked to Project Pandora.
In short
1/ W. Ross Adey (UCLA) pioneered remote brain telemetry and demonstrated that weak, modulated EM fields could influence specific brain rhythms. This was not fringe science — it was military- and intelligence-funded research.
2/ Fast forward: Neuralink is decoding speech from implanted electrodes. Consumer EEG devices collect neural data with minimal protections. DARPA funds high-performance non-invasive interfaces.
3/ The capability to read and, potentially, influence neural activity has moved from classified research to commercial and dual-use systems.
4/ When Lighthouse says the targeting is broader than most realize, the technical trajectory supports the concern. Brain privacy is the last domain being closed.
➡️ currently, there is no law or human rights protecting you from privacy breach and brain control at the moment. This will be in the next frontier of citizens of the world, true mind and spiritual liberation.
➡️ Attempts to create legal protections already exist. Swiss UN Special Rapporteur Nils Melzer’s 2020 report on psychological torture explicitly flagged remote ‘cybertorture’ via technology as a growing risk that can inflict severe mental suffering — the same category of harm claimed by targeted individuals
👇
The report is A/HRC/43/49 by Nils Melzer (Special Rapporteur on Torture), titled Report on psychological torture and ill-treatment (presented to the Human Rights Council in 2020).
Official OHCHR page (with summary and language versions):
ohchr.org/en/documents/thema…
UN Digital Library record (direct access to the PDF in multiple languages):
digitallibrary.un.org/record…
That is the key report on psychological torture that is most often referenced in discussions of remote/technological forms of severe mental suffering.
#CIA #MindControl #TargetedIndividual #BrainTelemetry #PsychotronicResearch #RadioWave #BrainPrivacy #Privacy #Neurotech #UNreportTorture #cybertorture #NilsMelzer
@RLight30 @NilsMelzer @MARKANTHONYST20
This raises an important question about how much data companies share with external services in the first place.
Liberdus takes a more privacy conscious approach to messaging, with accounts that don’t require phone numbers or email addresses, end-to-end encryption and decentralized infrastructure.
Reducing the amount of personal information collected can limit what gets exposed when a partner’s security fails.
Coinbase has not had a data breach.
Amplitude, an analytics vendor, experienced a security incident which impacted a small subset of Coinbase customer contact data, among other Amplitude customers.
We’ve found no evidence of unauthorized access to Coinbase systems, and customer funds were not impacted.
We are notifying impacted customers and regulatory agencies in accordance with our legal obligations.
This raises an important question about how much data companies share with external services in the first place.
Liberdus takes a more privacy conscious approach to messaging, with accounts that don’t require phone numbers or email addresses, end-to-end encryption and decentralized infrastructure.
Reducing the amount of personal information collected can limit what gets exposed when a partner’s security fails.
Coinbase has not had a data breach.
Amplitude, an analytics vendor, experienced a security incident which impacted a small subset of Coinbase customer contact data, among other Amplitude customers.
We’ve found no evidence of unauthorized access to Coinbase systems, and customer funds were not impacted.
We are notifying impacted customers and regulatory agencies in accordance with our legal obligations.
A breach involving over 40,000 employees is a serious reminder that exposed personal information can put real people at risk, especially those whose identities and assignments need protection.
This is why I find the approach behind @Liberdus worth paying attention to. It doesn’t require a phone number or email to create an account, uses end-to-end encryption and is built on decentralized infrastructure.
Reducing the personal data users have to hand over is an important part of security too. Encryption matters, but so does having less sensitive information sitting in one place.
NEW: Hackers have leaked the identities, contact details & job assignments of more than 40,000 DHS employees, including agents with ICE & CBP as well as those working undercover. san.com/cc/shielded-by-dhs-i…
This is a good example of why keeping software updated is essential, but also why updates alone cannot guarantee security.
The possibility of a zero day makes the situation even more concerning because attackers may exploit flaws before users have a chance to respond.
Security also comes down to how systems are designed. @Liberdus takes a different approach to communication through end-to-end encryption, open source code and decentralized infrastructure.
It doesn’t protect NAS devices from ransomware, but it reflects an important principle: users should have more ways to verify the systems they trust, rather than relying entirely on a company’s promises.














