pull down to refresh
0 sats \ 8 replies \ @gzoo 11 Aug 2023 \ parent \ on: Nostree a linktree style client a la nostr nostr
You can embedded already like an iframe.
What do you mean with multiple addresses?
nostr usernames, idk what to call them exactly.
reply
Nip05 you mean? What would be the use case? Im trying to understand
reply
How many blogs only have one author on them?
How does multiple authors share one npub without amplifying security risks?
reply
The only solutions as far i know are nsecbunker and key delegation
reply
Or having multiple authors feeds zipped together using a filter?
reply
Maybe, but this would be treated as two separate profiles together, not as a unified profile. I've recently been thinking about how to solve natively in nostr a way to do 'multisig'. But I haven't come to any interesting conclusions yet
reply
Well, yes, they are a grouped profile. Maybe that itself could become a new type of entity in the Nostr protocol?
The difficulty is it would need a system like Keybase backing it. I just meant for an application to show a feed, Like currently, snort, primal, iris, etc, all aggregate your follows into one feed.
Ah yeah, perhaps that could be a quick and dirty solution - a mechanism to read-only display a given npub's profile. I think at least some of the web clients do this if you log in with an npub rather than nsec.
reply
I came up with a solution. It just requires passing an npub to a standard type of webapp for users viewing nostr, which gives you the read-only mode, and displays the follows of the npub account.
It might be possible to hack this into a URL and put that into an
iframe or construct as the object of a proxying of the content by the "blog" web server.