Support Threading #96
Labels
No labels
Android
CS::needs customer feedback
CS::needs follow up
CS::needs on prem installation
CS::waiting
Chrome
Design:: Ready
Design:: in progress
Design::UX
E2EE
Edge
Firefox
GDPR
Iteration 13 IM
Linux
MacOS
Need::Discussion
Need::Steps to reproduce
Need::Upstream fix
Needs:: Planning
Needs::Dev-Team
Needs::More information
Needs::Priority
Needs::Product
Needs::Refinement
Needs::Severity
Priority::1-Critical
Priority::2-Max
Priority::3-Impending
Priority::4-High
Priority::5-Medium
Priority::6-Low
Priority::7-None
Progress::Backlog
Progress::Review
Progress::Started
Progress::Testing
Progress::Triage
Progress::Waiting
Reporter::Sentry
Safari
Target::Community
Target::Customer
Target::Internal
Target::PoC
Target::Security
Team:Customer-Success
Team:Design
Team:Infrastructure
Team:Instant-Messaging
Team:Product
Team:Workflows
Type::Bug
Type::Design
Type::Documentation
Type::Feature
Type::Improvement
Type::Support
Type::Tests
Windows
blocked
blocked-by-spec
cla-signed
conduit
contribution::advanced
contribution::easy
contribution::help needed
from::review
iOS
p::ti-tenant
performance
product::triage
proposal
refactor
release-blocker
s: dart_openapi_codegen
s::Famedly-Patient
s::Org-Directory
s::Passport-Generator
s::Requeuest
s:CRM
s:Famedly-App
s:Famedly-Web
s:Fhiroxide
s:Fhiroxide-cli
s:Fhiroxide-client
s:Fhirs
s:Hedwig
s:LISA
s:Matrix-Dart-SDK
s:Role-Manager
s:Synapse
s:User-Directory
s:WFS-Matrix
s:Workflow Engine
s:dtls
s:famedly-error
s:fcm-shared-isolate
s:matrix-api-lite
s:multiple-tab-detector
s:native-imaging
severity::1
severity::2
severity::3
severity::4
technical-debt
voip
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Matthias/conduit#96
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Official MSC2836
Issue in Ruma
Necessary for forum-like apps such as Hummingbard (repo) to work. Ruma/Conduit is looking to be the easiest and most cost-effective way to self-host a Matrix community. The most advanced reference implementation of a federated, ActivityPub-compatible forum also happens to be made in Rust: Lemmy.
Personally I see the greatest potential in a more Discourse-like client implementation, primarily designed for structured discussion as seen on Users and Internals. The official Matrix server for Rust should eventually bridge seamlessly with those two forums. I’m working with the Hummingbard developer to envision a prototype for such a chat/forum hybrid application in a soon-to-be-released rewrite of Hb.
A reference implementation exists in Dendrite:
https://github.com/matrix-org/dendrite/pull/1589
https://github.com/matrix-org/dendrite/pull/1596
It’s also been demonstrated in Cerulean:
https://github.com/matrix-org/cerulean
changed the description
changed the description
There are some reference implementations already, so do you think we should start implementing this before it has been merged into Matrix?
Definitely no urgency on this; primarily just wanted to track it, so others with similar requirements can chime in over time.
I will mark this as blocked until it is merged into the matrix spec.
changed title from {-[Feature Request]-} Threading to {+Support+} Threading
Some updated info:
IMHO this is no longer
blocked-by-spec
.This can probably be closed since https://gitlab.com/famedly/conduit/-/merge_requests/487
I still saw some problems with element web properly showing updates in threads, so I'll keep this open until I figured out why that is.
Indeed we face such strange behavior too.