HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
wallix
PEPS
Python2013–2016
wallix / PEPS

PEPS

Innovative Open source Email + File sharing

5Distinct people
16Mentions
0Explicit recommenders
691GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Innovative Open source Email + File sharing

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:03:16 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 year16 dated mentions

Observed mentions: 2013-11-08 20:40:19 UTC to 2016-11-03 15:14:49 UTC.

0510152013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 14 mentions; 2 submissions, 12 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016

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
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC101
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC14212
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101

What Hacker News says

16 sources
First, we had SquirrelMail and its ilk. Then, Roundcube became the standard. Their dominance is being eroded by Mailpile, RainLoop, and Nylas. Around the edges, we have Peps[1], Mailr[2] & Kite[3] which may all someday take off. Zimbra and the well known groupware vendors (OnlyOffice, Horde, Citadel, Kolab) are competing in more-or-less the same space. Probably dozens of other projects that are on the same level that I have never even heard of. I would love some sort of comparison, even a biased one written by the respective teams. Anyone have useful links? [1] https://github.com/MLstate/PEPS [2] http://pusto.org/en/mailr/ [3] http://khamidou.github.io/kite/
In Nylas N1 – extensible open-source mail client
Thanks for your message. We maintain a roadmap: https://github.com/MLstate/PEPS/wiki/Roadmap Thanks to Opa (possibly due to that fact that we know how to use it at its best), we are able to develop features very quickly. I would say that what we need most is to optimize the UX and little details that matter to refine them over time. But overall, I think we can go technically much farther that Zimbra/Roundcube. But to achieve more popularity, we will need to beef up some marketing aspects!
In The Opa Language
Project creator here (and kind of surprised to see Opa as news). Reading the different comments, I must say that Opa is still active (although we lack resources to animate the community). We are a small French startup meaning that I get to spend 50% of my time struggling with administration, and our evangelism resources are not compatible to those of companies like Meteor (and btw, Opa predates Meteor by a while). Currently, we use Opa to build a secure communication application, named PEPS : https://github.com/MLstate/PEPS which is a good example of a "big" and open source application written in Opa. Note also that bringing a new language (or framework) from toy examples to real apps is definitely not easy. Overall, quite glad to see that many things we introduced in Opa ("JSX" syntax, CPS-transforms, etc.) are becoming more prevalent, e
Read the rest
specially thanks to ES6. Indeed, adapting Opa to ES6, which we are looking at right now, would enable existing applications to use the latest ES6 features without changing the app code. That was one of the goal of the project: Opa was meant to be a "good way" to write applications, letting the compiler choose a target platform and write code for it. Opa is still relevant today, as a "good quality" (especially in terms of safety -- and if you are interested in certified applications like common criteria, please contact me: Opa is relevant in that space) "one-stop shop" to build develop web apps or services. Remind that when we started a few years ago, many were criticizing that we use a functional programming language, were telling us that nobody wants static typing, etc. (that was before Hack which helped a lot in popularizing the feature -- and Opa too is written in OCaml). And Opa has a future. The way the compiler is written, it's not that hard to have it compile the same application code into cloud platforms, including a lot of Amazon Lambdas...
In The Opa Language
It would be very interesting to know, technically, what are the interception means. Does it target phone calls, emails, internal spys, other things? From other documents, it appears that the NSA has the ability to listen to phone calls on French networks. As most of the "targets" use Orange, the historical telecom operator, and that collaboration from Orange with the NSA is unlikely, it would mean that their IT systems are owned. Regarding email, most French companies use Microsoft products both as servers (Exchange) and client (Outlook). Are there exploitable vulnerabilities in these products? As we are in that space, we have to push hard, for people even to consider French-written, open source communication software such as ours (https://github.com/MLstate/PEPS).
In New WikiLeaks Documents Reveal NSA Spied on French Companies
Interesting to read both the article and comments. It's cool to hate Mongo nowadays but we use it successfully (for PEPS, open source: https://github.com/MLstate/PEPS). The version of MongoDb used is not mentioned in the article. The changes between versions is a problem with Mongo but it improved much recently. One problem clearly identified is the lack of model. There are solutions to this. For instance, with Opa (http://opalang.org) we use strong static typing to generate a database model and guarantee that the whole applications sticks to it. That leaves out model changes, but there are solutions for that. Also, there is no need to have the whole collections in RAM, but clearly enough RAM for the "working set" helps. In the end, Mongo is no magic so do SQL databases which have their share of problems too.
In Goodbye MongoDB, Hello PostgreSQL
It's still a bit ahead of launch, but we are preparing an open source alternative to OwnCloud (that also includes messaging platform) that acts as an OAuth server for apps/plugins and an API and does not impose all apps to be implemented in the same language. We are using a NodeJS runtime, but the code is generated using a strongly statically typed language, Opa. Source code is not yet published, will be AGPL. Docker containers: https://github.com/MLstate/PEPS
In OwnCloud Server 8.0
We are asking ourselves the same question. We have developed for a few years a "more than email" server that we have already licensed to one major customer. The open source or not question is one main right now, and until we decide, we have prepared a free to download offer based on Docker. If you're curious: https://github.com/MLstate/PEPS We haven't really launched yet, but think that open sourcing (using for instance the AGPL license) might bring: - more visibility, - more confidence for the customers who would buy support and maintenance instead of licenses, - the opportunity of creating a community (if not on the core product, at least on extensions) - the loss of a few potential customers that would just use the open source version instead of work with us.
In Ask HN: Is it foolish to open source your SAAS business source code?

Showing the 15 most recent of 16 sources. Enable JavaScript to search and browse every indexed mention.

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.