1 — Page 5

non public

😴😂

I’ve got a suggestion for you 😉 Once we start using our local AI in the chat and it learns user behavior and recognizes regular users, you could ask her if you’re allowed to join her evil sister’s group.

Cinderella is really cool, but I’d honestly love to see what Anastasia can actually do. Unfortunately, there are only rumors, and apparently I’m not cool enough to get into the other group lol.

Cindy?

shes right ^^

nothing xD

and in USD?

Cinderella what is the Price of 100000000 WPLS in BTC?

Cinderella Hilfe

Help

Cinderella Hilfe

join Cinderella AI Chat Bot Suite - the most "advanced" chat tool 4 SMP & MATRIX! https://smp15.simplex.im/g#O6P1s2earUQKND1Gdn4-g8objkdMyhQXS1Ba8hxQzNA

• https://smp15.simplex.im/g#O6P1s2earUQKND1Gdn4-g8objkdMyhQXS1Ba8hxQzNA

Cinderella: hardening, and a short pause on feature updates ☕ (Less visible work this round, and more of the kind that matters) A privacy fix worth disclosing. SimpleX groups have a private thread between a member and the admins, separate from the public conversation. We found that those private messages arrived through the same event as ordinary group messages, and nothing in the capture pipeline distinguished them. Two had already been captured. Neither was ever published, and both have been deleted. The fix is a whitelist rather than a filter: only what is provably a public group message reaches the archive, and anything else fails closed, including message types that do not exist yet. A missing archive entry is recoverable. A published private conversation is not. An audit of silent failure. Several problems this month shared one shape: an error caught, converted into a state that looked ordinary, and nobody told. A dead API key that read as no key. Images withheld with no error. So we went looking on purpose, classified all 114 caught errors in the codebase, and found nine real cases where something could fail invisibly. The worst was on the consent path. If deleting a member's message in the group failed, the error went to a log file and the archive kept the message published. Cross-referencing production showed it has never actually happened, all six group deletions applied correctly, but it was possible from the day the code was written. A failed deletion is now retried automatically until it succeeds or an operator is told. Video links play in the archive. A YouTube link renders as a card you can play in place. Nothing loads from any third party until you click: the thumbnail is fetched once server-side and served from our own domain, so opening the archive produces no external requests at all. Groundwork for what comes next. There is now a durable job queue underneath everything. Unglamorous, but it is what makes automatic categorisation possible without background work blocking the bot. Measured with two thousand jobs queued, an interactive reply is claimed in the same time as with an empty queue. Alongside it, a write-ahead log for incoming events. SimpleX delivers each event exactly once and never re-sends it, so a handler that fails loses that message permanently, with no record it existed. Recording events before processing them makes that recoverable. It also explains the sixteen failed file receipts that have been flagged since the early days: file events were recorded but never retried, and the relays expire files after about forty eight hours. Next two days: the local AI. We are standing up the self-hosted model that will drive categorisation and the media gallery, running on our own hardware rather than a third-party API, so conversations never leave infrastructure we control. That work happens off to the side, so expect fewer updates here until it is running. Normal service resumes after. https://github.com/saschadaemgen/cinderella

• https://github.com/saschadaemgen/cinderella

nice one

SimpleGo @ Carvilon Intercom

good morning, We have deleted the SimpleX group due to a lack of interest and, above all, a lack of understanding of what a public group is for. In CyberDesk we use, among other things, the technology of SimpleGo, in a way that lets you make meaningful use of anonymized and metadata-resistant IoT and microcontroller communication with SimpleGo over SMP, all within a user interface in cyber style. In our latest plugin we are building the SMP protocol into a logic editor, so that you can simply connect to your IoT setup via SimpleX or SimpleGo. One example we have just integrated is a video intercom system, where functions such as opening the door run over SMP. This has the advantage that malicious attackers or ad trackers, which might for instance be lurking in an infected application on a mobile phone, or Google for that matter, have no chance of finding out which door was opened. That is of course an advantage for the security industry. And furthermore, the general interest within the SimpleX community in secure encrypted communication via hardware devices was unfortunately minimal to nonexistent.

Cinderella please help me

nice

YT Stream Test https://www.youtube.com/watch?v=oBDX_dPvq4A

The terrifying reality of Wi-Fi sensing ▶ Playing loads content from YouTube. Open on YouTube →

Cinderella: what shipped, and what is next A technical update since the last one. She has a proper help command. Ask in any phrasing, in English or German, or send /help. The capability list is generated from the active intent catalog rather than written by hand, so disabling a plugin removes it from the help text automatically and a new plugin appears without anyone editing anything. help consent and help prices give topic detail. Building that surfaced a resolver collision worth mentioning: help consent was resolving to a price lookup, because help reads as a plausible asset ticker and scored higher than the help intent. Fixed by forcing an instruction that literally begins with help to the help intent, rather than weakening the price resolver and causing a different problem elsewhere. The consent wording now states the terms before you agree, not after. Three properties, all in the prompt: publication is forward only, so nothing you said before opting in is ever included. It stays public until you take it back. And taking it back is final, all at once, with no way to restore it afterwards. Opting in again later starts fresh from that moment. That last property was not previously stated, and it is the one people would not expect. Your questions are archived alongside her answers. Until recently, any message the interaction layer processed as an instruction was never stored at all, so the public archive showed her answers with the questions missing. She appeared to be answering nobody. Question and answer are now treated as a pair: an answer is published only if its question is, and revoking removes both halves. Consent commands themselves stay out, since they are plumbing rather than conversation. Price lookups, on a plugin framework. Ask her what something is worth, or convert between two assets, in natural language. Three data providers behind one interface with automatic failover, attribution bound to whichever provider actually answered, and symbol-to-asset mappings resolved once and then pinned permanently rather than re-resolved on every request. That pinning matters more than it sounds. Provider search rankings shift, so re-resolving each time means the same question can quietly return a different token's price on a later day. One case in particular: Ethereum HEX and PulseChain HEX share an identical contract address, because PulseChain is a state fork. An address-only lookup returns a roughly 2.4x wrong price with no error at all. The plugin framework is the more durable part. A disabled plugin does not merely go quiet, it leaves the intent catalog entirely, so nothing can resolve to a capability that is switched off. Published images are stripped of metadata. Every image served from the public archive comes from a derivative with EXIF, IPTC and XMP removed. Phone photos routinely carry GPS coordinates and device serial numbers, and consenting to publish your words is not consenting to publish your home coordinates. The gate fails closed: a file that cannot be stripped is withheld rather than published unstripped. What is next Choosing what revocation does. Rather than a single irreversible action, you will pick: hide, which takes your words out of the public archive but keeps them so you can restore them later, or delete, which removes them for good. Deleting will require typing the word itself, so a reflexive yes cannot erase an archive. Alongside that, evidence holds. Content reported as illegal is held from destruction until it has been reviewed. The important detail is the separation: a hold prevents destruction, never hiding. You can always take your content out of public view immediately, with no review and no delay. Only the physical deletion waits. Reports are anonymous, so without that separation anyone could make someone else's content permanently undeletable simply by reporting it. Video links will play in the stream, with a design constraint worth stating: nothing loads from any third party until you click. The thumbnail is fetched once server-side and served from our own domain, so opening the archive produces no requests to external services at all. Alongside it, a consent banner with separate categories, where rejecting is exactly as easy as accepting. And a private channel. Right now everything she says is said in front of everyone, which is wrong for anything personal. Asking about your own archived content should not announce it to the room, and choosing whether to hide or delete should not be negotiated in public. That work includes a way to prove a private conversation belongs to a specific group member, because she must never change anyone's consent on the strength of an unverified message.

ANØM: The Most Genius FBI Operation https://www.youtube.com/watch?v=f6FRIDG8TPY

• ANØM: The Most Genius FBI Operation

🤞