jdev - 2026-04-10

Hi

XEP-0060 refers to a <payment-required xmlns="urn:ietf:params:xml:ns:xmll-stanzas"/> node, but that node no longer exists as of RFC 6120

Can Blocking Command (XEP-0191) be extended to include blocklists?

What kind of blocklists?

A uploaded text file containing lists of domains and JIDs

Or a text file on a HTTP server

Like a bulk import? A client could easily do that

Or a list updated by a PubSub node ✏

> Like a bulk import? A client could easily do that No like automated blocklist updating ↺

And also being separate from the blocks that the user has

for the pubsub thing that's more a server module. But very easy to write we basically have it already with mod antispam just need to make it per user or whatever

right sure. So like rtbl but user configurable in their own account and for 1:1 not muc. Should be easy

Yes

No

chunkipho: why

cuz

reasons not required

> for the pubsub thing that's more a server module. But very easy to write we basically have it already with mod antispam just need to make it per user or whatever Does Blocking Command have like a separation of lists? ↺

hi chunk

Like one user list, and the others that the client updates from fetching the text file lists it has ✏

hi snit

>> for the pubsub thing that's more a server module. But very easy to write we basically have it already with mod antispam just need to make it per user or whatever > > Does Blocking Command have like a separation of lists? Blocking command doesn't really have anything to do with this. That's just a command syntax. Actual blocking functionality is implementation defined and I don't see any obstacle to a subscribe to blocklist function ↺

pubsub has not method of notifying me when the node config changes or?