#4660 NORM Update.: ShareActivity() properties argument should do something

[Zarro Boogs per Child]

#4660: ShareActivity() properties argument should do something
-------------------------------+--------------------------------------------
  Reporter:  bert              |       Owner:  smcv              
      Type:  enhancement       |      Status:  assigned          
  Priority:  normal            |   Milestone:  Update.1          
 Component:  presence-service  |     Version:  Git as of bug date
Resolution:                    |    Keywords:  Update.1? review? 
  Verified:  0                 |  
-------------------------------+--------------------------------------------

Comment(by smcv):

 re custom properties: Basically, we don't want to have to think about
 data-size limits until we actually need to. telepathy-salut has some quite
 small limits on the size of a TXT record and a poor failure mode if the
 limit is exceeded, so we're more comfortable with only supporting a finite
 set of properties at this stage.

 Bear in mind that for the purposes of PS we're defining "activity
 properties" to mean "those properties that you need to be able to see
 without actually joining the activity", or more or less equivalently,
 "those properties that the Shell wants". Once you're in an activity, you
 can use Tubes to get whatever arbitrary data sharing you want.

 In future, perhaps we should treat the activity properties like the
 avatar, i.e. put a hash in the _presence._tcp or _olpc-activity1._udp TXT
 record and get the actual values via TCP. Then we'd be able to support
 arbitrary properties at the Telepathy level, and could punt the choice of
 what properties are needed to Sugar and activities.

 It seems to be somewhat vague whether the 'color' property is mutable or
 not. You're probably right, we should reject it too.

-- 
Ticket URL: <http://dev.laptop.org/ticket/4660#comment:12>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system