#[4] hates it, tho. Don't mention it around him. ๐Ÿ˜‚

Reply to this note

Please Login to reply.

Discussion

Hate is probably not the right emotion ๐Ÿ™‚. Heโ€™s mostly very nice.

Well, he says it's centralized bullshit, but I want to host an instance of it. I think it's brilliant. And so pretty! ๐Ÿคฉ

I always link to njump, if I can. Then people can just look at it there and decide if the want to jump into a websocket client from there.

You could use it to read eBooks and Wiki pages.

And you can use it to see something in Nostr while using the German Internet speed. ๐Ÿ˜‚

Any clients that have a "share" via njump, perhaps a setting can be used to supply the specific instance of njump you want to use.

+1 for sure. But assume we now make a standard for HTML clients? Where do we discover URLs and so on?

I was hoping you would tell us where. ๐Ÿคญ

lol. I suppose we could do it like other client's have been using nip05 and nip89 to store cache urls and CORS proxy stuff? User's can set urls they want to us?

But I suppose this is only shorthand for users wanting to share links, not for user's grazing the public internet. When I share links I try to use embed links so we don't have hardcoded urls everywhere. We can't really avoid that though.

We just got our own WikiNostr instance, too! ๐Ÿคฉ

Iโ€™m not interested in open graph and consorts. I donโ€™t think the embedding-tweets case is interesting enough. My main use-case is quoting in a matter which is as decay-proof as linking to Wikipedia or to the Web Archive, preferrably even better. Like referencing books, but with easy access to the library, where the relay is to be named for retrieval of the note.

Do you know how conventional physical libraries handle this? There are catalogues, interchange and archives. Censorship is difficult once the book has been printed.

Same with film infrastructure. One cinema will for sure play the film. Itโ€™s just not easy to access for everyone, whereas nostr should provide exactly this.