We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We can use matrix to federate video/channel information data, geo-restriction bypass, etc.
We need to include a way to authenticate users into the system, maybe maintain a new list for this? We can authenticate matrix handles
Matrix seems like a better idea than using IPFS currently, since we can actually authenticate users for data transfers.
We can get more up-to-date view counts on lesser known instances
Channel data can sometimes change - they get verified, changes in uploader url, name, etc
No response
https://spec.matrix.org/v1.4/client-server-api/#types-of-room-events
Ephemeral events, are still not a thing in matrix/synapse: matrix-org/synapse#12413 matrix-org/matrix-spec-proposals#2477
We could have them as persistent events, and change them once they've been implemented.
We need to look at scalability, since we would likely send 100s of events a minute.
The text was updated successfully, but these errors were encountered:
Fully implemented 🚀
Sorry, something went wrong.
No branches or pull requests
Describe the feature
We can use matrix to federate video/channel information data, geo-restriction bypass, etc.
We need to include a way to authenticate users into the system, maybe maintain a new list for this? We can authenticate matrix handles
Why would this be useful to add?
Matrix seems like a better idea than using IPFS currently, since we can actually authenticate users for data transfers.
We can get more up-to-date view counts on lesser known instances
Channel data can sometimes change - they get verified, changes in uploader url, name, etc
Concept(s)
No response
Additional context
https://spec.matrix.org/v1.4/client-server-api/#types-of-room-events
Ephemeral events, are still not a thing in matrix/synapse:
matrix-org/synapse#12413
matrix-org/matrix-spec-proposals#2477
We could have them as persistent events, and change them once they've been implemented.
We need to look at scalability, since we would likely send 100s of events a minute.
Acknowledgements
The text was updated successfully, but these errors were encountered: