xsf / xmpp-providers-website Goto Github PK

Add a register button to landing page and details page as we discussed.

🇫🇴 🇨🇰 🇨🇨 🇧🇻

This would also make it possible to filter providers by currently selected language.

I could think of the head bar. Its always present not to loaded and we could place a link, like we do to xmpp.work on xmpp.org

The percentage and letters should have coloring as well. right?

Not a prio request.

It could also colorize if information is missing and by corlors (grey, yellow, red) indicate how important that is. or symbols (tick, cross, ?)

Here are some ideas for more statistics

• How many providers offer chat, group chat and email support? bar chart
• Which website languages are offered? pie chart
• How many providers are free of charge? pie chart
• How many providers offer professional hosting? pie chart
• How many providers have specific organisation types? pie chart
• How many servers use which software (without version)? pie chart
• How many providers offer account creation via app, web or none of them? pie chart
• How many providers use CAPTCHAs? pie chart
• How many providers support password resets? pie chart
• How many providers have a specific XMPP Compliance Tester result? bar chart
• Bar charts for remaining limit properties

This is a relatively low-priority issue, but it would be nice to have and shouldn't be too difficult.

Running a (working) copy of the website locally or elsewhere (not at providers.xmpp.net) is more difficult than it should be. There are two options to fix it:

• Use relative paths to resources, these include:
  • https://providers.xmpp.net/css/bootstrap.min.css
  • https://providers.xmpp.net/css/style.min.css
  • https://providers.xmpp.net/fontawesome/css/all.min.css
• Alternatively, allow overriding the baseURL config during the build process. This could be done by using a docker build arg, and passing the -b flag to hugo when building.

Reference all information with the respective source in the json file so user and devs see where we got the information from

I know we discussed already, but I think the users understands that there is something to expand.

I has a better clean impression when it is collapsed in the first view

That way, the provider does not need to create a completely new provider file if only a small change is needed.

"Prefers dark" :)

The URIs in HTML look like this: xmpp:[[email protected]]?join.

Looking at the data, seems it's an array of strings, not a single string.

Hi,

When using the docker approach for building and deploying the site, docker uses the checksum of ADD/COPY-added files to determine whether a layer is in the cache or not.

This means, if the website in the repo changes, docker will correctly rebuild the final image.

However, if only the upstream providers data changes, docker cannot see this - because that data is only fetched during building (by tools/prepare.py).

My recommendation would be to not download stuff in the script, but use ADD with a https:// URL (e.g. from data.xmpp.net) instead to have docker download the file for you, and check if it has changed.

Explain that "unknown" for properties means that there is no statement on the provider's website

All occurrences of unknown should link to that FAQ entry.

Website

• add license (https://reuse.software) ?
• check logo license
• alphabetical sorting of providers in overview (category first, then alphabetical)
• Implement list of client with XMPP providers integration ("Integration" menu item)
• unify colors of categories/badges
• separate language links by comma
• add favicon
• hover effect for rating badges
• add more space to Details button in overview
• add shortcode for target="_blank" links in markdown files (to open them in a new tab)
• check horizontal alignment of icons in details view
• summarize support addresses requirement (1 is required, don't list every missing address)
• "Server location:" use plural
• copy button for badge code (needs JS)
• live filtering of results using JS

Both FAQ and About section need text.

Deploy daily

https://github.com/stpeter/xmppdotnet

This needs either DOAP files or manual work.

It would be awesome if one could directly see if the server is hosted green :)
https://www.thegreenwebfoundation.org/ is providing an API for that. Similar as the greenfediverse project is doing it: https://greenfediverse.codeberg.page/green-instances/

The website should offer an option to filter the providers by their server locations (i.e., by the property serverLocation). I suggest to show a list of all countries that are specified by the providers. To keep it simple, users should be able to select one country at a time.

nixnet.services is listed as category A provider but their users have problems with omemo key sharing in encrypted groups. May be we should explicitly check omemo key sharing of users in encrypted private groups which are not in contacts. This completely breaks the encrypted chat as no one else can send any message in this group until that user is removed.

Password: "You cannot reset the password"

I would like to turn it yellow or orange.

not red because it can also be an expected feature

Hi,

I think it is important to have group history in public channels, which is known as MUC MAM in XMPP jargon. In my experience, the listed sure.im provider does not have this feature.

http://web.archive.org/

• What is the list / project for and for whom?
• Filtering by country (If not, why do we not filter / categorize by country) / Should the server location or the provider's location be used?
• Why do we not rank providers in specific categories if there are no information?
• As soon as there is more automation, why do we (not) use properties that cannot be checked automatically for categorization?
• How does the list result in more decentralization and lower loads for each server?
• Why do we list / include all existing providers?
• Why do we not ask every provider to be included?

• Not scalable for many providers

• Why / How do we check whether a provider is responding to support requests?
• Why is there data that is not precise / incorrect?
• How do you test the registration success?
• ActivityPub: With ActivityPub, instances have a strong focus on communities (e.g., people having interest in FOSS, LGBT+ friendly, German speaking, etc.). There moderation is also a major topic (to avoid harassment, harmful content, etc.), and you can follow message from the instance only. So the choice of instance is really important, and we should take inspiration from there and provide information on moderation policy, and a short sentence describing the purpose of the instance in human friendly way, ToS is also something important to retrieve.