Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

Homeservers should announce MOTD, canonical name, human name, version, etc... (SYN-1) #1199

Open
matrixbot opened this issue Sep 15, 2014 · 9 comments
Labels
A-User-Experience O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Tolerable Minor significance, cosmetic issues, low or no impact to users. T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.

Comments

@matrixbot
Copy link
Member

It'd be nice for homeservers to have as much personality as possible, so when you log onto a given one with a given client you get some kind of message of the day, or perhaps a nickname for the server, or image/HTML or something to characterise the server you're logging into.

(Imported from https://matrix.org/jira/browse/SYN-1)

(Reported by @ara4n)

@matrixbot
Copy link
Member Author

Jira watchers: @erikjohnston @kegsay @ara4n

@matrixbot
Copy link
Member Author

matrixbot commented Sep 15, 2014

Links exported from Jira:

is blocked by SPEC-161

@matrixbot
Copy link
Member Author

Increasing the priority on this as it's getting really confusing tracking which homeservers my various clients connect to.

-- @ara4n

@matrixbot
Copy link
Member Author

Announcing the version would be particularly useful, to check whether a bug is due to a server being too old for a client or vice versa.

-- @ara4n

@matrixbot
Copy link
Member Author

...and we need to actually announce the canonical hostname of the server, rather than guessing it from the C-S API url

...and it'd be good to announce config data like maximum content upload size limit.

-- @ara4n

@matrixbot
Copy link
Member Author

This surely falls under the remit of CS v2 capabilities API? https://github.com/matrix-org/matrix-doc/blob/master/drafts/general_api.rst#capabilities-api-ongoing

-- @kegsay

@matrixbot
Copy link
Member Author

matrixbot commented May 1, 2015

There are a few separate classes of things we might wish to return to the client:

  1. Is it static or changes often, e.g. server name vs. message of the day.
  2. Is it for internal usage or for human consumption, e.g. turn uris vs message of the day.
  3. Is it something immediately required by the client to work, or can it be fetched after client startup.

It may be worth having multiple APIs for distributing this data, e.g. required static information gets sent once on login, whereas optional, dynamic data like MotD could be a separate API.

-- @erikjohnston

@matrixbot matrixbot added z-p2 (Deprecated Label) z-feature (Deprecated Label) labels Nov 7, 2016
@matrixbot matrixbot changed the title Homeservers should announce MOTD, canonical name, human name, version, etc... Homeservers should announce MOTD, canonical name, human name, version, etc... (SYN-1) Nov 7, 2016
@matrixbot matrixbot changed the title Homeservers should announce MOTD, canonical name, human name, version, etc... (SYN-1) Homeservers should announce MOTD, canonical name, human name, version, etc... (https://github.com/matrix-org/synapse/issues/1199) Nov 7, 2016
@matrixbot matrixbot changed the title Homeservers should announce MOTD, canonical name, human name, version, etc... (https://github.com/matrix-org/synapse/issues/1199) Homeservers should announce MOTD, canonical name, human name, version, etc... (SYN-1) Nov 7, 2016
@ara4n
Copy link
Member

ara4n commented Apr 2, 2018

...and email address of the admin so we know who to mail when their federation is screwed.

@richvdh
Copy link
Member

richvdh commented Nov 5, 2018

Now that we have server notices, perhaps this could be implemented using that.

ara4n added a commit to matrix-org/matrix-spec-proposals that referenced this issue Sep 23, 2019
@babolivier babolivier added S-Tolerable Minor significance, cosmetic issues, low or no impact to users. T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements. O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience A-User-Experience and removed z-p2 (Deprecated Label) z-feature (Deprecated Label) labels Aug 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-User-Experience O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Tolerable Minor significance, cosmetic issues, low or no impact to users. T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.
Projects
None yet
Development

No branches or pull requests

4 participants