robryk @robryk@qoto.org

@TechConnectify

Hm~ what's your benchmark for what moderation should care about? It seems that clearly you (and others) would benefit from having way stricter moderation, so it sounds like there's raison d'etre of an instance that has such stricter moderation (not only on its own users, but also on remote users by way of instance-wide mutes and blocks targeting individual remote users). (It might be impractical to actually run such an instance due to having to police ~all of fedi, but that sounds like something where "moderation subscriptions" might actually work.)

@Gbudd @freemo

Ah, you mean they _intend to_ be a danger to themselves, right?

@Gbudd @freemo I'm confused by the "not a threat to themselves" part. I can't see a way of interpreting that that doesn't make them one in such situations.

@niconiconi Is that the "let's try to observe the same muon and if we succeed, we know how far and in what direction we are wrt each other"?

@whitequark

Is it orientation dependent?

@TechConnectify @can

I'm sorry, I think I managed to misconvey my question badly.

I wanted to ask about the reason why your experience _with harassment_ over email is better. You mentioned (IIUC) that it's better because it's easier to ignore there; I wonder whether the presumably smaller volume of harassment (in absolute terms) is also important. (If this is the question you were responding to, then I'm very confused by your answer.)

@TechConnectify @can

Is the difference between fedi and email for you mostly a matter of expectations, or does volume of unwanted messages also play an important role (given that you don't publish your email in a very obvious way, I'd expect the volume to be much smaller for email, but maybe I'm way off)?

@Martin__Hope @freistern

Es ist auch immer ein bisschen schlimmer am Weihnachten: die Lüftung ist mehr mangelhaft und Leute fühlen ein grösseres Zwang um das Feier nicht zu vermissen (weil es nur einmal pro Jahr gibt).

@anarchiv for a reason I don't know my city doesn't want any teabags in is compost collection; maybe it's because people won't be able to distinguish though

@grimfrenzy@mstdn.social @delroth if the code of conduct is intended to inform people who might wish to join the community (which I believe they are; otherwise there would be no need to publish them), you also have the case of someone who's scrupulous enough to read it before doing anything else in the community.

@TechConnectify

All will be fine until the whistle randomly stops working and you melt the kettle (speaking from experience :)).

@b0rk

I think I had the same feeling. In both cases I initially found a lot of descriptions aimed to using git/nix for various things, which didn't help at all with building a model of how things work. For git the thing that made me understand it was a description (that I since lost track of) that described all the typical operations in terms of how they affect the commit graph (and described explicitly that commits are actually trees and the diffs are just diffs between them). For nix, the thing that helped me in a similar way was https://nixos.org/guides/nix-pills/, even though they felt less complete.

@b0rk

Note that this breaks down somewhat for flakes that provide something other than a package or a system configuration (a module, or an overlay, or a flake template).

@bascule

Why MAY is so negative? I think I saw it often used to indicate something that's a reasonable thing to do, but not something the RFC wanted to make a recommendation about either way (except to point out that the possibility exists and doesn't contravene any other requirements).

@b0rk

@delroth who might know

In case you're also looking for an answer to your last question alone: if a flake defines an overlay, it can naturally say "use the libc from the nixpkgs I'm being overlaid on" with all the benefits and warts of that.