Skip to content

Commit

Permalink
Update 2023-11-21-xmpp-providers-automation.md
Browse files Browse the repository at this point in the history
  • Loading branch information
cal0pteryx authored Nov 22, 2023
1 parent 62553af commit 8ecdb8f
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions content/blog/2023-11-21-xmpp-providers-automation.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,26 +6,26 @@ date: 2023-11-21
## Automating the Automatable

During the past year, the team behind the XMPP Providers project worked on automating the process of gathering data about XMPP providers.
Automating this process reduces manual work significantly (i.e. checking websites by hand, verifying information, listing sources, etc.) and helps to sustain the team's efforts.
Automating this process reduces manual work significantly (for example checking websites by hand, verifying information, listing sources, etc.) and helps to sustain the team's efforts.
Automation also enables the project to be up to date - every day!

At the beginning of this year, work on automating the collection of several data 'properties' (e.g. available size for file uploads) started.
An overview of all these data properties the team gathers for each XMPP provider can be found on the [overview page](https://providers.xmpp.net/overview/).
At the beginning of this year, work on automating the collection of several provider 'properties' (for example available size for file uploads) started.
An overview of all these provider properties gathered for each XMPP provider can be found on the [overview page](https://providers.xmpp.net/overview/).
Some of these properties were already available in a machine-readable format, making it easy to be collected.

A {{< external-link url="https://invent.kde.org/melvo/xmpp-providers/-/blob/master/TOOLS.md#automation" text="suite of tools" >}} has been developed since, providing the ability to query properties via XMPP and through the web.
All of these tools are working together in a GitLab pipeline, which runs every night to keep the data up to date.

**So far, the following properties are gathered automatically:**
**So far, the following properties are collected automatically:**

- Account Creation via XMPP Apps: For determining whether a server supports the creation of accounts via XMPP apps, [XEP-0077: In-Band Registration](https://xmpp.org/extensions/xep-0077.html) is used.
- Account Creation via Web Page: For retrieving a web page that can be used to create accounts, [XEP-0077: In-Band Registration - Redirection](https://xmpp.org/extensions/xep-0077.html#redirect) is used.
- Server Software: For determining which software (including its version) a server runs, [XEP-0092: Software Version](https://xmpp.org/extensions/xep-0092.html) is used.
- Support Addresses: For retrieving the support addresses of a provider, [XEP-0157: Contact Addresses for XMPP Services](https://xmpp.org/extensions/xep-0157.html) is used.
- Support Addresses: For retrieving the support addresses of a provider, [XEP-0157: Contact Addresses for XMPP Services](https://xmpp.org/extensions/xep-0157.html) is used. Support addresses will be available in version 2 (v2) of the API.
- Upload Limits and Storage Durations: For determining how much users can upload to a server and how long those files are stored, [XEP-0363: HTTP File Upload - Discovering Support](https://xmpp.org/extensions/xep-0363.html#disco) is used.

The [FAQ section](https://providers.xmpp.net/faq/#where-do-we-have-the-providers-properties-from) explains how these properties can be provided by server admins.

## More Automation

Not all of the properties collected by the XMPP Providers project are machine-readable yet.
Not all of the properties collected by the XMPP Providers project are machine-readable yet. To enable automatic collection of the missing properties, the team works on extending existing standards and, if necessary, creating new ones.

0 comments on commit 8ecdb8f

Please sign in to comment.