# Contact-Lookup Service

**URL:** <https://forum.delta.chat/t/contact-lookup-service/491>\
**Category:** Feature Proposal\
**Created:** [July 12, 2019, 10:27pm UTC](https://forum.delta.chat/t/contact-lookup-service/491 "2019-07-12T22:27:45Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![agschaid](https://forum.delta.chat/user_avatar/forum.delta.chat/agschaid/32/289_2.png) [@agschaid](https://forum.delta.chat/u/agschaid)\
**Post date:** [July 29, 2019, 2:54pm UTC](https://forum.delta.chat/t/contact-lookup-service/491/23 "2019-07-29T14:54:17Z")

</div>

Thank you @testbird for the hint. I think I have tried Jami when it was still called “Ring”.

I haven’t dug to deep but I am afraid they do share my point of view 😉

> As much as we like to say that Jami is completely without server, sometimes it is not exactly right as we have seen.

(From [Establishing peer-to-peer connections with Jami](https://jami.net/establishing-peer-to-peer-connections-with-jami/)).

In the settings there is a bunch of server URLs for various peer discovery techniques. I haven’t found too much about their contact discovery but there is at least [one issue](https://git.jami.net/savoirfairelinux/ring-project/issues/291) that hints a central service.

---

<div class="post-metadata">

**Author:** ![agschaid](https://forum.delta.chat/user_avatar/forum.delta.chat/agschaid/32/289_2.png) [@agschaid](https://forum.delta.chat/u/agschaid)\
**Post date:** [July 29, 2019, 3:01pm UTC](https://forum.delta.chat/t/contact-lookup-service/491/24 "2019-07-29T15:01:06Z")

</div>

From my point of view (as somebody who wants to use DeltaChat as a chat and not alternative mail client) I’d be strongly in favor of giving contacts with a DeltaChat history a different color.

---

<div class="post-metadata">

**Author:** ![Minim](https://forum.delta.chat/letter_avatar_proxy/v4/letter/m/ccd318/32.png) [@Minim](https://forum.delta.chat/u/Minim)\
**Post date:** [July 31, 2025, 9:03pm UTC](https://forum.delta.chat/t/contact-lookup-service/491/25 "2025-07-31T21:03:08Z")

</div>

The Jami setup is just an (optional) keyserver. It is sortof decentralized because it gives you a email-like address, and a keyserver can be run on any domain. I think you can register the same keys on several domains. You type in a person’s email-like address to contact them. Scanning QRs is also an option but I think rarer. Convenience usually trumps security.

It has recently been pointed out that identifying a Chatmail server as such is usually simple. So if someone is using a non-camoflaged Chatmail server, it is easy to tell.

Each Chatmail server could provide an optional keyserver. But I can see good arguements against it.

---

<div class="post-metadata">

**Author:** ![r10s](https://forum.delta.chat/user_avatar/forum.delta.chat/r10s/32/1513_2.png) [@r10s](https://forum.delta.chat/u/r10s)\
**Post date:** [October 5, 2026, 12:14pm UTC](https://forum.delta.chat/t/contact-lookup-service/491/26 "2026-10-05T12:14:13Z")

</div>

closing stale issue.

meanwhile, the contacts do not have a binding to an address any longer, so that a contact lookup service as suggested above does not make that much sense

---

<div class="post-metadata">

**Author:** ![r10s](https://forum.delta.chat/user_avatar/forum.delta.chat/r10s/32/1513_2.png) [@r10s](https://forum.delta.chat/u/r10s)\
**Post date:** [October 5, 2026, 12:14pm UTC](https://forum.delta.chat/t/contact-lookup-service/491/27 "2026-10-05T12:14:19Z")

</div>



[Previous page](https://forum.delta.chat/t/contact-lookup-service/491.md?page=1)
