It does

Disambiguating Community Forks

I noticed that people have been linking to nostr communities without including the admin's pubkey in the URL, e.g.

just https://satellite.earth/n/dwadziesciajeden

instead of the full URL https://satellite.earth/n/dwadziesciajeden/npub1xpuz4qerklyck9evtg40wgrthq5rce2mumwuuygnxcg6q02lz9ms275ams

It might seem like a minor issue but I think handling this ambiguity is actually pretty important for UX — subreddit's were useful because you could refer to them by name like "r slash [whatever]" and it was obvious what you had to type into your web browser to get there. On nostr it's trickier because there can be multiple versions of a community, each namespaced to the pubkey of its admin.

To deal with this, I just pushed an update showing a page at the bare URL that lists all the forks of community.

If you're signed in and Satellite detects that you're subscribed to one of the forks, you'll be redirected there automatically.

In a future update I might make it so that non-signed-in users get directed to the most popular fork.

Backend database with a bunch of services to support communities

Yeah me too. These libs didn't exist back into January/February when I wrote most of the core code for handling events and feeds. Relay pool wasn't even a thing yet in nostr-tools. Very impressed with NDK. I'm going to use it for my next greenfield thing.

Added to TODO

Clicking on your profile pic and selecting "Media" from the dropdown menu opens the same page

Yep. A reasonable compromise might be to use an API for certain queries, but encourage clients to implement fail-over behavior so that if an API goes down the client will still work. Obviously not all clients are going to do that, but I think I will probably end up doing that with Satellite sooner or later, especially if/when the problem of impersonator profiles becomes more of a thing and tagging suggestions need to be ranked by some kind of trust score (which would be expensive/hard to compute locally)

It's a general issue because in a pure client ("pure" in the sense that the client is pulling data only from relays) there's no way to match an arbitrary name to an npub without pulling metadata for *everyone*. What I do with Satellite is cache profile metadata that's already loaded for other reasons (e.g. your following list and/or other threads) and use that to populate the dropdown of suggesting when you start typing an npub to tag someone. Admittedly a half-solution, but it mostly works. A proper index of user identities that you could send proper queries would improve UX but it goes against the whole "dumb relay" thing.

Very interested in this, just filled out the form

Notifications are the biggest thing missing right now, I think.

I'm working on rolling that out later this week, in addition to a quote post function and relay management functions as soon as possible.

Are there other features you'd like to see prioritized? Would appreciate your perspective

Noted

Coming in the next update

Oh good, phew!

That’s the subscribe button!

Btw nostr:npub1alpha9l6f7kk08jxfdaxrpqqnd7vwcz6e6cvtattgexjhxr2vrcqk86dsn I implemented the kind 30001 thing so subscribing to communities should be compatible with nostr.kiwi 👍

I’ll look into it thanks!

Satellite Update — Subscribe to communities, unified modqueue, media posts, and more

- Subscribe to Communities: Communities you're subscribed to are marked with a white check mark and appear at the top of the list when you're signed in.

- Unified Modqueue: On Satellite, go to 'Menu' > 'Communities' > 'Pending Approval' to see an aggregated list of pending posts from all the communities you're a moderator of.

- Media Posts: Satellite will now auto-detect and render linked images, video, and audio to improve UX in media-focused communities.

Check it out at https://satellite.earth

More on the way.

Yeah, I was going with a kind 30001 event with a `d` tag "communities" and a list of the `a` tags of the communities that the user is following. That's what you're doing with nostr.kiwi as I understand nostr:npub1alpha9l6f7kk08jxfdaxrpqqnd7vwcz6e6cvtattgexjhxr2vrcqk86dsn ?

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z what do you mean by `k` tag?

Haha well I guess we’re imagining it now

It’s hard to imagine!