This may have mistakenly caused link-local addresses to be considered
global. May have caused mod_s2s and prosodyctl check dns to behave
incorrectly on networks using link-local IPv4 addresses. By my
guesstimate, these are extremely rare. Probably minimal impact beyond
a bit longer to establish s2s and some possible confusion from
prosodyctl check dns results.
Ref RFC 3927
Downloaded from http://www.inf.puc-rio.br/~roberto/struct/
This is for compatibility with Lua 5.2 (and 5.1). Eventually we can replace
this with string.pack/string.unpack which are available in 5.3+.
This is a very old statement, but people generally don't need to check for the
files, and shouldn't be encouraged to put them in Prosody's source dir. The
installer will be the way forward for most people, and hg for the rest.
Manually moving files into the right place is not something most users should
be doing.
The only sensible option for most people these days is "epoll". The option is
still supported, but it should only be needed by packagers for specific platforms
(e.g. BSD may choose libevent for kqueue) or other special cases.
The default config was updated in this way long ago, but if no option was
present in the config, Prosody would load internal_plain.
This change can result in changes (for the better) for people using very old
configuration files lacking an 'authentication' setting.
Reasons:
- These now default to enabled when not specified since 38b5b05407be
- Practically all servers require encryption these days for c2s/s2s.
- Disabling encryption can be considered a special case that doesn't
need to be in the default config file.
These options have been specified (and enabled) in the default config file for
a long time. However if unspecified in the config, they were not enabled. Now
they are.
This may result in a change of behaviour for people using very old config
files that lack the require_encryption options. But that's what we want.
Serving web pages outside of specialized modules seems like a rare use
case that doesn't warrant a spot in the default config file.
Many users seem to have it confused with mod_http_upload, so removing it
should help with that.
mod_admin_shell enabled by default because it's awesome!
mod_smacks and mod_bookmarks under recommended since they're recommended
by the compliance suite XEP-0459
Invites under nice to have and enabled by default to enable a somewhat
nice out of the box experience
Other new modules mostly under Other
mod_external_services left out since it's an advanced thing
Originally added in 202b9951b037 but util.pubsub gained a better method
in 6c2c2fc4b8dd since then, which mod_pep uses since 9194431b6447 which
should have deleted this.
All these :create calls would have failed with a 'conflict' error, since
the nodes had already been created. This was never noticed because of
missing error handling.
Also note that this code did not restore node configuration.