Search Results for "delivery"

...It helps developers avoid writing separate integrations for every SMS gateway their application may need. The package uses configurable gateways, strategies, messages, and phone number handling to make SMS delivery easier to manage. It is especially useful in applications that need verification codes, alerts, notifications, transactional messages, or fallback delivery across providers. The project is installed through Composer and is part of Overtrue’s broader PHP ecosystem. It is aimed at developers who want a practical abstraction layer for multi-channel SMS delivery in PHP applications.

Sideband is a privacy-focused, peer-to-peer mesh messaging protocol and platform that allows users to communicate directly over local networks or the internet without servers. It emphasizes metadata resistance and secure message delivery, working effectively in offline, low-bandwidth, or disaster recovery scenarios. Built-in Rust, Sideband supports encrypted group messaging, file transfers, and network self-discovery. It is ideal for use in community networks, crisis response, and decentralized communications infrastructure.

...Although cryptographic operations and message confidentiality are managed by the client side using the Signal Protocol, the server ensures message routing, user registration, and group updates without having access to the decrypted contents. Its codebase is public to ensure transparency and auditability for a security-focused community willing to inspect how message metadata and delivery mechanisms are implemented.

Dino is a modern, secure, and user-friendly XMPP (Jabber) chat client designed for desktop systems. It aims to provide a polished experience for private and group messaging, with a focus on privacy, end-to-end encryption, and federated communication. Unlike centralized chat platforms, Dino supports standard XMPP servers and integrates features like OMEMO encryption, media sharing, and modern chat UX patterns. It’s written in GTK and optimized for Linux environments, making it a solid choice...

NSQ is a realtime distributed messaging platform that is designed to scale, and can even handle billions of messages daily. It promotes distributed and decentralized topologies, allowing it high availability and fault tolerance along with guaranteed reliable message delivery. NSQ scales horizontally and is easy to configure and deploy. It is agnostic to data format, so messages can be in JSON, MsgPack, Protocol Buffers, or anything else. Official Go and Python libraries are available, and so are many other community-supported libraries. Binary releases are published for Linux, freebsd, darwin and Windows as well as an official Docker image.

A lightweight Redis-backed message queue for handling simple distributed messaging and job processing.

Continuation of LAN Messenger by kballen.

Ccnet is a platform for developing P2P collaboration applications, for example, a decentralized '''google docs'''. It provides basic P2P services such as peer management, group management, message delivery in the form of a daemon processor.

LAN Messenger is a decentralized UDP IM-style chat client which supports usernames, guaranteed-delivery IMs, broadcast chat, encryption, file transfer, simple UI, persistent settings, and IP blocking.

This project enables a user to Send SMS via internet using servers of goyali.com.Now the users do not need to type onto the small keypad of mobile. Also this sollution is cost effective. Also the user will receive the delivery report for every SMS sent

Mail Hail is a mail notification agent for the Jabber instant messaging server. Mail Hail includes Hailbox, an experimental local mail delivery agent.

Yet Another Chat Server. A Chat Server written in C++ and designed for speed, flexibility, and all-html delivery. Server oriented code.

The client and the server for chat via LAN. Advantages: the simplified protocol, low consumption of traffic, realization of server-side history and systems of reports on delivery of messages.

FluxyChat is a multi-tenant realtime chat API built on Cloudflare Workers, Durable Objects, and D1. What's different: - One Durable Object per room: WebSocket fan-out + ordering at the edge, no socket fleet to manage - Agent tool calls stream on the same room WebSocket as chat messages — debuggable in the operator console - MIT self-host on your own Cloudflare account, or use the hosted beta - Next.js operator console: rooms, agents, billing hooks out of the box - @fluxy-chat/sdk:...