Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds Topical Notes #1180

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

vitorpamplona
Copy link
Collaborator

@vitorpamplona vitorpamplona commented Apr 16, 2024

The goal here is to create Notes that are only displayed if you follow certain topics from certain relays.

With this, users can post into their City's relays or into a Hashtag's relays without polluting their main feed.

Solves #1170

Read here

@staab
Copy link
Member

staab commented Apr 16, 2024

Check to make sure those kinds aren't used anywhere else, they seem pretty likely to have already been nabbed. Also potentially of concern is location privacy, this pretty thoroughly doxxes users who use this feature, maybe @arkin0x has thought about that.

Otherwise, I think this is a really interesting idea. It pushes for de-commodification of relays, since if relays don't establish whether they support these events for a given topic/location, any popular tag will ultimately have 30021 events on all relays. I'll be interested to see how this works out.

@vitorpamplona
Copy link
Collaborator Author

Check to make sure those kinds aren't used anywhere else

Yep, they seem to be clean. I have a little crawler that hits every single visible relay for this: https://crawler.amethyst.social/. There is no kind 21 event out there. Kind 30021 has a total of 9 events that look like tests from June last year.

@vitorpamplona
Copy link
Collaborator Author

vitorpamplona commented Apr 16, 2024

Also potentially of concern is location privacy

On the privacy question, we could use random d-tags (UUID) with the following topic declared in the encrypted part. Maybe that is even better because it allows the user to follow many tags/labels (different spellings, languages, etc) for the same "topic".

@staab
Copy link
Member

staab commented Apr 16, 2024

Sure, but that wouldn't solve privacy problems for publishers of kind 21s. The only way to do that would be to encrypt the note for desired recipients. Obviously not feasible on an individual basis, so it would require some kind of key exchange. I don't know if we need that for this to be useful, I just know that I personally would not publish a kind 21 with a g tag.

@vitorpamplona
Copy link
Collaborator Author

vitorpamplona commented Apr 16, 2024

ohh I see. Yes, these are for the folks that want to make public events. Topic-based private discussions need another scheme.

Although the g tag means they are interested in a location or that the post was for a location. It might not necessarily mean that they are based on that location. Of course, the tag's multi-resolution options also help to not pinpoint somebody's exact location with high precision.

54.md Show resolved Hide resolved
54.md Outdated Show resolved Hide resolved
@arkin0x
Copy link
Contributor

arkin0x commented Apr 16, 2024

This is cool!

So, is the g tag required for usage of topics, or is it only required if you choose to subscribe to a place? IMHO this seems useful even if people don't use the location aspect.

I'm not sure how useful the g tag actually is because you could also just make the topic "#newyork" and that would probably be more intuitive than picking the geohash containing New York. The interface a client uses to select the topic tags would need a map interface for the g tag stuff and it could be fairly unintuitive to the pleb who doesn't already understand geohashes.

I'm not against the g tag being part of this because it's a cool idea but I think that if you want to see what people are posting via geohash it's easier to query the g tag for kind1 notes.

To address @staab 's question, subscribing to a g topic indicates your interest in an area; typically this would mean you live there or someone you know lives there. I think the key is to make people aware of this with good UI and let them make informed decisions, and also limiting the precision of the g tags in the client so that people don't accidentally subscribe to a place that is too specific. Geohashes with a length of 5 is my personal maximum for location-sharing comfort zone for accuracy; I only allow 1-5 in Yondar. (Higher means more precise which means less privacy.)

@mterenzio
Copy link

mterenzio commented Apr 16, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants