XSF Discussion - 2021-07-14

Can we have XEP-0157, but for bots?

Ge0rG, what stops a bot from using '157?

jonas’: on the bare JID?

full JID

That requires the bot to be online

that’s true

(same for servers publishing '157 though)

Also you need to have presence with the bot, which might or might not work

or you observe a message from the bot, that would come from the full jid

Yes, but there also happen to be bots that send a flood of messages, disconnect, and come back later with a different random resource

right

so you actually want '157 on the account. how about a vcard? :)

bonus: vcard is likely to pass through MUC

Wasn't there a field you could put 'software' in for vcard4

I don't want the software, I want to know whom to write that their bot is blocked for a year now.

could put something like: <email> <parameters><type><text>work</text></type></parameters> <text>psaintan@cisco.com</text> </email> in the vcard (stolen from '292)

That psaintan is everywhere!

Ge0rG, specify a way how an entity can publish/set xep157 information on their bare jid?

I think you can refer to your "boss" too

flow: that sounds like it would be better in PEP, or even vCard

how about vCard in PEP? :-O

But no bot does it anyway.

It would actually ve interesting to have a bot account type

we do have an disco indentity 'bot'

Zash: a server could automatically set that when doing disco

Mmmm

But what if you have multiple clients connected, and only one is a bot? Do we need a botness gradient?

Ge0rG, the identity is part of the resource’ disco#info response

jonas’: yes, I suggested to use that to automatically set the account bot flag

Saving devi disco#info in the account feels like something that's been mentioned before

A device registry? I've noticed that during server shutdown, very much time is spent deleting the non existent firewall flags from all connected accounts. We really need to do something about disk IO