| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
|
| |
.affiliation
It appears nothing currently uses this field in prosody or prosody-modules
|
| |
|
|
|
|
| |
...and fixing the logic bug that broke everything in the previous commit.
|
|
|
|
| |
data
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was originally not done based on my interpretation of XEP-0045. Today's
reading, however, revealed that it actually says the result
> SHOULD contain **at least** a <username/> element
(emphasis mine)
I take this to mean that including a form **is** allowed (and I think this is
sensible). Tigase already includes the form I believe.
I've gated the new behaviour behind a (default off) option, because it hasn't
been tested for compatibility with clients. My primary desire for it is in
Snikket, where the clients will be tested to ensure compatibility with this.
I don't anticipate that (m)any clients would break, so maybe after 0.12 we can
experiment with enabling it by default and eventually remove the option.
|
|
|
|
|
|
| |
arcseconds)
I surmise this can happen in a disconnected/smacks hibernation state.
|
|
|
|
|
|
|
| |
In this case `ret` is a table not containing the node, which makes
pubsub_error_reply() try to get an error template with that `ret` table
as index, which returns a `nil` then passed to table.unpack, which in
turn throws the error.
|
|
|
|
|
| |
The overlapping logic for deletion and password changed has been merged into
a single function.
|
|
|
|
|
| |
Seems more like conventional Lua than passing an empty string to signal
lack of value.
|
|
|
|
|
| |
Makes it so that returning e.g. util.cache :table() produces useful
output, which otherwise would look like empty tables.
|
|
|
|
| |
Avoids ellipsis
|
| |
|
| |
|
|
|
|
|
|
| |
as column
Similar to the earlier view
|
|
|
|
|
|
| |
Nicer and more readable.
Thanks jonas’ and prosody@ for JID length stats to inform column widths.
|
|
|
|
|
| |
Previously this would return item-not-found, even when you could see the
node in disco#items.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Internal use of XEP-0122 to shift the responsibility for converting
numbers to strings.
|
|
|
|
|
| |
Better than duck typing, in case anyone ever passes a non-stanza table
with a 'name' field.
|
|
|
|
|
|
|
| |
`reason` was often a table, so the log said "table: 0xptr" or such.
mod_c2s, mod_bosh etc logs the stream error stanza object, so better do
the same. It would be nicer if this was an util.error object, but that
will have to be a future change.
|
| |
|
|
|
|
|
|
|
| |
If the request fails in the middle then the file~ could be left behind
because no code was invoked to delete it then. This gets rid of it when
the request is removed. It may still be left in case of an unclean
shutdown.
|
|
|
|
|
| |
Labels are supposed to be fixed sets of things, so defined hosts are
okay, but not unknown hosts.
|
|
|
|
|
|
| |
Can't find anything saying anything on whether this is needed or not.
kawaii reported that both Chrome and Firefox complained unless the
header was added to the list of allowed headers.
|
|
|
|
|
|
| |
Clients would generally be using the "max" symbol instead of discovering
this, but this also gets us validation and earlier rejection of out of
bounds values.
|
|
|
|
|
|
|
| |
Disable persistence instead if no items should be persisted.
XEP-0060 is not entirely clear on what either of those option really
mean.
|
|
|
|
|
|
|
|
| |
Default left as 'never' in mod_pubsub to preserve the previous behavior.
Unclear if this is desirable, but can always be changed later.
In mod_pep this allows turning off the automatic resending of most
recent item.
|
|
|
|
|
|
|
| |
This is as per the HTTP standards [1]. Thankfully, the REQUIRED
www-authenticate header is already generated by the code.
[1]: https://datatracker.ietf.org/doc/html/rfc7235#section-3.1
|
|
|
|
| |
mod_auth_ldap provides LDAP support without being tied to Cyrus
|
|
|
|
|
| |
Because it's nice, not having to find it in http:list(), which could
have a lot of items.
|
| |
|
| |
|
| |
|
|
|
|
| |
We're doing our best!
|
| |
|
|
|
|
|
|
| |
The default of 0.001..100.0 did not feel suitable here. This might be
better. Longer is better and hold times less than a few seconds is
generally undesirable.
|
|
|
|
| |
Mirroring the internal API
|
|
|
|
|
| |
Previously it would default to exit with 0 as status code, meaning
success, which is weird.
|
|
|
|
|
|
| |
Per the unspoken internal standard of -1 as priority for most built-in
event handlers, since this makes it easy for 3rd party plugins to
override behavior by hooking at the default priority of 0.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This line was copied from mod_mam, where `origin.username` made sense,
less so here.
|
|
|
|
|
|
|
|
| |
This is becoming more common in XMPP as people experiment with a MIX-like
model where the bare JID joins a group chat instead of a full JID.
Specifically right now this is being added to help with processing
notifications from mod_muc_offline_delivery.
|
| |
|
|
|
|
| |
Remember to remove the compatibility things in some future version
|