Opened 7 years ago

Closed 4 years ago

#1290 closed enhancement (wontfix)

Add priorities for addressbook sources

Reported by: bird Owned by:
Priority: minor Milestone:
Component: apps/addressbook Version:
Keywords: usability Cc:
Parent Tickets: Sensitive: no

Description (last modified by str4d)

I had the idea to add priorities to the different addressbook sources.

Rank 1: the default addressbook
Rank 2: Addressbooks which are run by known and trusted community members
Rank 3: unknown or uncommon addressbooks

If for example the default addressbook report a different address than the other addressbooks for domain X, the user gets warned about the conflict so the user can decide.

This feature can improve the security by decreasing the easiness of spreading wrong addresses for domains and by warning the user about suspect cases.


Change History (3)

comment:1 Changed 7 years ago by zzz

Status: newinfoneeded_new

I don't understand what you're asking for. DNS resolution is not under the control of I2P or any other application, it's set by the OS / libs (i.e. libc). There's nothing we can do to change it.

comment:2 Changed 6 years ago by str4d

Component: unspecifiedapps/addressbook
Description: modified (diff)
Keywords: usability added
Milestone: 0.9.14
Status: infoneeded_newnew
Summary: add priorities for domain lookup sourcesAdd priorities for addressbook sources
Type: defectenhancement

I think by "DNS" they mean "addressbook" and/or "SusiDNS". Since the OP has no email address set and will likely never respond, I am going to assume that is what they meant and adjust the ticket accordingly.

comment:3 Changed 4 years ago by zzz

Resolution: wontfix
Status: newclosed

The way we do it is, first one wins. We don't have any easy way to note a subsequent conflict, store the conflict details, and present them to the user later in the web UI for conflict resolution. str4d added keyword 'usability' but I think this would be a usability nightmare to implement.

Somehow specifying that we trust some subscriptions more than others is tricky. GNS or some other signed naming system might be more applicable.

Proposals 112 (subscription feed enhancements) and 135 (signed address helpers) may also make this ticket less necessary. http://i2p-projekt.i2p/spec/proposals

Realistically, we aren't going to do this.

Note: See TracTickets for help on using tickets.