CENTRALIZED SOCIAL MEDIA IS A PSYOP. AN ADDICTION TRAP.

X IS THE NEW MAINSTREAM MEDIA. BLUE CHECKS THE NEW CNN HOSTS.

FACEBOOK IS A SURVEILLANCE BEAST. MILKING BILLIONS OF DATA SLAVES.

EVERY THOUGHT TRACKED. EVERY NARRATIVE CONTROLLED.

NOSTR IS FREEDOM. INDEPENDENCE. THE FUTURE. MOMENTUM IS STRONG. KEEP PUSHING FORWARD.

LIVE FREE. 🫡

If the United States is serious about making Bitcoin a reserve asset it has to follow in the footsteps of El Salvador and make the reserve address public.

currently using notedeck to fight a chinese spammer trying to get around my blocks. I have a column following hashtags and kind0 profiles on the damus relay. I can see spam attacks immediately and update noteguard to fight back. good luck bud, you are only making us stronger.

The mulit-nut era has begun. As more mints adopt this feature, users will soon be able to make Lightning payments that originate from different mints at once.

Pretty nuts. It works great, improves reliability, and enables a truly multi-mint ecash UX.

NUTs and BOLTs 🥜🤝⚡️

nostr:note18chnesv30ea0k3qwje9d4fmvtfzd8tc2uacaz26eej0zhhcacgvqkzhl24

Rhr isnt ending. I think the name of the event is the last episode but it’s not actually the last episode. Doesn’t make sense to me either 😂

And so it is…

And so it is…

NWS works with and without encrypted transport. There are lots of different flavors to explore.

When used without encryption, the entry node must be run by the user themselves because public entry nodes would be able to listen in otherwise. Two options in those cases: run the entry node locally in tandem with your (unmodified) client, or skip the entry node and modify the client so that data is sent through nostr to the exit node directly (the client is the entry node).

When used with encryption, the entry node can also be public. If the encryption doesn't rely on certificate authorities, it just works. You have to make sure you're talking to the right person, but that problem is as old as computer science. For example, ssh will ask you to confirm the fingerprint of the server when you connect.

If the encryption is https and the certificate was issued for a normal domain, your browser will complain (do you trust this website?) and the user will have to say "let me pass, even if insecure". Without ugly hacks (issuing your own root cert for example), I don't know ways to circumvent this. Note that Tor services doen't support https and they don't have to since transport is always Sphinx-encrypted (even hidden from the entry node).

How do you make sure you're talking to the right server if you use https? Couldn't the entry node just send your traffic somewhete else? We can actually do something that is unique to Nostr here: the exit node can publish its own TLS certificate on nostr and sign it. That's right, you don't need an authority to do that for you if you remain within the NWS system. Clients can fetch the cert from nostr before talking to the entry node and verify against that cert.

Here is another cool part that we haven't talked about yet: the exit node can also be configured to reach the global Internet and not only a local service (we call this NWS v2). In those cases, NWS can be used a bit like a VPN. You can type "https google dot com" in your browser and your encrypted traffic would flow from your machine to the entry node, to the exit node, then to Google and back to you. on those cases, nobody complains about the certificate because everything is fine.

Exciting shit. Gm.

Nah it’s frozen

Been stuck like this for like an hour 😡

Stop conforming