Matthias/conduit
1
0
Fork 0
Code Issues 179 Pull requests 44 Projects Releases 5 Packages Wiki Activity

Send all EDUs over federation #58

New issue
Open
opened 2021-03-03 10:41:12 +00:00 by timokoesters · 46 comments
timokoesters commented 2021-03-03 10:41:12 +00:00 (Migrated from gitlab.com)
Copy link
  • typing
  • read receipts
  • presence
    • reliable
    • unreliable
  • to-device messages
  • device list updates
- [ ] typing - [x] read receipts - [ ] presence - [ ] reliable - [ ] unreliable - [x] to-device messages - [ ] device list updates
timokoesters commented 2021-05-14 12:10:49 +00:00 (Migrated from gitlab.com)
Copy link

assigned to @timokoesters

assigned to @timokoesters
timokoesters commented 2021-05-21 11:27:12 +00:00 (Migrated from gitlab.com)
Copy link

marked the checklist item read receipts as completed

marked the checklist item **read receipts** as completed
timokoesters commented 2021-07-20 20:20:44 +00:00 (Migrated from gitlab.com)
Copy link

marked the checklist item to-device messages as completed

marked the checklist item **to-device messages** as completed
M0dEx commented 2022-06-30 12:54:56 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in merge request !370

mentioned in merge request !370
M0dEx commented 2022-11-18 16:22:53 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in merge request !418

mentioned in merge request !418
M0dEx commented 2022-11-27 17:59:13 +00:00 (Migrated from gitlab.com)
Copy link

changed the description

changed the description
timokoesters commented 2023-02-07 22:26:23 +00:00 (Migrated from gitlab.com)
Copy link

changed title from Send EDUs over federation to Send {+all +}EDUs over federation

changed title from **Send EDUs over federation** to **Send {+all +}EDUs over federation**
M0dEx commented 2023-05-28 22:00:34 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit f807c1c38d37a06f2bd02456bc9c3c6ea1b244c0

mentioned in commit f807c1c38d37a06f2bd02456bc9c3c6ea1b244c0
M0dEx commented 2023-05-28 22:07:42 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 925e77bd17d091ced4f59260b1ec9e50b0781faa

mentioned in commit 925e77bd17d091ced4f59260b1ec9e50b0781faa
M0dEx commented 2023-05-28 22:10:37 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in merge request !476

mentioned in merge request !476
M0dEx commented 2023-05-28 22:17:45 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit fa3108bcd7fca058d83212b3633e6d0232ffb788

mentioned in commit fa3108bcd7fca058d83212b3633e6d0232ffb788
M0dEx commented 2023-05-28 22:23:46 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 110e92c717ccb18dbcff3dc78cca03de8365cd68

mentioned in commit 110e92c717ccb18dbcff3dc78cca03de8365cd68
M0dEx commented 2023-05-28 22:25:30 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 9b58bcd80f5f854c09c78fb27de1b09d46811232

mentioned in commit 9b58bcd80f5f854c09c78fb27de1b09d46811232
M0dEx commented 2023-05-28 22:26:30 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 843a6a77c8ca8ee9ba1d1318dc2e60c870f39005

mentioned in commit 843a6a77c8ca8ee9ba1d1318dc2e60c870f39005
M0dEx commented 2023-05-29 09:41:24 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit ae5b52002aab5f9b16b3409df62ab782320765a7

mentioned in commit ae5b52002aab5f9b16b3409df62ab782320765a7
M0dEx commented 2023-05-29 09:41:24 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 8000bdce80e7f14fabb8af01dea10ea5382ae99c

mentioned in commit 8000bdce80e7f14fabb8af01dea10ea5382ae99c
M0dEx commented 2023-05-29 11:56:22 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 689e8451cc81be938641dcc3c36f11070af6f098

mentioned in commit 689e8451cc81be938641dcc3c36f11070af6f098
M0dEx commented 2023-05-29 21:18:23 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 7ba2bdf78eaa0f66dd7c1dc1488ac00d5cfa01a5

mentioned in commit 7ba2bdf78eaa0f66dd7c1dc1488ac00d5cfa01a5
M0dEx commented 2023-05-29 21:23:01 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 1cab2d9305d35556cf5df21413fa030c287d2f80

mentioned in commit 1cab2d9305d35556cf5df21413fa030c287d2f80
M0dEx commented 2023-05-29 21:27:22 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit d296ec19f190d83ebb7c041bd5e012b088a14277

mentioned in commit d296ec19f190d83ebb7c041bd5e012b088a14277
M0dEx commented 2023-06-25 21:18:31 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 9e9a75e2f1571701c5bcdd8f6b41b9189c9ad85d

mentioned in commit 9e9a75e2f1571701c5bcdd8f6b41b9189c9ad85d
M0dEx commented 2023-06-25 21:18:31 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 3837004b68f775e4e4eb2db6ee6b92d3aee270a1

mentioned in commit 3837004b68f775e4e4eb2db6ee6b92d3aee270a1
M0dEx commented 2023-06-25 21:18:31 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 7ac074ec27b95429ab0992b0656de2f70180960d

mentioned in commit 7ac074ec27b95429ab0992b0656de2f70180960d
M0dEx commented 2023-06-25 21:18:31 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 44d29c53114a13526ab7d00b67da8bd2417af4ac

mentioned in commit 44d29c53114a13526ab7d00b67da8bd2417af4ac
M0dEx commented 2023-06-25 21:18:31 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 1b4c76af7e47d29b80ddb1b21c6efe2fe776a5b1

mentioned in commit 1b4c76af7e47d29b80ddb1b21c6efe2fe776a5b1
M0dEx commented 2023-06-25 21:18:31 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 267fdd20836e1886e92cff31f25f04203995401f

mentioned in commit 267fdd20836e1886e92cff31f25f04203995401f
M0dEx commented 2023-06-25 21:18:31 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 98e76904153b470322a95d5160fa044d1718f3c6

mentioned in commit 98e76904153b470322a95d5160fa044d1718f3c6
M0dEx commented 2023-06-25 21:18:31 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 3c04150b2981c5758ae73018234b751e3c955d74

mentioned in commit 3c04150b2981c5758ae73018234b751e3c955d74
M0dEx commented 2023-06-25 21:18:31 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit c6da78aa36ceb8ef32d07c15a1779df9cab02b8a

mentioned in commit c6da78aa36ceb8ef32d07c15a1779df9cab02b8a
M0dEx commented 2023-06-25 21:18:31 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit dbe70bf9223ec9ddb8e316a11b5b6c14cd8c2160

mentioned in commit dbe70bf9223ec9ddb8e316a11b5b6c14cd8c2160
M0dEx commented 2023-06-25 21:18:31 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 13257e4f72d75375d1b9cb226f290f4892d6efd4

mentioned in commit 13257e4f72d75375d1b9cb226f290f4892d6efd4
M0dEx commented 2023-06-25 21:18:31 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 9b273ecf97e4e88148518d0f0e3b99954b418824

mentioned in commit 9b273ecf97e4e88148518d0f0e3b99954b418824
M0dEx commented 2023-07-03 16:02:13 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 8c7cb7cc9e83e8aa6e8b1ca65c2249a469311438

mentioned in commit 8c7cb7cc9e83e8aa6e8b1ca65c2249a469311438
M0dEx commented 2023-07-03 16:02:13 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit b423dd282669e76f6e1f6ffea7850eb8e00b38e4

mentioned in commit b423dd282669e76f6e1f6ffea7850eb8e00b38e4
M0dEx commented 2023-07-03 16:02:13 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 0210c5c4d29c15765da8ec0328ddfbdb8bc7f681

mentioned in commit 0210c5c4d29c15765da8ec0328ddfbdb8bc7f681
M0dEx commented 2023-07-03 16:02:13 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 70927547bd7b18dbff89235373a982981983f1f9

mentioned in commit 70927547bd7b18dbff89235373a982981983f1f9
M0dEx commented 2023-07-03 16:02:14 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit d3a2b3e12c53a8d6d20a48f37d09816211a30e07

mentioned in commit d3a2b3e12c53a8d6d20a48f37d09816211a30e07
M0dEx commented 2023-07-03 16:02:14 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit a7f0e2b181fe98cc8c456742897b0bd8890a50fd

mentioned in commit a7f0e2b181fe98cc8c456742897b0bd8890a50fd
M0dEx commented 2023-07-03 16:02:14 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 73855c44b3cc68e39cf74a2bba97443b90d00768

mentioned in commit 73855c44b3cc68e39cf74a2bba97443b90d00768
M0dEx commented 2023-07-03 16:02:14 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 421899290471122ac946c7caf7c30fff1abcde6a

mentioned in commit 421899290471122ac946c7caf7c30fff1abcde6a
M0dEx commented 2023-07-03 16:02:14 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit fdc46d0cfe0a16d36c7cae6601f810f4c0146f97

mentioned in commit fdc46d0cfe0a16d36c7cae6601f810f4c0146f97
M0dEx commented 2023-07-03 16:02:14 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 0bef084f08ae3414c4224d787667291f12607be8

mentioned in commit 0bef084f08ae3414c4224d787667291f12607be8
M0dEx commented 2023-07-03 16:02:14 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 26dae1e214e067f9ada5a061d42299b9293aab0e

mentioned in commit 26dae1e214e067f9ada5a061d42299b9293aab0e
M0dEx commented 2023-07-03 16:02:14 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit a8967e6ef02f218e40e845b5b68b34aef359100c

mentioned in commit a8967e6ef02f218e40e845b5b68b34aef359100c
solarkraft commented 2023-09-01 13:25:04 +00:00 (Migrated from gitlab.com)
Copy link

Hey, thank you very much for working on this!

What's the approximate high level status / what are the plans regarding this feature?

It seems like one of the last things missing for a "complete" experience.

Hey, thank you very much for working on this! What's the approximate high level status / what are the plans regarding this feature? It seems like one of the last things missing for a "complete" experience.
CobaltCause commented 2023-12-29 08:40:55 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in issue #412

mentioned in issue #412
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
next
performance
jonas-test-ci-docker-building-quemu-on-fsinfo-runner
presence
master
askstate
recoverbroken
Nyaaori/temp-combined-feature-branch
Nyaaori/destructive-rocksdb-recovery
Nyaaori/full-profile-directory
Nyaaori/read-receipt-config-options
Nyaaori/private-read-receipts
Nyaaori/federation-backfill
Nyaaori/declare-msc3827
Nyaaori/remove-misisng-e2ee-readme
refactor
Nyaaori/refactor-next
refactor-ci-fix
bump-docker-alpine-to-3.16.2
jplatte/up-ruma
mdbook-docs-preparation
async
244-support-well-known
complement-integration
brokenjoinfix
state_full_ids_cache
ticho34782694/conduit-rocksdb-memory-usage
docs-the-second
serve-element-web
perf
nyaaori/older-room-versions
serve-well-known
unbeatable-101-next-patch-64009
docs-overhaul
state-res-perf
stablecrosssigning
member-reason
admin-command-for-cache-memory-usage
measure-cache-memory-usage
lesscache
locks
state-res-closure-rebased
ruma-client
ruma
v0.6.0
v0.5.0
v0.4.0
v0.3.0
v0.2.0
Labels
Clear labels   
Android

This label indicates that the issue affects Android devices.

  
CS::needs customer feedback

Issue has been finished and needs feedback from the customer if everything is okay OR the customer needs to answer questions before issue can be worked on.

  
CS::needs follow up

We have received questions or new information from the customer that needs discussing in the meeting with Product and Sales

  
CS::needs on prem installation

This Issue needs to be installed on prem at the customer after closing

  
CS::waiting

This Issue is in progress in other teams (prod/tech)

  
Chrome

This label indicates that the issue affects the chrome browser. You should always combine it with other platforms like Android, if it only affects Android.

  
Design:: Ready

   
Design:: in progress

   
Design::UX

@Famedly: Do not use this label

  
E2EE

   
Edge

This label indicates that the issue affects Edge devices.

  
Firefox

This label indicates that the issue affects Firefox devices.

  
GDPR

   
Iteration 13 IM

   
Linux

This label indicates that the issue affects Linux devices.

  
MacOS

This label indicates that the issue affects MacOS devices.

  
Need::Discussion

Topic needs more discussion

  
Need::Steps to reproduce

   
Need::Upstream fix

   
Needs:: Planning

   
Needs::Dev-Team

This label indicates that the issue needs to be assigned to a dev team.

  
Needs::More information

   
Needs::Priority

This label should be set if there is no priority on feature or improvement requests.

  
Needs::Product

   
Needs::Refinement

the issue is triaged and needs to go to the refinement meeting to be able to set story points to the issue

  
Needs::Severity

This label should be set if bug reports need a severity.

  
Priority::1-Critical

The Priority 1 label indicates a critically dire issue such as a regression, or failure in existing features. We look at issues with this label frequently. If you find yourself assigning a Prio 1 label to an issue, please be sure that there's a positive handoff between filing and a prospective owner for the issue. Prio 1 issues should be rare. Normally there should be zero open P1 issues. "The world is on fire."

  
Priority::2-Max

The Priority 2 label indicates that the issue deserves immediate attention, such as affecting a top-tier customer. There are generally only one or two Prio 2 bugs at a time, and we aim for there to be none. "A customer is on fire."

  
Priority::3-Impending

A bug with Priority 3 flag indicates that a top-tier customer is about to encounter this bug. Generally, there are less than ten Priority 3 bugs. Issues may not be handled immediately (sometimes some Prio 4 issues are handled first), but are top-of-mind and we explicitly consider them weekly. "A customer is about to be on fire."

  
Priority::4-High

The Priority 4 label indicates high-priority issues that are at the top of the work list. This is the highest priority level an issue can have if it isn't affecting a top-tier customer or breaking the app. Bugs marked Priority 4 are generally actively being worked on unless the assignee is dealing with a P1-P3 bug(or another P4 issue).

  
Priority::5-Medium

The Priority 5 label indicates issues that we agree are important to work on, but not at the top of the work list. This is the default level for a bug. An issue at this priority level may not be worked on for a long time. Often an issue at this level will first migrate to Prio 4 before we work on them.

  
Priority::6-Low

The Priority 6 label indicates issues we think are valid but not important. This is the default level for new feature requests. We are unlikely to work on such issues unless they form part of a long-term strategic plan (see the Roadmap).

  
Priority::7-None

The Priority 7 label indicates valid issues that are unlikely to ever be worked on. We use "thumbs-up" on these issues to promote them to Priority 6 or higher based on demand.

  
Progress::Backlog

The Refinement of the issue is completed and DoR for the Squad is fulfilled

  
Progress::Review

Merge Request is ready for review. By definition MR review needs to be done by a second developer.

  
Progress::Started

The issue has been picked up for work by a developer in the team and the developer started to work on actively on the issue.

  
Progress::Testing

In testing

  
Progress::Triage

This is the first step of the process. Issue has been recently opened. Product team will identify/evaluate the following: - Clarify questions if required / verify DoR for Product is met. - It’s been identified if Design work is required or not. - Technical Feasibility - Components involved. - Team to work on that issue. - Severity (in case the issue refers to a bug)

  
Progress::Waiting

A blocker has been identified and work cannot continue.

  
Reporter::Sentry

   
Safari

This label indicates that the issue affects Safari devices.

  
Target::Community

   
Target::Customer

   
Target::Internal

   
Target::PoC

Proof of Concept - issues necessary for potential customer acquisition. Can be scoped by deadline for planned presentations

  
Target::Security

   
Team:Customer-Success

   
Team:Design

Issues which are in the competence area of the frontend chapter. It is not a scoped label anymore as issues can be part of different chapters. Before we can start implementing/changing this, we need a UI/UX design first.

  
Team:Infrastructure

Issues which are in the competence area of the infrastructure chapter. It is not a scoped label anymore as issues can be part of different chapters.

  
Team:Instant-Messaging

   
Team:Product

Issues which are in the responsibility of the product team.

  
Team:Workflows

   
Type::Bug

A software bug is an error, flaw or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.

  
Type::Design

A task about creating or improving the UI/UX design

  
Type::Documentation

   
Type::Feature

Nothing broken; Request for a new feature.

  
Type::Improvement

An improvement or enhancement to an existing feature, technically solution or code. It makes a working functionality faster, more secure, add some additional value, refactors code etc. or helps to design a better UX and UI.

  
Type::Support

   
Type::Tests

A task about writing or improving automated or manual tests.

  
Windows

This label indicates that the issue affects Windows devices.

  
blocked

   
blocked-by-spec

   
cla-signed

   
conduit

   
contribution::advanced

   
contribution::easy

Easy task to start with a contribution

  
contribution::help needed

   
from::review

Reported by famedly review

  
iOS

This label indicates that the issue affects iOS devices.

  
p::ti-tenant

This label indicates that the issues is a requirement of the ti-tenant

  
performance

   
product::triage

   
proposal

A feature propsal.

  
refactor

   
release-blocker

This issue needs to be fixed before the next release.

  
s: dart_openapi_codegen

   
s::Famedly-Patient

Service: Famedly-Patient App

  
s::Org-Directory

For issues that relate to the organisation directory https://gitlab.com/famedly/company/backend/services/organisation-directory/

  
s::Passport-Generator

Service: PASSporT-Generator

  
s::Requeuest

For anything relevant to the requeuest library

  
s:CRM

Service: CRM

  
s:Famedly-App

Service: Famedly-App

  
s:Famedly-Web

Service: Famedly-Web

  
s:Fhiroxide

Service: Fhiroxide

  
s:Fhiroxide-cli

Fhir(oxide) maintenance and debug CLI

  
s:Fhiroxide-client

Fhiroxide client library

  
s:Fhirs

Service: FHIRS

  
s:Hedwig

Service: Hedwig

  
s:LISA

Service: LISA

  
s:Matrix-Dart-SDK

Service: Matrix-Dart-SDK

  
s:Role-Manager

Service: Role-Manager

  
s:Synapse

Service: Synapse

  
s:User-Directory

Service: User-Directory

  
s:WFS-Matrix

Service: Workflow-Service-Matrix

  
s:Workflow Engine

Service: Workflow-Engine

  
s:dtls

   
s:famedly-error

   
s:fcm-shared-isolate

   
s:matrix-api-lite

   
s:multiple-tab-detector

   
s:native-imaging

   
severity::1

Blocker: Broken feature with no workaround or any data-loss. It makes the feature unusable!

  
severity::2

Critical: Broken feature with an unacceptably complex workaround.

  
severity::3

Major: Broken feature with a workaround.

  
severity::4

Low: Functionality is inconvenient.

  
technical-debt

This Issue is a technical debt. Mark issues with this label to have an overview of the technical debts in a repository or group.

  
voip
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Matthias/conduit#58
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?