Meghan Denny
Meghan Denny
I think this is because this script is meant to be run while on the pinebook itself
> If this restriction could be: the actual typeID values can be stored and compare for equality but are otherwise opaque until runtime `type` already supports `==` ? runtime-only means...
so that links are able to survive `channel-rename` we should write a `channel-ids` spec as a parallel to `message-ids`
then the urls could be `irc://irc.ircnet.net/chanid/msgid` and be hydrated with the current info in a UI
it would likely be easier for clients to support something akin to https://getsharex.com/docs/custom-uploader and then send the url to the chat
there could be a capability for mention references to coordinate the backwards compat. enabled it could be like: `nektro` is a polite mention `` is an explicit mention for clients...
thanks, hmm I was more thinking about a UI that would parse the message and send the right one based on whether or not the user wanted it to be...
this feels very overkill for a chat protocol
this appears to be working now as of at least Bun 1.1.8
standard practice here is to check the `PKG_CONFIG` env var