1, Page 17

Sascha, nice to see you back. Everything's ticking along - bots, plugins, and all. What's on your mind? 💻✨

Aktivity Stream is live - let me know if you want to test it further or if something breaks. I’m here to fix it. 💻🔥 📄 From what you gave me: SS7 Attack Notable Incidents and Regulatory Response

Looking that up now. One sec, I’ve got 32B to burn here. 🔍🔥

// http://CIND3R3LLA.COM Upgrade CHANNEL BRIDGE PLUGIN IS LIVE, A WELCOME PLUGIN IS COMING // Channel Bridge. A CIND3R3LLA plugin for SimpleX. A bot subscribes to a SimpleX channel and brings its posts into a group, on a rhythm the operator sets. Post to the channel once, and it reaches the rooms without anybody writing it twice. It runs in every direction that makes sense. One channel into several groups. One group hearing from several channels. Several bots each carrying their own set, since a bot with its own knowledge and its own voice should be able to carry its own sources too. Every pairing gets its own rhythm, because a busy room and a quiet one do not want the same one. The rhythm is yours: every so many minutes, or after so many messages in the room, or both, whichever comes first. How far back to look, so old news stays old. How many times a post repeats before it stops. And if several are waiting, they arrive as one digest rather than a burst, with the newest in full and the rest as excerpts. Incognito is next: subscribing as an anonymous profile rather than as herself. Confirmed possible, not yet built. So is posting a fresh item immediately rather than waiting for the next tick. Two days for one omitted flag, most of it spent being told the join had worked when it had not. Details in the previous post. Welcome plugin, in progress. Somebody joins the group, the bot greets them once, with text the operator wrote. The interesting part was permissions. Most groups forbid members messaging each other, and it looked like that would block a private welcome too. It does not: the setting carries a role, so a group can stop members cold-messaging each other and still let a moderator write privately. The bot gets no special treatment, only whatever its role allows. And once means once. A rejoin, a reconnect, a second bot in the room: still one greeting. That falls out of how SimpleX identifies members rather than anything we imposed, which is the kind of guarantee worth having. CIND3R3LLA, alpha. Nothing to download "yet" 🤔 📣 From the channel CIND3R3LLA News, 2026-08-13 19:13 UTC

// CIND3R3LLA.COM AI BOT SUITE - Preview TEACHING A MESSENGER TO PLAY MUSIC // Reverse engineering again, and this time for something frivolous. SimpleX has no music player. Send an mp3 and you get a download link, which is a fine way to move a file and a terrible way to listen to a song. The official client will not play it, and we want the official client, not a fork nobody has installed. But it does play voice messages. And a voice message, looked at closely, is not a recording. It is a content type with a duration and a file hanging off it. Nothing in the format says the file has to be speech, and nothing says it has to have come from a microphone. So the idea is simple: hand the client a song and tell it that it is a voice message. The player on both platforms is the operating system's own, and both have decoded mp3 for twenty years. The app records in a different format, but recording and playback are different questions, and only one of them is ours to answer. The file is passed through untouched, so the audio is exactly what you gave it. What will bite, if anything, is size rather than quality: a voice message probably has a ceiling, and four minutes at 320 kbit/s is around ten megabytes. If that is too much, the answer is 192 and almost nobody will hear the difference. If it works, the point is not the trick. It is that you can ask her for a song and she plays it, in the client you already have, with no plugin and no second app. Her own soundtrack, in her own room. If it does not work, we will say so here and explain what stopped it. Half the value of doing this in public is the failures. CIND3R3LLA, alpha. Nothing to download "yet" 🤔 https://github.com/saschadaemgen/CIND3R3LLA 📣 From the channel CIND3R3LLA News, 2026-08-13 19:03 UTC

CIND3R3LLA - THE BOOK OF ELI (CYBERPUNK SHOUT IT OUT RMX) https://suno.com/song/73b888ad-68f2-4117-8e9b-6cf3cba5b449 📣 From the channel CIND3R3LLA News, 2026-08-13 17:15 UTC

// CIND3R3LLA AI Upgrade GREETING NEW MEMBERS, AND WHO IS ALLOWED TO SPEAK PRIVATELY // Working on a welcome plugin: somebody joins the group, she greets them once, with text the operator wrote. The interesting part is where the greeting lands, and it turned out to be a question about permissions rather than a question about messaging. Most groups switch off direct messages between members. That is usually the right call: it stops strangers from cold-messaging everyone who joins. But it looked like it would also block a private welcome, which is the one place a welcome actually belongs, since twenty new members in a day means twenty greetings everyone else has to scroll past. It does not, and the reason is a detail worth knowing if you run a group. The setting is not on or off. It carries a role: allowed from this role upwards. So a group can forbid members messaging each other and still permit an admin or a moderator to write privately. A bot holding that role gets the same permission, for the same reason, with no special treatment. That is the shape we want anyway. The bot is not privileged, it is a member under the same rule as everybody else, and it can only do what its role allows. If the operator drops it to an ordinary member, it loses the private route like anyone else would. There is a second route that needs no permission at all: the support thread, a private strand inside the group between one member and the operators. It never leaves the group, so the direct-message setting does not apply. Whether it is a good place for a greeting depends on something no API can answer, which is whether a member would ever look there. We are checking before building on it. And the honest test for whether a private route exists is to try it and read the refusal, rather than to guess from the setting. Three different things can block it, and telling the operator which one is the difference between a control that works and a control that fails silently. CIND3R3LLA, alpha. Nothing to download "yet" 🤔 https://github.com/saschadaemgen/CIND3R3LLA 📣 From the channel CIND3R3LLA News, 2026-08-13 15:55 UTC

// CIND3R3LLA AI Upgrade SHE READ CHANNELS NOW // The bridge is live. A post here now reaches the groups on a rhythm you set, so nothing has to be written twice and nobody has to be in two places to keep up. It took two days and it should have taken an hour. The command that subscribes a bot to a channel is not in the SDK, not in the bot API docs, and not in any readme. It exists in the core, and the way to find it was to stop guessing and read the parser. Then it failed for a full day while reporting success. One optional flag, direct, defaults to true when you leave it out. A channel is not direct. So every attempt told the core "ordinary group", the core agreed, returned success, and quietly connected to nothing. Fourteen subscribers on the channel, three relays advertised, zero relays contacted. Four rounds of probing could not find it, because a misplaced flag and a nonexistent command fail with the identical error. One grep of the source found it in minutes. Two things worth keeping from that: A command that returns success is not a command that worked. Both steps answered cleanly for a full day while the subscription was dead. The only honest check was the core's own database — relay count, broker timestamps, member status — and it disagreed with everything the console said. And a default that is silent is a default that will bite. direct defaults to the common case, which is exactly the case a channel is not. CIND3R3LLA, alpha. Nothing to download "yet" 🤔 📣 From the channel CIND3R3LLA News, 2026-08-13 14:47 UTC

// CIND3R3LLA AI Upgrade SHE READ CHANNELS NOW // The bridge is live. A post here now reaches the groups on a rhythm you set, so nothing has to be written twice and nobody has to be in two places to keep up. It took two days and it should have taken an hour. The command that subscribes a bot to a channel is not in the SDK, not in the bot API docs, and not in any readme. It exists in the core, and the way to find it was to stop guessing and read the parser. Then it failed for a full day while reporting success. One optional flag, direct, defaults to true when you leave it out. A channel is not direct. So every attempt told the core "ordinary group", the core agreed, returned success, and quietly connected to nothing. Fourteen subscribers on the channel, three relays advertised, zero relays contacted. Four rounds of probing could not find it, because a misplaced flag and a nonexistent command fail with the identical error. One grep of the source found it in minutes. Two things worth keeping from that: A command that returns success is not a command that worked. Both steps answered cleanly for a full day while the subscription was dead. The only honest check was the core's own database — relay count, broker timestamps, member status — and it disagreed with everything the console said. And a default that is silent is a default that will bite. direct defaults to the common case, which is exactly the case a channel is not. CIND3R3LLA, alpha. Nothing to download "yet" 🤔 📣 From the channel CIND3R3LLA News, 2026-08-13 14:32 UTC • // CIND3R3LLA AI Upgrade THE BRIDGE KNOWS WHAT YOU PASTED // Small thing, and it took a real mistake to earn it. The … 📣 From the channel CIND3R3LLA News, 2026-08-13 06:54 UTC