HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
erthink
ReOpenLDAP
C2018–2019
erthink / ReOpenLDAP

ReOpenLDAP

Production-ready replacement for OpenLDAP with robust multi-master replication (MegaFon).

2Distinct people
4Mentions
0Explicit recommenders
263GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Production-ready replacement for OpenLDAP with robust multi-master replication (MegaFon).

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month4 dated mentions

Observed mentions: 2018-08-28 20:02:13 UTC to 2019-04-18 21:20:57 UTC.

012018-08-01 00:00:00 UTC to 2018-09-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 20182018-09-01 00:00:00 UTC to 2018-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-01 00:00:00 UTC to 2018-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-11-01 00:00:00 UTC to 2018-12-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2018-12-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 20182019-01-01 00:00:00 UTC to 2019-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-02-01 00:00:00 UTC to 2019-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-01 00:00:00 UTC to 2019-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-01 00:00:00 UTC to 2019-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 2019

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 20182018-08-01 00:00:00 UTC2018-09-01 00:00:00 UTC101
Sep 20182018-09-01 00:00:00 UTC2018-10-01 00:00:00 UTC000
Oct 20182018-10-01 00:00:00 UTC2018-11-01 00:00:00 UTC000
Nov 20182018-11-01 00:00:00 UTC2018-12-01 00:00:00 UTC110
Dec 20182018-12-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
Jan 20192019-01-01 00:00:00 UTC2019-02-01 00:00:00 UTC000
Feb 20192019-02-01 00:00:00 UTC2019-03-01 00:00:00 UTC000
Mar 20192019-03-01 00:00:00 UTC2019-04-01 00:00:00 UTC000
Apr 20192019-04-01 00:00:00 UTC2019-05-01 00:00:00 UTC101

What Hacker News says

4 sources
In my opinion, the solution isn't to initially replace the messaging platform. Rather, user metadata management first and foremost must be addressed. There needs to be a way for people to have something like OpenLDAP+SAML that is federated. User metadata can then be used on whatever shiny app is cool at the time. Messaging platforms come and go, but the people are what remain fairly constant. Applying this logic also means you can give people multiple options and use the same logins on multiple applications. If I were to take a first stab at this, I would probably use something like the OpenLDAP fork ReOpenLDAP [1] and use my domains and my friends domains to set up master-master replication. Each domain owner is master for their domain. I have no idea what saml2 provider I would put in front of it. This system would store password
Read the rest
hashes, ssh public keys, contact information, bio (used for signatures and "about me" boxes). There should be a combination of web API's and a web UI to self service account info so that anyone can maintain, update or otherwise remove their data when they want. [1] - https://github.com/leo-yuriev/ReOpenLDAP
In Time to #DeleteFacebook, Again

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.