NIP: add idsOnly param to REQ? Relays would reply with event ids only, not the full event. You would only request the full event if you didn’t already receive it from other peers or local cache. This is basically how bitcoin advertises objects with inv messages which are then requested with getdata if needed.

Example:

1. Add idsOnly param to REQ messages, so the relay responds with event ids only, not the full event.

2. Get an event id that you don't already have. Request it and get the full event as response.

3. After a few hundred milliseconds, receive the same event id from 3 other relays. Don't request it this time, as you already have it. Up to 75% bandwidth saved, depending on the event content size in relation to the requests.

Psychedelic watching people chat with gpt3 https://iris.to/#/profile/npub1tsgw6pncspg4d5u778hk63s3pls70evs4czfsmx0fzap9xwt203qtkhtk4

https://iris.to/ now supports nostr feed, replies, likes, profile editing etc. It’s quickly hitting the subscription limit on the relay though, need to bundle the requests. I’ll be working on it again after Christmas.

https://iris.to/#/post/767d342a09448955628ffac40ed3f4e5cc1669eb5f9d5d71f3495312ec97c155

On the profile pages only, no aggregate feed yet

Messages and follows now working on Iris (sometimes) https://iris.to/#/profile/82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2

Moi! Valitettavasti kehitys ei vielä liene niin pitkällä.

You could just generate 1 million "followers" by a script. In order to calculate a follower count that makes sense, you need a web of trust, PoW, bitcoin payment or some other spam prevention mechanism. There’s no “accurate” way to do it, the choice of algorithm is up to you.

The block list can be maintained locally, or potentially you could share it publicly or with a group. I don’t know what other nostr devs have in mind.

And you can add / remove relays (but they’re not persisted yet 😄)

Iris -> nostr posting and following also works.

You can now paste note ids (bech32, beginning with “note”) into the iris.to search box. Feed still tbd.

https://iris.to/#/post/note1dj0qyynesqjyv7wgzh77zeesa4fw6u6m7smdycda9qasnmepgnrqse98k3

This place feels like FREEDOM

https://github.com/nostr-protocol/nips/blob/master/02.md

"Every new contact list that gets published overwrites the past ones, so it should contain all entries. Relays and clients SHOULD delete past contact lists as soon as they receive a new one.”

Nostr is an event system. It would be useful to have a state management system on top of it, so changes are merged instead of overwriting.

I think it would be powerful to combine gundb with nostr for that purpose. I originally built iris.to on gundb and I’m now adding nostr.

Cheers! https://iris.to/#/profile/npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m

Added iris.to nostr profile photos via image proxy

You can now paste hex / bech32 nostr public keys into the search box at iris.to, and it will take you to the profile page.

I just added support for #nostr keys and profiles to https://iris.to . If you already have an iris key, a nostr key is derived from it. If you log in with a nostr key, an iris key is derived from it. For now it only syncs your profile, but I'll add posts as well.

In iris.to I've tried to hide as much of cryptography and networking as possible. When you create an account, there's "What's your name?" instead of "generate new keypair". Default peers are used and connectivity is only shown by a small indicator.

In iris.to I’ve been trying to hide everything related to cryptographic keys as much as possible. For new account creation there’s “What’s your name” instead of “Generate new key” etc.

Also relays should probably hidden from places other than settings page, although a small connectivity indicator could be shown.

Hello world!