2025_04_27.md

tinySSB Meeting Notes - 2024-04-27

Agenda

• Check-ins
• App development guide
• Spec progress

Min-App dev

https://docs.google.com/document/d/1P2k5NO1w34DlmF05DdejNaWkg1LGTgjhf5Xd9WYc-5c/edit?tab=t.0

Feedback

1. define the API the mini-apps can call

2. dependency injection please (no global variables)

window.miniApps.register("wuff", {
  init: function (api) {
    let json = { type: 'Wuff'};
    api.writeLogEntry(JSON.stringify(json));

    return {
      handleRequest: function(command, args) {
        console.log("Wuff handling request:", command);
        switch (command) {
          case "incoming_notification":
              console.log("Wuff incoming_notification:", JSON.stringify(args, null, 2));
              handleWuff(args.args);
              break;
        }
        return "Response from Wuff";
      }
    }
  }
})

ES6 / import-export ideas

export default {
  name: 'wuff',
  init: function (api) {
    
  }
}

// App.js

import wuff from 'apps/wuff/index.js'
import kanban from 'apps/kanban/index.js'

start([
  wuff,
  kanban
])

3. refactor the API calls

writeLogEntry({
  type,
  payload
})

handleRequest({
  type,
  payload
})

Repo: https://github.com/tinySSB/mini-app-spec

---

Spec

Nano:

• feed messages
  • if exactly 48 bytes => type 0
  • if less that 48 => type 1
    • variable length .. may or may not fit into 48 bytes
• wire packets for replication
  • these are feeling pretty clear now

Claim messages:

[GOSET_DMX_CONST (7 bytes) | 'c' (1 byte)| lowest FID (32 bytes) | highest FID (32 bytes) | XOR (32 bytes) | cnt (1 Byte) ]

Novelty messages:

• notification of
• to be deprecated

Zap:

• clear everything out
• to be deprecated

Questions

Claim

1. why is cnt limited to 100?
2. why is cnt 1 bytes only - caps us at 256 feeds
3. is there padding that takes this to 120 bytes?
   • currently at 105 bytes

Want

1. how do we say "I don't want to hear anything about feed 4"

Future improvement

Claim messages

1. drop the outside 2, as you've already sent those out

Deleting messages

1. second feed of deletes

• messages contain
  • sequence of message(s) to delete
  • info to be able to know DMX to jump messages
  • signature
• could use this for Lipmaa links too

Wrap up messages

1. copy Keyhives sedimentree

Actions

Mix:

• book a time with Nanomonkey
  • SF time: <= 4pm, (or >= 7pm)