Message-first social client

Yurumeet

A quieter inbox for the same self-hosted social server. Keep your actor, communities, and ActivityPub identity; change only the client.

Start with Yurumeet Read the contract

Client

Conversation first, feed optional.

Yurumeet uses the short client id yurume. It opens the same DMs and community chats exposed by yurucommu-server, but keeps the first screen focused on messages. On a standalone domain, the client asks for the server URL or reads it from ?server=.

Yurumeet app connection screen asking for a social server URL
Shared identity

Sign in with the same server account and keep the same ActivityPub actor.

Requests built in

Message requests stay separate until you reply, matching the server's direct-addressed Note model.

Groups included

Community chats sit beside people, with filters for a compact inbox.

Server

One server, separate clients.

The backend is still yurucommu-server. Takosumi wires normal Capsule outputs and records runs; Yurumeet stays a separate client surface.

1

Install yurucommu-server

The server exposes social API, ActivityPub, media, and push registration outputs.

2

Connect Yurumeet

The client consumes the server's well-known discovery and output values.

3

Keep the same network

Followers, DMs, communities, and federation remain server owned. 

{
  "server": "yurucommu-server",
  "client": "yurume",
  "brand": "Yurumeet",
  "entry": "messages",
  "uses": [
    "api.social.v1",
    "activitypub.server.v1"
  ]
}

Install

Ship it as a normal client surface.

Yurumeet lives beside Yurucommu, not inside Takos core. A host can run the product site at yurumeet.com, serve the app client from app.yurumeet.com, and point it at a compatible yurucommu-server.

Yurucommu Source