@kate@social.treehouse.systems
Post #1228344
2026-03-14 18:13 UTC
i figured it makes the most sense to just use OCM as the underlying mechanism, because nextcloud already implements and uses it. luckily in the case of federated sharing the system doesn't really work like a distributed system, because there is always one node that has the correct data (the node where the share was initiated from) and the others just follow it. the data getting out of sync is not really an issue, especially because security relevant things will always be delegated to the origin instance, thus not relying on trusting other nodes to apply the restrictions correctly.
Replies (2)
-
@kate@social.treehouse.systems 2026-03-14 18:17
still very interesting to see how this plays out. i really need to make sure it's the best we can have, to avoid needing any (breaking) changes in the future. also a little scary ahh
-
@kate@social.treehouse.systems 2026-03-14 19:36
also i'm so happy to finally fix the sharing and federation mess in nextcloud. while it's works surprisingly most of the time (if you don't hold it wrong), it's also some of the worst code and architecture i've ever seen