Which tool is that?

Tangential to the problem I mentioned. For the nice url, the @ could still be replaced with a /, too.

While it makes for a nicer URL, it is not recommended. These links get copied and people don't keep their nip05 resulting in broken links very quickly.

5 1/4. I remember they were sold single-sided or double-sided but you could punch a hole to mark the single-sided double-sided which they usually were.

I want to second the "what?".

Nowadays, "off" is a lie.

What else is in your network? Is "Wake on LAN" enabled in the bios?

whyNotBoth.jpg

Show the zaps and npubs in different bars at once.

As npubs have no cost, I'd really not want to see npub counters of accounts that I'm not at least following indirectly.

Wait, nostr:npub1wxl6njlcgygduct7jkgzrvyvd9fylj4pqvll6p32h59wyetm5fxqjchcan zapped? I thought when people use it, the recipient would still know who zapped?

Was it deemed a threat?

@libreoffice these buttons are confusing. ;D

https://void.cat/d/8Ny8xZ9pfEgYLmERdkcNPe.webp

For what it's worth, I opted for Deno. The following finds all t he accounts that have accepted badges on the Damus relay:

```

#!/bin/sh

//bin/true; exec deno run -A "$0" "$@"

import { Nostr, Relay, NostrKind } from "https://deno.land/x/nostr_deno_client@v0.2.7/mod.ts";

// import { Nostr, Relay, NostrKind } from "../nostr.ts";

const nostr = new Nostr();

nostr.relayList.push({

url: 'wss://relay.damus.io'

});

nostr.on('relayConnected', (relay: Relay) => console.log('Relay connected.', relay.name));

nostr.on('relayError', (err: Error) => console.log('Relay error;', err));

nostr.on('relayNotice', (notice: string[]) => console.log('Notice', notice));

await nostr.connect();

const set = {};

var round = 1;

var d = Math.round(Date.now() / 1000);

while (true) {

const filter = {

kinds: [30008],

until: d - 1,

limit: 200

};

const allNotes = await nostr.filter(filter).collect();

console.log(`Round ${round++}. We had ${Object.keys(set).length} users and found ${allNotes.length}, probing until ${new Date(d * 1000)} ...`)

if (allNotes.length === 0) {

break;

}

d = allNotes.reduce( (result, item) => {

return Math.min(result, item.created_at)

}, d)

for await (const note of allNotes) {

set[note.pubkey] = note.tags.length;

}

}

for (const [k, v] of Object.entries(set)) {

console.log(`${k} ${v}`);

}

Deno.exit();

```

1249 accounts accepted badges. How many of them might be interested in my "Badges Badge" https://badges.page/b/naddr1qqx5jgrvd94k2grzv9jxwetnqgsydl97xpj74udw0qg5vkfyujyjxd3l706jd0t0w0turp93d0vvungrqsqqqafew90d6s ?

ChatGPT "thinks" it's benign. I asked "What protocol is trojan in trojan://someUserId@123.23.23.3/..." and got:

The URL scheme "trojan://" is not a standard protocol like HTTP or FTP. It is commonly associated with Trojan proxies, which are a type of network proxy that allows users to bypass internet censorship and access blocked websites.

In the context of "trojan://someUserId@123.23.23.3/...", it appears to be a representation of a Trojan proxy configuration. Here's a breakdown of the components:

"trojan://" indicates the URL scheme associated with Trojan proxies.

"someUserId" represents a placeholder for the user ID or username.

"123.23.23.3" is an example IP address, which could be the address of the server hosting the Trojan proxy.

"/..." denotes that there may be additional path or query parameters following it, but without specific information, it's challenging to determine their purpose.

It's important to note that the term "trojan" is often used to refer to malicious software, specifically Trojan horses, which are a type of malware that disguises itself as legitimate software. However, in the context of the URL scheme "trojan://," it typically refers to the usage of Trojan proxies rather than malicious software.

On which client?

People are slow to cull relays. Me included.

Doesn't sound like a tool anyone could try out quickly :(

What is the best tool to scrape all relays for specific events as a one-off task?

For example I have a list of 50 relays and want to know which version (event id) of my profile is stored on each of them.

My current approach is to go to https://nostr.info/relayr/ , patch the `ws.onmessage` callback to `console.log` what I need and then to either use the UI or further call on the dev console what the UI would call.

Fellow nostr devs, how do you do this?

What would it take to make it work again? Pay Twitter millions?

You're making a strong case for a nostr-based ticketing system independent of source code control. I think that makes a lot of sense.

If you figure it out, poke Jack. He's offering 10BTC for a GitHub replacement although he didn't define well what he expects.