-
It is true that the resource shound't have any meaningful details in them, but they should be unique across all user connections. I noticed that my two test ios devices both register "iphone" as their resource which results in them being kicked constantly due to resource conflicts. You are correct in the sense that resource strings aren't purposed to be identifiable. I wasn't asking to put some valueable info into them rather some recognisable pattern. Something like Conversations ( Conversations.6uUn ) or Gajim ( Gajim.28as3nh3 ) or Dino ( dino.2syds ) and so on. I think that these random letters aren't considered meanigful, but they are recognisable which is a benefit.
Would it be possible to set the resouce string to something groupable eg. Siskin.UIDevice.current.name ? This would be nice to monitor the connected users, based on their resource string.
https://github.com/tigase/siskin-im/blob/209812c20c1131e53b2fb5cdccf2995d64ff2c1f/SiskinIM/service/XmppService.swift#L569