Avatar
jimbocoin πŸƒ
6140478c9ae12f1d0b540e7c57806649327a91b040b07f7ba3dedc357cab0da5
The SUPERCYCLE guy.

Agreed. For a full archival node, you’ll probably want at least 2TB. That’s enough to accommodate the current chain data, plus room for an indexing service like Fulcrum, plus room to grow.

If you don’t want all the historical data, you can get away with 10GB like lassdas said.

The squeaky wheel gets replaced

#Bitcoin is for enemies. #Nostr is for ememigos.

You might like websocat. It’s a command line tool that lets you make WebSocket connections, sending standard input to it, and spitting received WebSocket message data back out to standard output.

You can cat a JSON file with a [β€œREQ”] message, then read back the contents, for example. There are command line flags for things like keeping the socket open. https://github.com/vi/websocat

I would check that if you can. The Nostr protocol requires SSL connections for WebSocekts, I believe. There may be a difference in whether clients enforce it.

On Coracle, what are these numbers in semi-circles? Something about relays? #asknostr

Is your WebSocket server serving SSL (wss://)? If not, that could be the difference.

#Nostr client feature request: universe mute-follows toggle.

When browsing Universe, I’m looking for new people to follow. It would help to be able to hide posts from people I’m already following.

#Nostr client feature request: pattern-based, client-side mute .

I want to automatically mute every Nostr post containing a Twitter/X link.

Dear Dairy,

Day 14. The locals have accepted me as one of their own. They suspect nothing.

S U P E R C Y C L E nostr:note1xrj9mx5766k5q7gxfpv3c25j52hlj7ynr8pppxdus923470nvnjq46ky7w