@floomhq/signaldash 0.39.4 → 0.39.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +12 -4
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -120,7 +120,7 @@ setup installs both from the same pinned npm package
120
120
  the human chose to execute:
121
121
 
122
122
  ```bash
123
- npx -y @floomhq/signaldash@0.39.4 <invite-code>
123
+ npx -y @floomhq/signaldash@0.39.6 <invite-code>
124
124
  ```
125
125
 
126
126
  Run that command in a terminal, not in an agent chat. Do not ask an agent to
@@ -389,15 +389,23 @@ linkedin.com to fill the gap. An empty item list therefore means only that the
389
389
  visible SignalDash and Buffer sources are empty, never that the native LinkedIn
390
390
  calendar is empty.
391
391
 
392
+ The read-only calendar page renders each stored SignalDash image through a
393
+ calendar-session-protected, tenant-scoped media route. It does not invent
394
+ visuals for Buffer entries because SignalDash does not store their media bytes.
395
+ Calendar media is no-store and becomes unavailable when the session expires or
396
+ the originating user is revoked.
397
+
392
398
  `li_scheduled_post_preview` returns a short-lived, single-use browser handoff
393
399
  for one exact active SignalDash post owned by the authenticated user. The page
394
400
  shows only that post, including its stored image attachments. Preview sessions
395
401
  and media routes remain account- and post-scoped, expire independently, and
396
402
  are revoked on logout. New exact-post links use
397
403
  `https://signaldash.dev/p/<token>` and calendar links use
398
- `https://signaldash.dev/c/<token>`. Each compact token is 24 base64url
399
- characters generated from 18 random bytes. Already-issued
400
- `/scheduled-post/h/<token>` and `/calendar/h/<token>` links remain valid until
404
+ `https://signaldash.dev/c/<token>`. Each new compact token is 8 base64url
405
+ characters generated from 6 random bytes. Its 48 bits of entropy are bounded
406
+ by a 15-minute lifetime, one-use consumption, and a durable five-attempt
407
+ per-client throttle. Already-issued 24-character compact tokens and 48-character
408
+ `/scheduled-post/h/<token>` or `/calendar/h/<token>` links remain valid until
401
409
  their normal expiry.
402
410
 
403
411
  `li_edit_scheduled_post` replaces one complete scheduled-post payload in place.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@floomhq/signaldash",
3
- "version": "0.39.4",
3
+ "version": "0.39.6",
4
4
  "description": "Secure LinkedIn, WhatsApp, and email access for AI agents",
5
5
  "type": "module",
6
6
  "bin": {