bramvdnheuvel / matrix-events-directory Goto Github PK

https://github.com/toger5/st-petersburg-widget needs to store the game state

https://github.com/nordeck/matrix-barcamp afaik stores all of its data in matrix itself

The issue is about the fact that some keys in event content are required only under certain conditions. This is not currently implemented in the codebase, and there are a few potential ways to address it.

One option is to mark the conditionally required keys as optional, but this could lead to the test object checker sometimes approving events that do not follow the specifications. Another option is to implement the feature, but this would add complexity and might not be worth it if the conditional requirements are complex.

Another option is to change the spec and call the keys optional from our side. This would not add complexity to the codebase and would still allow for optional keys in the Search section of the directory. For the Browse section, events would not be allowed to contain conditionally required keys.

https://gitlab.com/minestrix/minestrix-doc MinesTRIX is another social media-on-matrix project
related MSC: matrix-org/matrix-spec-proposals#3639

• im.vector.modular.widgets widgets in a room
• io.element.widgets.layout how/where to show them, though this is very element-specific and not truly in the spirit of the directory

Repository: https://codeberg.org/imbev/matrix-social

Storing additional client information per device

https://github.com/vector-im/element-meta/blob/develop/spec/matrix_client_information.md

https://github.com/toger5/TheBoard afaik uses custom events to store the drawings and other elements

https://github.com/nordeck/matrix-poll afaik stores all of its data in matrix itself

Marking room members as unimportant functional members

https://github.com/vector-im/element-meta/blob/develop/spec/functional_members.md

Effektio is a community organizing app built on top of Matrix.

Though it currently doesn't have any custom event types in use, it intends to implement these in the future.

To quote @ben:effektio.org on this:

yes, as the whitepaper states, we eventually want events to be part of the matrix-spec or - alternatively, if matrix thinks they shouldn't be part of its spec - be part of a Effektio-Spec which has a similar open governance system as matrix has. With one crucial detail changed though and that is we want to experiment and build it from the UI-side, meaning we won't spec events very early and then build implementations, but start with a design/mock, then think about events, then build and get something into the hands, refine it, and once we are ready we put that all into a full spec - with as little changes as possible after the fact. This is too ensure we built super solid UI/UX first and will probably ingrain UI/UX-behaviour and expectations into the spec, too.

Ideally, you'll find all that on https://docs.effektio.org/ - which currently is only the documentating the events as part of the rust API docs though: https://docs.effektio.org/api/main/rust/effektio_core/events/index.html

Based on this information, it might take a while before definitife custom event types will be published for use in the more general Matrix ecosystem.

https://github.com/opentower/populus-viewer

Some details are mentioned in the README, including links to the MSCs derived from this project

https://gitlab.futo.org/circles/circles-spec Circles is a social media-on-matrix project

https://github.com/matrix-org/matrix-hookshot/
A bridge between Matrix and multiple project management services, such as GitHub, GitLab and JIRA.

Custom state events are used to store user-manageable bridge configuration, i.e. the bridged services.

E.g. link to Element Call from the m.call events