valeriansaliou

I’m working on Prose, a lightweight XMPP team messaging app that can work as a Discord replacement. There’s no calls for the moment and OMEMO support is on the works but everything else is working great and pretty mature.

Lightweight macOS app / Windows running with Tauri are available and they feel native. But it’s also a Web app that can run on any domain.

Available at prose.org and https://github.com/prose-im/prose-app-web

This resembles how I monitor all infrastructure I run. One of them has 150 small independent VMs, for which I had to build a custom micro service monitoring open source tool that I still use to this day: https://github.com/valeriansaliou/vigil

There’s no certificate expiration monitoring just yet, but everything else is there: poll probes (active ICMP or TCP probes), push probes (reporting HTTP API for apps), and local probes (reporting HTTP API for sub-Vigil for firewalled infrastructure parts).

This opens up a market for someone building a Slack app and putting it on the Slack marketplace, that would relay in/out messages from/to XMPP o IRC. I'd pay for this, I definitely don't want to use Slack from their Electron app that sucks both my battery and my RAM. I'd stick with Adium as an XMPP client connected to Slack.

Notes:

---

Vigil is an open-source Status Page built in Rust that you can host on your infrastructure. You can use it to monitor all your servers and apps, and get a Web Status Page visible to your users (ie. on a domain of your choice, eg. status.example.com).

It is useful in microservices contexts to monitor both apps and backends. If a node goes down in your infrastructure, you receive a status change notification in a Slack channel (eg. #infrastructure). Your phone / watch / etc. will ping you when something goes wrong, or when the infrastructure auto-recovered from downtime).

Vigil is usually used in a SaaS context to monitor tens of services, but it can also prove useful to monitor services on eg. a personal server, or monitor a small infrastructure made of APIs.

---

This is an open-source version of https://status.crisp.chat/ which we've been running over the last 2 years. It saved our service from small to large downtimes hundreds of time. This is why we're now releasing it as Open Source, as most SaaS starting up won't need to use a complex, expensive commercial solution while a self-hosted app would do.

This is part of our effort to give back to the OSS community. Hope this can help :)

We're open to feedbacks & feature requests.

Crisp does that, and is able to integrate with Slack to reply to visitors - in addition to its Web dashboard.

Website: https://crisp.im/

Disclosure: I am the co-founder.

Bug fixed. Email event processing was delayed yesterday, emails should have be dispatched a few hours back ago.

Can you retry now? We had some event processing delays due to our growth.

Thanks, we'll look into it to fix it! :)

Hi! We're still early in the product, mobile apps are in beta ATM, we're working on native versions for them, current versions are just transitional versions.

Hey! Which way? Email notification for an unread message from visitor to operator after 1 minute, if visitor doesn't leave his email, is that right?

Hello! We're running NodeJS (ECMAScript 6), RabbitMQ and Redis at the core of our infrastructure. The whole thing is split into micro-components (eg: a worker dedicated to emails, another to client-side websocket, another to messages, etc).