[ticker-dev] Ticker group "invitation" attachments

Phillips, Matthew Matthew.Phillips at dsto.defence.gov.au
Tue Aug 24 20:47:43 CDT 2004


Just to add to the buzzing of excitement that this proposal has generated, I'd like to extend it a bit to add security properties eg:

  Ticker-Group: 1.0
  Name: Private Chat
  Type: chat 
  Private-Keys: Private Chat,My Private Key
  Default-Secure: true
  Accept-Insecure: false

New fields (all optional):
  
  * Private Keys: comma-separated list of private key names (do all clients have symbolic names for keys?)
  * Shared-Keys: Same as above for any shared keys.
  * Default-Secure: "true" or "false" (case insensitive) to indicate default to sending securely or not. Default is true (but obviously moot if no keys are included).
  * Accept-Insecure: "true" or "false" (case insensitive) to indicate whether to accept insecure messages or not. Default is true.

Since I'm kind of in a hurry to get this into the imminent beta release, and there doesn't seem to be a lot of interest in this from anyone else, I'm going to go ahead and implement it if good reasons not to haven't come in before Friday. If any changes are needed, we can bump the version number and I'll support both in the full release.

Just out of interest: am I the only one doing, or planning to do, any serious development in the ticker/presence area?

Matthew.

> -----Original Message-----
> From: ticker-dev-bounces at tickertape.org 
> [mailto:ticker-dev-bounces at tickertape.org] On Behalf Of 
> Phillips, Matthew
> Sent: Monday, 16 August 2004 1:22 PM
> To: 'ticker-dev at tickertape.org'
> Subject: [Spam Detected] [ticker-dev] Ticker group 
> "invitation" attachments
> 
> Hi all,
> 
> I've decided I'd like to add the ability to "invite" others 
> to a ticker group for the next Sticker (it's about the only 
> useful suggestion I had from JWID and I want to show willing 
> ;) So I'm proposing a simple attachment format for ticker 
> groups, and suggesting "application/x-elvin-tickergroup" as 
> the MIME type. Some examples probably will get the idea across:
> 
> ---
> 
>   Ticker-Group: 1.0
>   Name: ticker-dev
>   Type: chat
> 
> ----
> 
>   Ticker-Group: 1.0
>   Name: CNN
>   Type: news
> 
> ----
> 
>   Ticker-Group: 1.0
>   Name: Interesting
>   Type: custom
>   Subscription: contains (Message, "foobar")
> 
> ----
> 
> You'll note the idea is to use the same "name: value" format 
> as for keys. To spec the format a little more precisely, I'm 
> also proposing:
> 
>  * UTF-8 encoding be the default
>  * To allow either \n or \r\n as the line-delimeter
>  * To allow empty lines and comment lines preceded by '#'.
> 
> Also '\' would be an escape anywhere in a line, and at the 
> end of a line would allow line concatenation eg:
> 
>   Field\:with a colon: This is a \
>   multiline value for "Field:with a colon"
> 
> Comments, suggestions?
> 
> Matthew.
> _______________________________________________
> ticker-dev mailing list
> ticker-dev at tickertape.org
> http://www.tickertape.org/mailman/listinfo/ticker-dev
> 


More information about the ticker-dev mailing list