nostromat

Public Key

npub19e4p34nd4l03l9s4athl78geqshljrdveu0jeyjfkftgem8qqgmqwxmwvd

Profile Code

nprofile1qqszu6sc6ek6lhcljc274mllr5vsgtlepkkv78evjfymy45vansqydspr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9uq3samnwvaz7tmjv4kxz7fwdehhxamgv4ex2tnrdaksg6rtsx

Publishing to

relay.snort.social

relay.noswhere.com

relay.nostr.band

Author Public Key

npub19e4p34nd4l03l9s4athl78geqshljrdveu0jeyjfkftgem8qqgmqwxmwvd

Show more details

Last Notes

2023-02-02 18:38:23

- reply

Run my own relay then. But it's hardly likely, unless the guy is posting CP

2023-02-02 18:36:30

- reply

I write to 8 relays currently. That's probably too much but you see the point? If one of them deletes my DMs it doesn't matter

2023-02-02 18:23:24

- reply

You realise that nobody apart from the sender and recipient can read the DMs?

2023-02-02 18:17:56

- reply

Sounds like you didn't get it actually

2023-02-02 17:12:44

- reply

Yes that's all a client needs to do. For additional services like text search you need a search server etc

2023-02-02 17:05:52

- reply

It's actually very light on webserver resources. Basically you load up the client once and that's it. You can handle vast amounts of traffic on such a client at very low cost

2023-02-02 17:03:24

- reply

That's incorrect, browsers can run the protocol just fine. There are other clients without a backend. My client does not have a backend

2023-02-02 16:57:42

- reply

The load needs to be shared across relays so that people can help by spinning up a new relay, instead of this centralization

2023-01-26 16:31:53

- reply

https://nostrom.at/

2023-01-26 14:20:13

- reply

Anyone can submit a pull request with their proposal and you can read through existing open and accepted PRs to see how it works

2023-01-26 13:16:53

- reply

If you wanted to use the protocol, for example, to share data for a vehicle tracking application, you could absolutely do that, it would just use different kinds of events

2023-01-26 12:53:11

- reply

Specifications are here https://github.com/nostr-protocol/nips

2023-01-26 12:45:49

- reply

We're using clients that post basic "text" notes that contain a content field. If you want more complex content, you would use a different kind of note.

2023-01-25 15:22:45

- reply

Seems like a nice idea. Maybe something for the self-hosting people to add to their servers

2023-01-25 00:12:49

- reply

I'm not too happy about the timestamps

2023-01-23 15:37:53

- reply

I was disappointed when coinbase started adding all the shittiest shitcoins. Most of their volume is from BTC and ETH anyway

2023-01-22 12:57:42

- reply

You can run any version of bitcoin core you want. You cannot run a different version of congress

2023-01-17 00:25:45

- reply

It's worse if everybody just uses the same 10 relays I see all the time. The client sees a lot of other lesser-known relays and can actually help to decentralise by using them.

2023-01-17 00:16:53

- reply

The client should be able to find relays with the 'censored' data through the protocol, rather than the user having to intervene. Manual will be there but it's like one of those mobile settings pages only 1% of people use

2023-01-17 00:05:36

- reply

Automatic management is the way forward imo. Most people won't care too much about which relays they use. But to do that properly is a nice to have at this stage

2023-01-16 18:20:20

- reply

Yeah there are definitely people who take offence to being blocked and will try to harass you for it on other channels or through mutuals.. it's sad but they are out there

2023-01-16 18:17:29

- reply

Yes, exactly like this

2023-01-16 17:44:02

- reply

Ah there is a proof-of-work NIP already too. Awesome!

2023-01-16 17:37:02

- reply

Yes, likely need something like NIP-05 to filter on so that there's some sort of cost involved to creating spam accounts

2023-01-16 17:30:20

- reply

But also tempting to keep refining your code when it's already just good enough!