!GsmxjHfeAYLsTEQmjS:nixos.org

Matrix Meta (Nix)

626 Members
Discuss your proposals for the Matrix space here, before suggesting them in #matrix-suggestions:nixos.org178 Servers

Load older messages


SenderMessageTime
23 May 2025
@gnu_ponut:matrix.orgGnuxie 💜🐝
In reply to @k900:0upti.me
Yes and I'm not even convinced it's a good idea
it's a really good idea and the only bad thing about it from my perspective is that it is not included in event auth. So doesn't go far enough yet.
09:17:53
@gnu_ponut:matrix.orgGnuxie 💜🐝it's also fail unsafe atm09:18:51
@emilazy:matrix.orgemilydo you not share my concerns?09:50:56
@gnu_ponut:matrix.orgGnuxie 💜🐝 I didn't read them, sorry 10:00:51
@gnu_ponut:matrix.orgGnuxie 💜🐝 it's a relatively small feature that will take time for servers to adopt yes. but the only have to implement the event forwarding and not the policy server itself. 10:01:37
@gnu_ponut:matrix.orgGnuxie 💜🐝 scanning content I think is out of scope and not useful 10:01:57
@gnu_ponut:matrix.orgGnuxie 💜🐝 so I don't see that as a concern 10:02:07
@gnu_ponut:matrix.orgGnuxie 💜🐝 I'll show why 10:02:10
@gnu_ponut:matrix.orgGnuxie 💜🐝https://marewolf.me/posts/draupnir/25/02.html#priorities-a-focus-on-on-boarding-users10:02:31
@gnu_ponut:matrix.orgGnuxie 💜🐝 * 10:03:49
@gnu_ponut:matrix.orgGnuxie 💜🐝 the bigger issue is just proactively getting access to events to stop flooding 10:04:08
@gnu_ponut:matrix.orgGnuxie 💜🐝 from new users 10:04:17
@emilazy:matrix.orgemily(these three messages, FWIW)10:05:11
@emilazy:matrix.orgemilyah, but I guess you read them :)10:05:19
@emilazy:matrix.orgemily"but the only have to implement the event forwarding and not the policy server itself" → that's precisely the concern wrt centralization/SPOF right?10:05:33
@emilazy:matrix.orgemilyhm, ok.10:05:49
@emilazy:matrix.orgemilythen the Matrix blog presentation of the feature confuses me somewhat10:05:59
@emilazy:matrix.orgemilysince they explicitly say "In short, they're servers on the internet where you can send events to and have them be checked for spam/illegal imagery/etc."10:06:31
@gnu_ponut:matrix.orgGnuxie 💜🐝 yeah they intend to use them differently to me I think 10:06:49
@gnu_ponut:matrix.orgGnuxie 💜🐝 and the point is they enable people to make tools for proactive checks 10:08:00
@gnu_ponut:matrix.orgGnuxie 💜🐝 whether those tools are made is something else 10:08:10
@gnu_ponut:matrix.orgGnuxie 💜🐝 since fundamentally it is impossible in matrix atm 10:08:24
@emilazy:matrix.orgemilyright. well I agree that there needs to be a blocking kind of moderation and that reactive approaches are hopeless, yeah10:08:26
@gnu_ponut:matrix.orgGnuxie 💜🐝 * since fundamentally it is impossible in matrix atm without policy servers 10:08:37
@emilazy:matrix.orgemilyin my view, it's not really a good thing for NixOS that rooms are independent of homeserver10:08:46
@emilazy:matrix.orgemilythe split-brain issues we've had, and the reactive-only moderation, are things that wouldn't be an issue if nixos.org was authoritative for our rooms10:09:10
@emilazy:matrix.orgemilyand the benefits we gain from federation are from users being able to be on different homeservers, not the rooms being distributed across homeservers10:09:28
@emilazy:matrix.orgemilyof course this may not be the case for all communities10:09:35
@gnu_ponut:matrix.orgGnuxie 💜🐝 well that's another argument entirely and we can't go from saying this feature will take too long to roll out to fundamentally changing the protocol x3 10:11:31
@dgrig:erethon.comdgrigThe (main/only?) benefit of the current architecture is the fact that the nixos.org HS isn't a SPOF. Obviously, with this also come all the issues you mentioned (split brains, abuse, etc).10:11:47

Show newer messages


Back to Room ListRoom Version: 6