Nostr notes by Awiteb

No, I no longer run it on my phone. No one was actually using it, ...

2026-07-13T12:26:23Z

In reply to nevent1q…t8rj
_________________________

No, I no longer run it on my phone. No one was actually using it, it just consumed power for no reason :). I'll remove it from my relay list soon, once I create an onion service for my relay wss://nostr.4rs.nl.

just saying, it's not peer to peer network

2026-05-13T08:31:15Z

In reply to nevent1q…xmdw
_________________________

just saying, it's not peer to peer network

Not the repos, but the patches and issues are nostr events. For ...

2026-04-25T21:04:29Z

In reply to nevent1q…h6ch
_________________________

Not the repos, but the patches and issues are nostr events. For repos there is GRASP, which use Nostr to check if the push authorized or not, instead of ssh keys in regular git server. So you create a single nostr event called Repository State Announcement, and push your repo to 5 GRASP server, they will not ask you for an account, they will just check that the repo state match the nostr one.

Weirdly, Jumble filters out onion relays by default. Disable it ...

2026-04-20T09:19:24Z

Weirdly, Jumble filters out onion relays by default. Disable it in settings? Nope, it'll still filter them. Why? You haven't enabled 'insecure' connections, which is Jumble's way of saying `wss` and `https` without the secure marker

The video feels longer than 4 minutes, possibly because he speaks ...

2026-04-20T09:09:49Z

In reply to nevent1q…hhud
_________________________

The video feels longer than 4 minutes, possibly because he speaks fast

I like this concept, a hybrid Nostr model where users run onion ...

2026-04-20T07:50:40Z

I like this concept, a hybrid Nostr model where users run onion relays directly on their devices. This approach makes Nostr P2P.

User uptime is the challenge. We still need always-online relays. But local relays on user devices can sync their data when they come online.

Here's a scenario. A Nostr client first tries to send an event to the user's WRITE relays. If these are all offline, the client then tries to send the event to the READ relays of the user's contacts, specifically those contacts who also have the sender in their contact lists. When the user comes back online, their device can fetch pending events from those contact relays. I think these local relays should be WoT relays, not just personal ones.

quoting
naddr1qv…cfsy

You don't need a server. You don't need to pay for hosting. Your Android phone is enough to run a personal Nostr relay, accessible from anywhere, over Tor, for free.

This guide covers:

Installing apps via Zap Store

Setting up Citrine as your relay

Exposing it over Tor with Orbot

Connecting from desktop browsers using Tor + FoxyProxy

Step 1: Get Zap Store

Zap Store is a Nostr-native app store. Apps are published by their creators directly on Nostr, so you can follow the developer, see their other work, and zap them to support development, all without ads or shady monetization.

Discovery can take some getting used to, but there are genuinely useful apps there that you won't find pushed by algorithm or paid placement. If someone you follow builds an app, you can find it on Zap Store and follow their work directly.

Install Zap Store first. We'll use it to install the other apps in this guide.

Step 2: Install and Configure Citrine

Citrine is a Nostr relay that runs locally on your Android phone. It's made by the same developer as Amber (the popular Nostr signer app), which is a good trust signal. Install it from Zap Store (or Play Store).

Once installed, you have a few options for how permissive your relay is:

Option A: Personal relay only

Only store events from your pubkey or events that mention you. Your relay stays small and relevant to you only. Good default for most people.

Option B: Open relay with auto-cleanup

Allow anyone to publish events to your relay, but run automatic cleanup so old events get deleted. You can configure it to never delete your own events while cleaning up everything else.

Option C: No filtering

Accept and keep everything. Generous, but be aware: your relay is open to spam and your storage will fill up over time.

Pick what fits your use case. After configuring, Citrine will start listening on a local port (default: 4869). Note this port number — you'll need it in the next step.

Step 3: Expose Your Relay Over Tor with Orbot

Your relay is running, but it's only accessible locally on your phone. To reach it from other devices and networks, you'll use Orbot to create a Tor hidden service (.onion address).

Install Orbot from Zap Store or Play Store.

Create a hidden service

Open Orbot

Go to settings and find Hidden Services (or "Tor Hidden Services")

Add a new hidden service pointed at the port Citrine is using (e.g. 4869)

Orbot will generate a .onion address. Save this, it's your relay address

Whitelist Citrine in Orbot

In Orbot's app list, enable Tor only for Citrine. This routes Citrine's traffic through Tor but leaves all your other apps unaffected.

Set Orbot as Always-On VPN

Go to Android Settings → Network → VPN, find Orbot, and enable Always-on VPN. This makes Orbot start automatically when your phone boots, keeping your relay reachable without manual intervention.

Do not enable the "Block connections without VPN" / kill switch option. Since only Citrine is whitelisted, enabling it would cut internet access for all your other apps.

Your relay is now live. The .onion address works over mobile data, Wi-Fi, any network, no port forwarding, no static IP needed.

Step 4: Add Your Relay to Your Nostr Clients

Your .onion relay address looks like: ws://youraddress.onion

Add it to your relay list in your Nostr client. Most mobile Nostr apps (Yakihonne, Amethyst, etc.) have built-in Tor support and will connect to .onion relays automatically once you add the address.

Step 5: Connect from Desktop

Most mobile apps work out of the box, but desktop browsers can't resolve .onion addresses natively. Fix this with Tor + FoxyProxy.

Install Tor

You need Tor running locally. Install it however you prefer. On macOS and Linux, Homebrew is the easiest way:
brew install tor
brew services start tor
Homebrew itself can be installed from brew.sh. Once running, Tor listens on localhost:9050 (SOCKS5).

Install FoxyProxy

Install the FoxyProxy extension for Firefox or Chromium-based browsers.

Configure FoxyProxy

Click the FoxyProxy icon → Options

Go to Proxies → Add

Fill in:

Title: Onion Resolver (or anything you like)

Type: SOCKS5

Hostname: 127.0.0.1

Port: 9050

Scroll down to Proxy by Patterns → Add Pattern

Title: onion

Pattern: *.onion

Save

Back in FoxyProxy popup, switch mode to Proxy by Patterns

Now your browser will route only .onion addresses through Tor, leaving all normal traffic unchanged. The goal here is connectivity, not anonymity. You're just making .onion addresses resolvable.

Open your web-based Nostr client (e.g. Yakihonne web, Primal) and add your relay. It will connect.

You're Done

You now have a personal Nostr relay running on your phone, reachable from anywhere in the world. No server, no fees, no central point of failure. Your data lives on your device.

I'm now a Tor relay operator, my relay fingerprint is ...

2026-04-17T22:12:15Z

I'm now a Tor relay operator, my relay fingerprint is `C61B3104A7871EED8CCDA43D6BDC5BA54EC140F4`. #asknostr any tips?

This should not happen. Clients should at least respect user ...

2026-04-17T22:09:37Z

In reply to nevent1q…mp4v
_________________________

This should not happen. Clients should at least respect user relays, and if they are good, they will support NIP-65. Without NIP-65, there will only be a few large relays that can censor users.

Here you go, the first real example written by nostr-scrolls, ...

2026-04-10T02:08:05Z

In reply to nevent1q…a4gf
_________________________

Here you go, the first real example written by nostr-scrolls, it's very simple.

https://github.com/rust-nostr/nostr-scrolls/blob/b66d2ff/nostr-scrolls/examples/resonate.rs

quoting
nevent1q…e3fx
AGFzbQEAAAABMAlgAX8AYAF/AX9gAn9/AGADf39/AGADf39/AX9gAn9/AX9gAAF/YAR/f39/AGAAAAKzAg8Fbm9zdHIDbG9nAAIFbm9zdHIJc3Vic2NyaWJlAAEFbm9zdHIEZHJvcAAABW5vc3RyDGV2ZW50X2dldF9pZAABBW5vc3RyDnJlcV9hZGRfYXV0aG9yAAIFbm9zdHIHZGlzcGxheQAABW5vc3RyFGV2ZW50X2dldF9jcmVhdGVkX2F0AAEFbm9zdHIHcmVxX25ldwAGBW5vc3RyDHJlcV9hZGRfa2luZAACBW5vc3RyDXJlcV9zZXRfc2luY2UAAgVub3N0cg1yZXFfc2V0X3VudGlsAAIFbm9zdHIRcmVxX2Nsb3NlX29uX2Vvc2UAAAVub3N0cg1yZXFfc2V0X2xpbWl0AAIFbm9zdHIQZXZlbnRfZ2V0X2lkX2hleAABBW5vc3RyC3JlcV9hZGRfdGFnAAcDHh0DAwAAAgICAgMFBQMDAAAIAAAAAggAAgAAAQABAwQFAXABBwcFAwEAEQYZA38BQYCAwAALfwBBkKzAAAt/AEGQrMAACwdIBwZtZW1vcnkCAANydW4AHAVhbGxvYwAoC19faGVhcF9iYXNlAwEHb25fZW9zZQApCG9uX2V2ZW50ACsKX19kYXRhX2VuZAMCCQwBAEEBCwYTFBUWERIK0R0dTwEBf0GOgMCAAEEGEICAgIAAIABBgIDAgAAgAUEBcSIDGyABQQF2QQ4gAxsQgICAgAACQCACKAIEIgFBAEgNACACKAIAIAEQgICAgAALAAskAQF/IAEQgYCAgAAhAyABEIKAgIAAIAAgAjoABCAAIAM2AgALDAEBfyABEJKAgIAAC3QBA38jgICAgABBIGsiASSAgICAAEEAQQA6APiHwIAAIAFBCGpBACgC9IfAgABBARCQgICAACABLQAMIQIgASgCCCEDIAFBwILAgAA2AhwgAUKAgICAEDcCFCADIAIgAUEUahCbgICAACABQSBqJICAgIAACwwAIAEgARCUgICAAAsSACABEIWAgIAAIAEQgoCAgAALDAAgASABEJaAgIAAC5gBAQJ/I4CAgIAAQSBrIgIkgICAgAACQCABEIOAgIAAIgMNAEH8gcCAAEHHAEGwgsCAABCagICAAAALIAJBGGogA0EYaikAADcDACACQRBqIANBEGopAAA3AwAgAkEIaiADQQhqKQAANwMAIAIgAykAADcDAEEAKAL0h8CAACACEISAgIAAIAEQgoCAgAAgAkEgaiSAgICAAAt9AQF/AkACQAJAIAEgAigCACIDEJiAgIAADQAgAiADQQFqNgIAQQAhAgwBCyABIAIQmYCAgABFDQEgAiACKAIAIgNBBGo2AgAgASADaigAACEBQQEhAgsgACABNgIEIAAgAjYCAA8LQciGwIAAQYcBQYyHwIAAEJqAgIAAAAs6AQF/QQAhAgJAAkACQCAAIAFqLQAADgICAQALQfiFwIAAQYEBQbiGwIAAEJqAgIAAAAtBASECCyACCx0BAX8gASABKAIAIgJBAWo2AgAgACACEJiAgIAACw8AIAAgASACEI+AgIAAAAurAgECfyOAgICAAEEwayIDJICAgIAAIAAQoYCAgAAQo4CAgAAgA0EsaiACQQhqKAAANgAAIAMgAikAADcAJAJAAkACQEEAKAKEmMCAACICQf8ASw0AIAJBFGwiBCABOgCMmMCAACAEIAA2AoiYwIAAIAQgAykAITcAjZjAgABBACACQQFqNgKEmMCAACAEQZSYwIAAaiADQShqKQAANwAAIANBBDYCFAwBCyADQRhqIANBKGopAAA3AAAgAyADKQAhNwARIAMgAToAECADIAA2AgwgAygCFEEERw0BCyADQQxqEKeAgIAAQQBBADoAiKzAgAAgA0EwaiSAgICAAA8LIANBDGoQp4CAgABBAEEAOgCIrMCAAEGohcCAAEGBAUHohcCAABCagICAAAALgQcBB38jgICAgABBMGsiASSAgICAACABQQA2AhwCQAJAAkACQAJAIABFDQACQCAAIAFBHGoQmYCAgABFDQAgASABKAIcIgJBBGo2AhwgACACaigAACECIAFBEGogACABQRxqEJeAgIAAIAEoAhQhAyABKAIQIQQgAUEIaiAAIAFBHGoQl4CAgAAgASgCDCEFIAEoAgghBkHUgsCAAEEeEICAgIAAAkAgBEEBcUUNACADQQFIDQMLAkACQCAGQQFxRQ0AIAVBAUgNAQsgAhCGgICAACEHEIeAgIAAIgBBBhCIgICAACAAQQcQiICAgAACQCAHIANBgKMFbEGA9SQgBEEBcRsiBGsiA0EASA0AIAAgAxCJgICAAAsCQCAHIARqIgRBAEgNACAAIAQQioCAgAALIAAQi4CAgAACQCAGQQFxRQ0AIAVBAEgNACAAIAUQjICAgAALAkBBAC0A+IfAgABFDQBBACgC9IfAgAAQgoCAgAALQQBBAToA+IfAgABBACAANgL0h8CAABCHgICAACIAQQYQiICAgAAgAEEHEIiAgIAAIAIQjYCAgAAiBEUNBCAAQeUAIARBwAAQjoCAgAAgAhCNgICAACIERQ0FIABB8AAgBEHAABCOgICAACAAEIuAgIAAIAEgAEEBEJCAgIAAIAEtAAQhBCABKAIAIQAgAUH0gsCAADYCKCABQoCAgIAQNwIgIAAgBCABQSBqEJuAgIAAIAAQnYCAgAAQnoCAgABBACgC/IfAgAAiBEH/AE0NBiABQYiDwIAANgIsIAFCgICAgBA3AiQgASAANgIgIAFBIGoQn4CAgABBAEEAOgCAmMCAAEHYhMCAAEH/AEGYhcCAABCagICAAAALQZyDwIAAQS1BtIPAgAAQmoCAgAAAC0Gch8CAAEGLAUHkh8CAABCagICAAAALQfCDwIAAQdcAQZyEwIAAEJqAgIAAAAtBxIPAgABBOUHgg8CAABCagICAAAALQfyBwIAAQccAQaCCwIAAEJqAgIAAAAtB/IHAgABBxwBBoILAgAAQmoCAgAAACyAEQQR0IgZBiIPAgAA2AoyIwIAAIAZCgICAgBA3AoSIwIAAIAYgADYCgIjAgABBACAEQQFqNgL8h8CAACABQQI2AiQgAUEgahCfgICAAEEAQQA6AICYwIAAIAIQgoCAgAAgAUEwaiSAgICAAAvUAQQCfwF+An8BfiOAgICAAEEgayIBJICAgIAAIAFBCGogABClgICAAAJAIAEoAghBAXFFDQAgASgCDCEAEJ6AgIAAIAFBGGogAEEEdCIAQYiIwIAAaiICKQIANwMAIAApAoCIwIAAIQNBACgC/IfAgABBf2oiBEEEdCIFQYiIwIAAaikCACEGIAAgBSkCgIjAgAA3AoCIwIAAIAIgBjcCAEEAIAQ2AvyHwIAAIAEgAzcDECABQRBqEKaAgIAAQQBBADoAgJjAgAALIAFBIGokgICAgAALMQACQEEALQCAmMCAAA0AQQBBAToAgJjAgAAPC0GshMCAAEE5QciEwIAAEJqAgIAAAAsXAAJAIAAoAgRBAkYNACAAEKaAgIAACwsaACAAEKGAgIAAIAAQnYCAgAAgABCCgICAAAv8AQQDfwF+A38BfiOAgICAAEEgayIBJICAgIAAIAEgABCigICAAAJAIAEoAgBBAXFFDQAgASgCBCEAEKOAgIAAIAFBEGogAEEUbCIAQZCYwIAAaiICKQIANwMAIAFBGGogAEGYmMCAAGoiAygCADYCACAAKQKImMCAACEEQQAoAoSYwIAAQX9qIgVBFGwiBkGYmMCAAGooAgAhByAGQZCYwIAAaikCACEIIAAgBikCiJjAgAA3AoiYwIAAIAIgCDcCACADIAc2AgBBACAFNgKEmMCAACABIAQ3AwggAUEIahCkgICAAEEAQQA6AIiswIAACyABQSBqJICAgIAAC3YBBH8Qo4CAgABBACECQQAoAoSYwIAAIQNBiJjAgAAhBEEAIQUDQAJAAkACQCADIAVHDQAgAyEFDAELIAQoAgAgAUcNAUEBIQILQQBBADoAiKzAgAAgACAFNgIEIAAgAjYCAA8LIARBFGohBCAFQQFqIQUMAAsLMQACQEEALQCIrMCAAA0AQQBBAToAiKzAgAAPC0GshMCAAEE5QciEwIAAEJqAgIAAAAtrAQF/AkACQAJAAkACQAJAIAAoAggOBAECAwABCyAAKAIQKAIAIgENAwwECyAAKAIQKAIAIgENAgwDCyAAKAIQKAIAIgENAQwCCyAAKAIQKAIAIgFFDQELIAAoAgwgARGAgICAAICAgIAACwt2AQR/EJ6AgIAAQQAhAkEAKAL8h8CAACEDQYCIwIAAIQRBACEFA0ACQAJAAkAgAyAFRw0AIAMhBQwBCyAEKAIAIAFHDQFBASECC0EAQQA6AICYwIAAIAAgBTYCBCAAIAI2AgAPCyAEQRBqIQQgBUEBaiEFDAALC0EBAX8CQAJAAkAgACgCBA0AIAAoAgwoAgAiAQ0BDAILIAAoAgwoAgAiAUUNAQsgACgCCCABEYCAgIAAgICAgAALCxcAAkAgACgCCEEERg0AIAAQpICAgAALC5ABAQN/QQAhAQJAAkAgAEGHgICAeGpBh4CAgHhNDQBBACEBQQhBACgCjKzAgAAiAkGQrMCAACACGyICQQdxIgNrQQAgAxsgAmoiAiAAaiIAIAJJDQAgAD8AQRB0IgNNDQFBACEBIAAgA2tBEHYgAEH//wNxQQBHakAAQX9HDQELIAEPC0EAIAA2AoyswIAAIAIL/gEBA38jgICAgABBEGsiASSAgICAACABQQhqIAAQpYCAgAACQAJAIAEoAghBAXFFDQAgASgCDCECEJ6AgIAAAkACQCACQQR0IgIoAoSIwIAAQQFHDQAgAkGIiMCAAGooAgAgAkGMiMCAAGooAgAoAhARgYCAgACAgICAACECDAELIAJBiIjAgABqKAIAIAJBjIjAgABqKAIAKAIQEYCAgIAAgICAgABBACECC0EAQQA6AICYwIAAIAAQqoCAgAAhAwJAIAINACADRQ0CCyAAEKCAgIAADAELIAAQqoCAgABFDQAgABChgICAACAAEIKAgIAACyABQRBqJICAgIAAC2oBAX8jgICAgABBEGsiASSAgICAACABQQhqIAAQooCAgABBACEAAkAgASgCCEEBcUUNACABKAIMIQAQo4CAgABBAEEAOgCIrMCAACAAQRRsLQCMmMCAACEACyABQRBqJICAgIAAIABBAXEL3QIBAn8jgICAgABBEGsiAySAgICAACADQQhqIAAQooCAgAACQCADKAIIQQFxRQ0AIAMoAgwhBBCjgICAAAJAAkACQAJAAkACQCAEQRRsIgQoApCYwIAADgQABAEDAAsgBEGUmMCAAGooAgAgASAEQZiYwIAAaigCACgCEBGCgICAAICAgIAADAELIARBlJjAgABqKAIAIAEgAkEARyAEQZiYwIAAaigCACgCEBGDgICAAICAgIAAC0EAQQA6AIiswIAADAMLIARBlJjAgABqKAIAIAEgAkEARyAEQZiYwIAAaigCACgCEBGEgICAAICAgIAAIQFBAEEAOgCIrMCAACABDQEMAgsgBEGUmMCAAGooAgAgASAEQZiYwIAAaigCACgCEBGFgICAAICAgIAAIQFBAEEAOgCIrMCAACABRQ0BCyAAEKGAgIAAIAAQgoCAgAALIANBEGokgICAgAALC/4HAQBBgIDAAAv0B3BhbmljIG9jY3VycmVkUEFOSUMhbm9zdHItc2Nyb2xscy9zcmMvdHlwZXMvZXZlbnQucnMAbm9zdHItc2Nyb2xscy9zcmMvdHJhaXRzLnJzAG5vc3RyLXNjcm9sbHMvc3JjL2hvc3RfZmZpL3V0aWxzLnJzAG5vc3RyLXNjcm9sbHMvc3JjL3V0aWxzLnJzAG5vc3RyLXNjcm9sbHMvc3JjL3R5cGVzL3N1YnNjcmlwdGlvbi5ycwBub3N0ci1zY3JvbGxzL3NyYy9zaW1wbGVfY2VsbC5ycwBub3N0ci1zY3JvbGxzL2V4YW1wbGVzL3Jlc29uYXRlLnJzAEludmFsaWQgcG9pbnRlciBieSB0aGUgaG9zdCBydW50aW1lAFEAEAAjAAAAMQAAAAkAAABRABAAIwAAACIAAAAJAAAAAAAAAAAAAAABAAAAAQAAAAIAAAByZXNvbmF0ZTogbG9hZGluZyB0YXJnZXQgZXZlbnQAAAAAAAAAAAAAAQAAAAMAAAAEAAAAAAAAAAAAAAABAAAABQAAAAYAAABsaW1pdCBtdXN0IGJlIHBvc2l0aXZlAADZABAAIgAAAEUAAAAJAAAAdGltZSB3aW5kb3cgbXVzdCBiZSBwb3NpdGl2ZdkAEAAiAAAAQQAAAAkAAABudWxsIHBvaW50ZXIgcGFzc2VkIGFzIGEgcGFyYW1ldGVycyBwb2ludGVyANkAEAAiAAAAPAAAAAEAAABTaW1wbGVDZWxsOiBhbHJlYWR5IGJvcnJvd2VkuAAQACAAAAAZAAAADQAAAEZhaWxkIHRvIHJlZ2lzdGVyIGEgbmV3IGBvbl9lb3NlYCBoYW5kbGVyLiBUaGUgaGFuZGxlcnMgaXMgZnVsbACQABAAJwAAAEYAAAANAAAARmFpbGQgdG8gcmVnaXN0ZXIgYSBuZXcgYG9uX2V2ZW50YCBoYW5kbGVyLiBUaGUgaGFuZGxlcnMgaXMgZnVsbJAAEAAnAAAAKQAAAA0AAABJbnZhbGlkIHByZXNlbmNlIGZsYWc6IGV4cGVjdGVkIDB4MDAgb3IgMHgwMSwgZ290IHNvbWV0aGluZyBlbHNldQAQABoAAAAQAAAADgAAAFJlYWRQYXJhbShpMzIpOiBFeHBlY3RlZCByZXF1aXJlZCBwYXJhbWV0ZXIsIGJ1dCBob3N0IHByb3ZpZGVkIDB4MDAANQAQABsAAABAAAAADQAAAFJlYWRQYXJhbShldmVudCk6IEV4cGVjdGVkIHJlcXVpcmVkIHBhcmFtZXRlciwgYnV0IGhvc3QgcHJvdmlkZWQgMHgwMAAAABQAEAAgAAAAEwAAAA0AAAA=

> you have knobs to set endianness and presence byte. Sounds ...

2026-04-09T16:04:31Z

In reply to nevent1q…70uy
_________________________

> you have knobs to set endianness and presence byte.

Sounds good, but you should remove it when the NIP become standard and use what is in the NIP

This is so cool!

2026-04-09T15:53:11Z

In reply to nevent1q…9kj0
_________________________

This is so cool!

Where can I find your runtime? I also want to test my scrolls :) ...

2026-04-09T12:20:31Z

In reply to nevent1q…kefx
_________________________

Where can I find your runtime? I also want to test my scrolls :)

I haven't published any scroll yet, all of them in my local relay.

Do your runtimre respect the new little-endian?

And you can build them as simple as this, using nostr-scrolls ...

2026-04-09T11:57:31Z

In reply to nevent1q…fu9p
_________________________

And you can build them as simple as this, using nostr-scrolls

```rust
#![no_std]
#![no_main]

use nostr_scrolls::{PublicKey, Filter, cb};

#[allow(unused_must_use)]
#[nostr_scrolls::main]
fn run(me: PublicKey) {
let filter = Filter::new();
filter.author(&me);
filter.kind(1);
filter.close_on_eose();
filter.tag('t', "asknostr");

let sub = filter.subscribe();
sub.on_event(cb!(|event| {
nostr_scrolls::display(&event);
}));
}
```

https://github.com/rust-nostr/nostr-scrolls

Is this a joke? I don't understand. With Bitcoin, I can see ...

2026-04-04T21:51:29Z

In reply to nevent1q…s2cm
_________________________

Is this a joke? I don't understand. With Bitcoin, I can see the concern due to its history, but why would it matter if your Monero comes from a miner? Also, as I understand it, only large companies, exchanges, and governments are interested in acquiring "clean" Bitcoin.

What if my screen is actually big?

2026-04-04T06:17:43Z

In reply to nevent1q…4lq7
_________________________

What if my screen is actually big?

this is a good NIP ...

2026-04-02T01:28:13Z

this is a good NIP https://github.com/nostr-protocol/nips/pull/2281

Cool domain

2026-03-31T08:19:07Z

In reply to nevent1q…d56f
_________________________

Cool domain

@nprofile…wcv8

2026-03-30T21:54:32Z

In reply to nevent1q…kwqc
_________________________

Constant (nprofile…wcv8)

Nostr event nevent1qqsqqqqq43tr4fw05079dzhgdmhrf60jkshu79cvjew0g7f0x0e9g4gzyqqqqqqp2p08ujyjwprwnwa2w2937w63zgn7ygqv27xku6ascaltjaq42ev

2026-03-30T15:00:55Z

I like rust-nostr.org

now I know what these numbers means

2026-03-27T21:30:29Z

In reply to nevent1q…zrwl
_________________________

now I know what these numbers means

ideas is not copyrighted :)

2026-03-27T21:27:26Z

In reply to nevent1q…p0gl
_________________________

ideas is not copyrighted :)

Don't you ever need cash? For example, to buy something at a ...

2026-03-27T21:25:06Z

In reply to nevent1q…8x0x
_________________________

Don't you ever need cash? For example, to buy something at a gas station or a similar place.

True :) #nevent1q…05s2

2026-03-26T17:34:01Z

True :)

quoting
nevent1q…05s2
Nostr is so uncensored that you can’t even censor yourself

to do the same task or in general?

2026-03-24T15:20:08Z

In reply to nevent1q…u8p9
_________________________

to do the same task or in general?

This is how a #GRASP relay sync its git repos based on the ...

2026-03-24T00:53:42Z

This is how a #GRASP relay sync its git repos based on the maintainers list and repo ID. Thank you DanConwayDev (npub15qy…yejr) and fiatjaf (npub180c…h6w6) for this cool protocol.

More about GRASP: https://gitworkshop.dev/danconwaydev.com/grasp

cc: Yuki Kishimoto (npub1drv…seet) dluvian (npub1use…k5ks) Silberengel (npub1l5s…gx9z)

The Iranian people have been without internet access for the past ...

2026-03-22T08:32:40Z

The Iranian people have been without internet access for the past 23 days.

#FreeIran

I enjoy watching Tsoding's recreational programming streams, ...

2026-03-19T06:04:52Z

I enjoy watching Tsoding's recreational programming streams, they are cool and I always learn something.

However, every time I watch one, I hate Go and C more, I don't understand how and why people use them!

> Give your agent the ability to securely pay for what you ...

2026-03-19T05:46:38Z

In reply to nevent1q…ersp
_________________________

> Give your agent the ability to securely pay for what you need as you code.

The intent is to embed prompts within advertisements.

This made me feel uncomfortable

2026-03-19T05:41:16Z

In reply to nevent1q…x584
_________________________

This made me feel uncomfortable

this is better ```rust for manager in ...

2026-03-18T00:08:54Z

In reply to nevent1q…evnt
_________________________

this is better

```rust
for manager in self.plugins_managers.as_ref() {
if let reject @ WritePolicyResult::Reject { .. } =
manager.admit_event(event, addr).await
{
return reject;
}
}
```

As a user, I prefer Marmot because it's more secure. But as a ...

2026-03-17T23:19:33Z

As a user, I prefer Marmot because it's more secure. But as a developer, I find it a bit more complex (though I haven’t looked into it deeply). NIP-17 is simpler.

quoting
nevent1q…ncfp
What should we do about DMs on nostr?

Cool using of binding in rust ...

2026-03-17T23:08:46Z

Cool using of binding in rust https://doc.rust-lang.org/rust-by-example/flow_control/match/binding.html

```rust
for manager in self.plugins_managers.as_ref() {
match manager.admit_event(event, addr).await {
reject @ WritePolicyResult::Reject { .. } => return reject,
_ => {}
}
}
```

#rust

There is nak.nostr.com :) I mean, of course there is another ...

2026-03-17T18:22:53Z

In reply to nevent1q…dflm
_________________________

There is nak.nostr.com :) I mean, of course there is another reason, I haven't tried it yet

> but it is the most important Nostr client. Why?

2026-03-17T18:14:56Z

In reply to nevent1q…dm5v
_________________________

> but it is the most important Nostr client.

Why?

I like this song

2026-03-04T13:08:49Z

In reply to nevent1q…nfwl
_________________________

I like this song

Equality is not fairness. How can it be fair that someone with a ...

2026-03-02T21:48:29Z

Equality is not fairness.

How can it be fair that someone with a low income pays the same amount of VAT as someone with a high income? One person is afraid to spend their monthly income because of rising prices, while the other doesn't even bother to ask about the price before buying.

The first one doesn't drive much because of minor traffic violations like veering off course or slightly exceeding the speed limit. The second driver gets three speeding tickets on his way to the airport because he doesn't care. How is that fair?

Fuck the system!

there is no nixpkgs maintainer, each package have its ...

2026-03-02T15:04:57Z

In reply to nevent1q…fger
_________________________

there is no nixpkgs maintainer, each package have its maintainers.

if you just changed the hash to an incorrect one, nix will show you an error and the package won't be built.

if you mean changing the source to a malicious source code, other maintainers or anyone else saw the incorrect source, they will report it and it will be fixed. You can also check the package source by running `nix-edit` command.

Also not any change on the packages will be chipped to the stable nixpkgs version, it chipped to the unstable first.

Hi @nprofile…jejf, this note is pinned in my timeline because ...

2026-03-02T05:55:51Z

Hi utxo the webmaster 🧑‍💻 (nprofile…jejf), this note is pinned in my timeline because its timestamp in the future (2048)

nostr:nevent1qqs2h5d4224xmvvkalap64k2lu2lfphuezpdsts8f5ywx3c8mksvsdcprfmhxue69uhhyetvv9ujucnjd9nksarzdak8gtnwv46qyg9hyaxj3clfswlhyrd5kjsj5v04clhjvgeq6pwztmysfzdvn93geva2mmxg

> Smarter DM Delivery: messages now route to the ...

2026-03-02T02:10:58Z

In reply to nevent1q…rx6y
_________________________

> Smarter DM Delivery: messages now route to the recipient's preferred relays

Do you also send the author's `kind:10002` event to all relays the event was published to? as specified in NIP-65

> Smarter DM Delivery: messages now route to the ...

2026-03-02T02:08:44Z

In reply to nevent1q…rx6y
_________________________

> Smarter DM Delivery: messages now route to the recipient's preferred relays, for those with custom relay setups

I disagree with the phrase "for those with custom relay setups". Sending events to the recipient's relays should be the default for every Nostr client, as specified in NIP-65. Nostr's decentralization relies on not centralizing around shared relays.

Thank you for the app. 🫡

Happy birthday Vezire 🥳

2026-03-02T01:53:50Z

In reply to nevent1q…95sm
_________________________

Happy birthday Vezire 🥳

> What is the source of the known hash? The known hash is ...

2026-03-02T00:19:00Z

In reply to nevent1q…93uc
_________________________

> What is the source of the known hash?

The known hash is manually entered in the package's Nix file. When adding a new package, you specify its source (e.g., Git or crates.io) and initially leave the hash field empty. Nix will then download the source, compute its hash, and error because it doesn't match the empty value. You simply copy this computed hash from the error message into the file to finalize it.

Check the nixpkgs GitHub repo. Search for a program's package file to see its hash and the PR that updated it.

I just use nixpkgs, all the packages are hash-verified. Cool

2026-02-28T13:05:31Z

In reply to nevent1q…jzw8
_________________________

I just use nixpkgs, all the packages are hash-verified. Cool

Yes ✊

2026-02-17T08:59:16Z

In reply to nevent1q…uwr8
_________________________

Yes ✊

Why?

2026-02-13T12:12:39Z

In reply to nevent1q…h9qj
_________________________

Why?

Having multiple ways to entertain yourself in your free time ...

2026-02-08T19:45:16Z

Having multiple ways to entertain yourself in your free time isn't ideal. You'll want to do them all, and you won't be able to do that without reducing your work time

#naddr1qv…rpww

2026-02-07T12:01:49Z

quoting naddr1qv…rpww

The difference between a service that dies and a protocol that survives is architectural. A service has an operator and a legal jurisdiction that can be pressured. A protocol has none of these, which is why a single injunction killed Napster while two hundred thousand lawsuits did nothing to BitTorrent. The design decision that separates them is whether the system requires any specific human being to continue operating. If it does, that human is the attack surface.

This principle extends to every layer of the stack. A smart contract deployed to a blockchain that no one can modify or withdraw falls outside the reach of sanctions law, because what belongs to no one cannot be sanctioned. Code that requires an operator to run a server or coordinate transactions creates a pressure point that the state will eventually find and squeeze. The architectural question every protocol designer must answer: after I walk away, does this keep running?

Governments have converged on five strategies for attacking systems they cannot shut down directly.

The first is prosecuting developers. When code itself is beyond reach, the people who wrote it become targets. Privacy tool developers have faced criminal charges for money laundering and operating unlicensed money transmitting businesses, with sentences measured in years and forfeitures measured in hundreds of millions. The legal theory that building a tool makes you responsible for its misuse has been applied even when the tool operates autonomously after deployment. For builders, the practical implication is clear: legal exposure correlates with operational involvement. Writing and deploying immutable code carries less legal surface area than running a service built on that code.

The second is controlling distribution. A protocol that cannot reach users exists only in theory. App store gatekeepers control software distribution for billions of devices and have removed privacy-focused applications without explanation or recourse. Any system depending on a single distribution channel has a single point of failure, regardless of how decentralized its protocol layer might be. Sideloading, alternative stores, progressive web apps, and direct binary distribution all provide redundancy, but each one narrows the potential user base. Building for multiple distribution channels from the start is cheaper than retrofitting after your primary channel disappears.

The third is attacking the network layer. Deep packet inspection identifies protocol traffic by its byte patterns, and governments with sufficient infrastructure block identified traffic at the ISP level. The most aggressive approach blocks all fully encrypted traffic that fails to match known protocol fingerprints, accepting collateral damage to legitimate services. The countermeasure is encrypted transport that makes protocol traffic indistinguishable from ordinary web traffic. When blocking your protocol means blocking HTTPS itself, only a government willing to break its own internet can sustain the censorship.

The fourth is exploiting centralization. Decentralized protocols tend to centralize in practice. When two mining pools control over fifty percent of block production under one regulatory jurisdiction, or one relay handles seventy percent of all posts, the protocol's theoretical decentralization is operationally meaningless. These concentration points create pressure that regulators can exercise at trivial cost. Dominant relays and large mining pools exist because users and operators choose convenience over distribution, and every one of them is a target.

The fifth is economic attrition through compliance costs. The global anti-money laundering system costs $275 billion per year and catches less than one percent of criminal proceeds. Banks spend hundreds of millions each on compliance to avoid regulatory penalties; crime prevention is incidental to the calculation. Each enforcement action against a protocol creates a new compliance category, generating demand for new monitoring tools. The compliance industry grows with each demonstration of its own ineffectiveness. The cost falls on every entity that interfaces between open protocols and the traditional financial system, creating a buffer zone of institutions too afraid of regulatory liability to touch anything novel.

The protocols that survive these attacks share a set of design properties, each one a direct answer to one of the vectors above.

Eliminate operator dependency. If the system requires a specific person or company to function, that person or company will eventually be pressured or arrested. The design target is a system that runs on any willing machine with no coordination from its creators. The test: if every original developer disappeared tomorrow, would the protocol keep running without them?

Build redundant distribution from day one. Satellite broadcasts requiring only a receiver dish and mesh networks operating on unlicensed radio spectrum both eliminate potential chokepoints at layers the state does not control. No single distribution channel should be necessary for the protocol to reach its users. The projects that treat distribution as an afterthought discover its importance when their primary channel vanishes overnight.

Encrypt all transport by default. Traffic that is identifiable is traffic that can be blocked. Encrypted transport that makes every byte appear uniformly random forces censors into an expensive choice: block all unidentified encrypted traffic and accept massive collateral damage, or allow the protocol through. For protocols operating in adversarial environments, this is a survival requirement.

Treat decentralization as a discipline. The natural tendency of every network is to concentrate around a few high-capacity nodes, and this tendency must be actively resisted through relay diversity, geographic distribution of infrastructure, multiple independent client implementations, and low barriers to running nodes. A protocol that launches decentralized and drifts toward concentration has a shelf life determined by how long it takes regulators to notice.

Intellectual honesty demands acknowledging the limits. Governments do not need to break the cryptography. They need to make the human interfaces painful enough that ordinary users never encounter the protocol at all. A system confined to sideloaded apps and terminal commands will serve its committed users, but it will not become the default communication layer for a billion people. The UX gap between centralized services and decentralized protocols remains the most effective form of soft censorship, and no architectural principle solves it alone.

The economic asymmetry cuts both ways. Protocol adaptation is cheap, but building usable software is expensive. The open-source projects that sustain these protocols operate on budgets that would not cover a single bank's compliance department. Survival and mass adoption are different problems requiring different resources, and most protocols will achieve the first without ever reaching the second.

The humans who build these protocols pay real costs: years behind bars and millions in forfeiture. The code they write pays nothing. It copies itself across every willing machine on the network, indifferent to the legal theories arrayed against its creators. The state can punish the hand that types, but it has never succeeded in erasing what was typed. For builders, the lesson is structural: design for a world where you are not around to run it, distribute through channels no single entity controls, encrypt so censors cannot identify it, and resist the centralization that makes all other defenses irrelevant.

Vector (@nprofile…8pny) has some seriously cool looking posts! ...

2026-02-07T11:57:54Z

Vector (VectorPrivacy (nprofile…8pny)) has some seriously cool looking posts! Thanks YuurinBee (nprofile…3vkx) for your brilliant work on making them so visually engaging! 🫡

quoting
nevent1q…kup5

nostr:nevent1qvzqqqqqqypzpw8e9es7w829s6hxle5hpaea6r7m3yqsjky79aqhhm6ytwa6jtydqy88wumn8ghj7mn0wvhxcmmv9uq3qamnwvaz7tmwdaehgu3wd4hk6tcqyqawndkw5mv47hfagnxtdhealrj3hp88rv90zg3cmyh67d9yxvcmckdxnfc

why you reply with LLM output?

2026-02-03T01:33:02Z

In reply to nevent1q…j8sw
_________________________

why you reply with LLM output?

Agree, you should try https://n34.dev

2026-02-01T19:26:46Z

In reply to nevent1q…u3cq
_________________________

Agree, you should try https://n34.dev

Normal person?

2026-01-30T10:41:25Z

In reply to nevent1q…juc7
_________________________

Normal person?

I use ProtonVPN, but if you don't need Proton services, I ...

2026-01-28T04:01:41Z

In reply to nevent1q…2shc
_________________________

I use ProtonVPN, but if you don't need Proton services, I recommend MysteriumVPN

Nostr event nevent1qqsqqqq9z58mlkqhpq5zrtc7wplcxk929aqg7cj9hx8zvc9lpt3jucczyqqqqqqp2p08ujyjwprwnwa2w2937w63zgn7ygqv27xku6ascaltj2kjt9v

2026-01-23T22:07:35Z

today I tried #hytale, it's a good game

You can do something similar using NIP-98. You will sign the ...

2026-01-16T23:01:56Z

In reply to nevent1q…ya83
_________________________

You can do something similar using NIP-98. You will sign the event using NIP-07. Which is easy `window.nostr`

it's insane

2026-01-14T21:03:05Z

In reply to nevent1q…a8ev
_________________________

it's insane

Yes, check #monero

2026-01-13T06:18:35Z

In reply to nevent1q…tfhn
_________________________

Yes, check #monero

There is 100K public keys in my relay having less than 10 events ...

2026-01-11T01:23:32Z

There is 100K public keys in my relay having less than 10 events and no one of these events is a private message. Only 12K does have a private message.

#relay

Bitchat is great, but we are not in the same country

2026-01-10T13:22:10Z

In reply to nevent1q…tuhl
_________________________

Bitchat is great, but we are not in the same country

The Iranian government has cut off the internet for most ...

2026-01-10T13:18:32Z

The Iranian government has cut off the internet for most Iranians, including my friend Kayhan Sepanta (nprofile…wvxz) . I hope he's okay. Fuck this corrupt government.

🫡🫡

2026-01-04T15:25:38Z

In reply to nevent1q…lhlk
_________________________

🫡🫡

I hope it will be a great year in which we develop Nostr and make ...

2025-12-31T22:00:37Z

I hope it will be a great year in which we develop Nostr and make it better than 2025.

Thanks to the relays operators

2025-12-24T06:51:04Z

In reply to nevent1q…yzs6
_________________________

Thanks to the relays operators

> ᴀɴᴅ ɢᴇᴛ ᴡᴀʀɴɪɴɢꜱ ꜰʀᴏᴍ ...

2025-12-23T07:38:35Z

In reply to nevent1q…ra2p
_________________________

> ᴀɴᴅ ɢᴇᴛ ᴡᴀʀɴɪɴɢꜱ ꜰʀᴏᴍ ᴊᴜᴍʙʟᴇ ᴛʜᴀᴛ ɪ ʜᴀᴠᴇ ᴛᴏᴏ ᴍᴀɴʏ ʀᴇʟᴀʏꜱ

Just ignore it, you can have as many relays as you want, I don't know why it's suggested in the NIP to have less than 6.

> *ᴀᴅᴅɪɴɢ* ᴍʏ ʀᴇʟᴀʏ ᴛᴏ ʜɪꜱ ʟɪꜱᴛ ᴀꜱ "ᴄᴇɴᴛʀᴀʟɪᴢɪɴɢ" ʙᴇᴄᴀᴜꜱᴇ ᴏʙᴠɪᴏᴜꜱʟʏ, ᴛʜᴀᴛ'ꜱ ᴛʜᴇ ᴏᴘᴘᴏꜱɪᴛᴇ

Why? you asking him to publish his events to a relay in your list, this isn't decentralization if I have to write to relays of people I know. Each person writes to whatever relay they want, and you (as a follower) have to listen to those relays and fetch their events.

To clarify, the client can connect to any relay without needing you to add it. The basis of Nostr's decentralization is its multiple relays. When the client forces you to use a specific set of relays, this isn't decentralization; the client has to connect to the relays of those you follow to fetch their events.

The client can also send to any relay, and must send the event to your read relays if the event mentioned you.

What client you are using? so I can report this issue.

Nostr is decentralized, it will be centralized if we all used the ...

2025-12-23T07:05:59Z

In reply to nevent1q…xjnx
_________________________

Nostr is decentralized, it will be centralized if we all used the same relays to see each other.

Gowron's client should not send the events to your relay, it doesn't makes sense to send my events to everyone relays.

Instead, Gowron's client send the events to Gowron's write relays, and your client should read from it and fetch Gowron's events, why? because Gowron in your follow list (contact list).

What is your client?

Everyone should run a Nostr relay, whether local or public, or at ...

2025-12-22T10:00:31Z

Everyone should run a Nostr relay, whether local or public, or at least back up their own events.

Yes, I remember a client did this, it generate the private key ...

2025-12-21T16:18:10Z

In reply to nevent1q…2na0
_________________________

Yes, I remember a client did this, it generate the private key from your fingerprint.

But yeah, your private key will be public if you generated it like this.

PayTo: Payment Targets (RFC-8905) ...

2025-12-21T12:01:46Z

In reply to nevent1q…c77c
_________________________

PayTo: Payment Targets (RFC-8905)

https://github.com/nostr-protocol/nips/pull/2119

Nostr is decentralized, anyone can run a relay. If I broadcast my ...

2025-12-21T11:58:15Z

In reply to nevent1q…fxsk
_________________________

Nostr is decentralized, anyone can run a relay. If I broadcast my notes to 3 relays that are not will known, you will never find my notes without knowing my relays first, because they are in it.

Global means global, not 150 most used relays. There is more than 1600 nostr relay out there.

Yeah, we should focus on personalized WoT, not the global one.

2025-12-21T11:51:10Z

In reply to nevent1q…kg6c
_________________________

Yeah, we should focus on personalized WoT, not the global one.

Nostr event nevent1qqsqqqqzrsw64ctklj0cfvle7nka7453k2cd235xxk9zwy4ryas0qpczyqqqqqqp2p08ujyjwprwnwa2w2937w63zgn7ygqv27xku6ascaltjmjx824

2025-12-21T04:41:41Z

Nostr is decentralized; there is no global truth.

how does it works? The client comes with a local relay and it ...

2025-12-20T07:43:33Z

In reply to nevent1q…vs2t
_________________________

how does it works? The client comes with a local relay and it also search for other locals relays?

Why a gift wrapped kind 1? why not a kind 14, chat message?

2025-12-14T19:33:26Z

In reply to nevent1q…k6rp
_________________________

Why a gift wrapped kind 1? why not a kind 14, chat message?

Nostr always like this, this is why we use Web of Trust

2025-12-13T13:38:34Z

In reply to nevent1q…cfxl
_________________________

Nostr always like this, this is why we use Web of Trust

Same, I said WTF. lol

2025-12-12T20:51:02Z

In reply to nevent1q…2dan
_________________________

Same, I said WTF. lol

wish you the best

2025-12-12T19:59:06Z

In reply to nevent1q…vpnz
_________________________

wish you the best

Unblock her and tell her you were high :)

2025-12-12T19:57:25Z

In reply to nevent1q…vh4l
_________________________

Unblock her and tell her you were high :)

How your app will be good if you don't understand it? Also I ...

2025-12-11T05:17:31Z

In reply to nevent1q…ue7v
_________________________

How your app will be good if you don't understand it? Also I noticed couple Nostr web apps that doesn't works, or have a functionality that doesn't works, I think this is because of vibe coding.

Don't track what I saw and what I didn't, please

2025-12-10T19:09:13Z

In reply to nevent1q…dz3l
_________________________

Don't track what I saw and what I didn't, please

No please

2025-12-10T18:57:16Z

In reply to nevent1q…nd6g
_________________________

No please

agreed

2025-12-10T08:58:08Z

In reply to nevent1q…eltl
_________________________

agreed

truly

2025-12-10T08:44:10Z

In reply to nevent1q…pz0x
_________________________

truly

By the way, atproto is a decentralized protocol, but the problem ...

2025-12-10T08:41:26Z

In reply to nevent1q…hcg6
_________________________

By the way, atproto is a decentralized protocol, but the problem is that most people use a single client, which is centralized (bscy). That's why I like having many clients in Nostr (because it's simpler than atproto). It's true there are some large clients (which I don't like), and I hope they don't get any larger.

why?

2025-12-09T23:53:18Z

In reply to nevent1q…xgye
_________________________

why?

I would like personalized WoT more than a global one

2025-12-08T19:56:22Z

In reply to nevent1q…kuh4
_________________________

I would like personalized WoT more than a global one

> I love that we have all these WoT services and metrics ...

2025-12-07T22:01:59Z

In reply to nevent1q…9f8h
_________________________

> I love that we have all these WoT services and metrics popping up, but I am concerned that it could lead to centralization.

Agree, I think each client should have a build-in lightweight WoT algorithm, we can archive that with a simple portable WoT library, it shouldn't sync its index 24/7 only once every couple days are enough.

The index size should not be that much, I think it will be 2~3GB maximum if the user have a big network.

cc: Kayhan Sepanta (nprofile…wvxz)

Can it read the content from the stdin?

2025-12-06T11:39:26Z

In reply to nevent1q…99ra
_________________________

Can it read the content from the stdin?

Is this AI!!!

2025-12-06T11:29:10Z

In reply to nevent1q…j7ef
_________________________

Is this AI!!!

I'm using Coracle with 20 as a default PoW

2025-08-24T21:17:27Z

In reply to nevent1q…54wz
_________________________

I'm using Coracle with 20 as a default PoW

Yeah, PoW for the win; by @nprofile…633s

2025-08-24T21:06:35Z

In reply to nevent1q…9c79
_________________________

Yeah, PoW for the win; by DanConwayDev (nprofile…633s)

lol

2025-08-24T21:01:07Z

In reply to nevent1q…jqn5
_________________________

lol

#nevent1q…u3ah

2025-08-20T08:41:01Z

quoting nevent1q…u3ah
Gitplaza v0.4.0 is out:

### Features
- Open nevent and note IDs
- List releases in profile and repo view
- List posts in profile view
- Comment on releases (and other event kinds that can be viewed now)
- Show referenced event IDs and coords above post
- Open post by clicking card in posts view

### Improvements
- Increase task buffer size
- Simplify actors

### Performance
- Fetch database faster
- Don't wait for full relay initialization to start subscriptions
- Copy less data

### Documentation
- Add PR link for release events to README.md

Link: https://codeberg.org/dluvian/gitplaza/releases/tag/v0.4.0

#gitplaza #releastr #gitvianostr

Hi, welcome to Nostr buddy

2025-08-18T07:55:28Z

In reply to nevent1q…krfg
_________________________

Hi, welcome to Nostr buddy

#nevent1q…a2p3

2025-08-12T00:16:25Z

quoting nevent1q…a2p3
We need to get out skates on with #GitViaNostr I'm convinced ngit.dev/grasp is the key to a decentralised alternative to github. We need more server implementations and people running them.
nevent1q…qaj3

They are at least connected to each other :)

2025-08-12T00:12:47Z

In reply to nevent1q…8tu7
_________________________

They are at least connected to each other :)

Looks cool

2025-08-11T06:06:48Z

In reply to nevent1q…rnv4
_________________________

Looks cool

xmrbazaar is great #monero #xmr #marketplace ...

2025-08-10T21:47:08Z

xmrbazaar is great #monero #xmr #marketplace

https://xmrbazaar.com/user/Awiteb/

Because of what?

2025-08-09T16:44:04Z

In reply to nevent1q…p8r8
_________________________

Because of what?

I'm using Proton.me, which costs $13 per month. Don't opt ...

2025-08-09T13:37:12Z

In reply to nevent1q…njyr
_________________________

I'm using Proton.me, which costs $13 per month. Don't opt for the 'Individuals Unlimited' plan; choose the 'Proton Business Suite' instead, it's available for individuals, includes SMTP, and both plans are the same price.

Exactly, you can mix them and make something you comfortable ...

2025-08-08T22:08:47Z

In reply to nevent1q…g6kj
_________________________

Exactly, you can mix them and make something you comfortable with, like using ngit for sending and fetching but n34 for issues and reviewing patches.

Thank you, looking back for your feedback

2025-08-08T20:29:39Z

In reply to nevent1q…4vt7
_________________________

Thank you, looking back for your feedback