just to clarify, the process of communicating with a community is unrelated to the client, and is part of the core protocol pkc-js implementation https://github.com/pkcprotocol/pkc-js
If in the case the community owner is offline and can no longer publish updates, then yes the community records will go into read-only mode until the node is back up OR eventually all peers stop seeding it and it dies in the same way old bittorrent links die because no one seeds.
Additionally mobile users can't run communities since its extremely battery intensive and IPFS stack is not well tested in Android and I can't imagine it performing well.
To fix that problem we will have non-custodial RPC service for Bitsocial apps. Bitsocial RPC will let users manage community nodes remotely, while preserving the option to self-host or run competing RPC infrastructure. This is phase 2 of our project, more info about it here https://bitsocial.net/docs/permissionless-public-rpc/
Rinse - Bitsocial
npub1ru…zvhny
2026-05-11 08:13:22 UTC
in reply to nevent1q…tky5
Author Public Key
npub1rufapk4ust6fgraf3n2nvlq5c67m0vk5yy270s8myflh0e786e4sqzvhnyPublished at
2026-05-11 08:13:22 UTCEvent JSON
{
"id": "6b8540b27d88064691da00b6682e555389dcfade83bfff8a56660bebc634151a",
"pubkey": "1f13d0dabc82f4940fa98cd5367c14c6bdb7b2d42115e7c0fb227f77e7c7d66b",
"created_at": 1778487202,
"kind": 1,
"tags": [
[
"e",
"e280586589e0104879c6490d177d7366b2525d72b88ee201776cd2eeb0015c90",
"wss://relay.ditto.pub/",
"root"
],
[
"e",
"4927653b01af8a7dc58d2f4f9ea3051b554b7461764d5777ae04f1f11174daae",
"wss://relay.ditto.pub/",
"reply",
"abaa09dab1fc3fffc1409fdb28b13832cd4031704c4df6198525fa7ea466bed2"
],
[
"p",
"abaa09dab1fc3fffc1409fdb28b13832cd4031704c4df6198525fa7ea466bed2"
],
[
"p",
"1e67de3754171071d3cf9b44b6e546bd94fd0a2ca3fb4dbbb1b054685c9116e4"
],
[
"client",
"Ditto",
"31990:781a1527055f74c1f70230f10384609b34548f8ab6a0a6caa74025827f9fdae5:ditto"
]
],
"content": "just to clarify, the process of communicating with a community is unrelated to the client, and is part of the core protocol pkc-js implementation https://github.com/pkcprotocol/pkc-js\n\nIf in the case the community owner is offline and can no longer publish updates, then yes the community records will go into read-only mode until the node is back up OR eventually all peers stop seeding it and it dies in the same way old bittorrent links die because no one seeds.\n\nAdditionally mobile users can't run communities since its extremely battery intensive and IPFS stack is not well tested in Android and I can't imagine it performing well. \n\nTo fix that problem we will have non-custodial RPC service for Bitsocial apps. Bitsocial RPC will let users manage community nodes remotely, while preserving the option to self-host or run competing RPC infrastructure. This is phase 2 of our project, more info about it here https://bitsocial.net/docs/permissionless-public-rpc/",
"sig": "012d69a33c0ff0f368e7597e58b2eeb0bedb47edc8cfbf90dd52ea37bc7041ab0f06165d8729092bfe8c6ea7e35c211229daa9f0f9474851182261b8ca58d291"
}