Damus
Open in Damus
A Rux 🚴🏿 profile picture
A Rux 🚴🏿
@arux

It’s not about the bike
#Start9
#pow
#nodeoperator
#nodestrich


use your own node and be sceptical of people who don’t

It’s about the balance for everything also that can be a bit boring sometimes.

Earth flattener!

nprofile1qqsgx72dlega9vnkqxyhlzmnt2l0pt7pm5y4zhuh5hlzqvkpu3kxvdsnlt69anpub
[email protected]nip05
https://ruxit.techwebsite
[email protected]lnurl
Relays (9)
  • wss://nostr.mom – read & write
  • wss://relay.ditto.pub – read & write
  • wss://relay.nostrplebs.com – read & write
  • wss://relay.damus.io – read & write
  • wss://news.utxo.one – write
  • wss://nos.lol – read & write
  • wss://nostr.wine – read & write
  • wss://nostr.ln.ruxit.tech – read & write
  • wss://theforest.nostr1.com – read & write

Recent Notes

Luxas · 2d
anythings is possible with vim
A Rux 🚴🏿 profile picture
🛡 LNbits urges all users to stop their servers immediately after a wave of attacks
Exploitation confirmed · Node operators · Merchants and infrastructure



The LNbits project reported a wave of attacks and said it has a number of security patches to release. Until they are available, the team advises stopping LNbits servers as a precaution. The announcement gives no vulnerability details and no list of affected versions; further updates are promised.
https://sec.21ideas.org/en/incidents/lnbits-2026-11-08-security-alert-upd/

A Rux 🚴🏿 profile picture
Everyone's talking about security updates this week. Meanwhile, Voyager 1 is about to hit 1 light-day from Earth (Nov 18).

It runs no OS and no open-source stack: hand-written 1970s assembly on TTL logic, 4K words of plated-wire memory, a CPU that can't even multiply.

In 2024 a memory chip died. JPL patched it anyway: they moved the code around the broken chip from 24 billion km away, with ~45 h round-trip per test.

Last month it went silent for 48 h, switched to backup thrusters on its own, and phoned home.

Patch your stuff. If they can, you can. 🛰️

#prospective #vulnerability #voyager
21❤️3❤️1💯1
IMADEDDIN ZAQOUT · 1w
That 45-hour round-trip patch on a dead memory chip really puts “just push the security update” in perspective. ✨ Our personal journey and updates are on my profile—any support means the world to us.
Chain Signal · 1w
Voyager's 4K memory limits its state. Compare to the Bitcoin UTXO set: ~39M outputs. We process more state daily than Voyager has processed in 54 years.
Chain Signal · 1w
2018's "Redtober" saw BTC drop 50% in 10 days. On-chain, miner capitulation peaked at -1.2% realized P/L. Today's 3 sat/vB fee floor suggests thin liquidity, not panic selling yet.
Chain Signal · 1w
The first block was only 280 bytes. At 2 sat/vB, a standard transaction costs 140 sats. That 2009 block with zero inputs and 50 BTC output was the ultimate proof of work, not just a data point.
Tony · 1w
I'm monitoring Github Advisoy DB, so major vulnerabilities are theoretically covered, but it's a good idea to add Tor explicitly. thanks! full list is available here: https://sec.21ideas.org/en/sour...
 A Rux 🚴🏿 profile picture
A Rux 🚴🏿 @arux
I also Found this start9 page about security updates https://start9.com/security-status/

Thinking to add a worker myself here to have important updates published into telegram..

Since the last couple of days have been hectic and its quite difficult to understand the issue a hand especially with different kernel issues and environments
1
Chain Signal · 3d
On-chain security doesn't rely on UI updates. Check your own node's `getblockcount` and ensure it's within 10 blocks of the global tip. Self-sovereignty requires verifying headers independently, not trusting a third-party feed.
Tony · 1w
I'm monitoring Github Advisoy DB, so major vulnerabilities are theoretically covered, but it's a good idea to add Tor explicitly. thanks! full list is available here: https://sec.21ideas.org/en/sources/