pol, drm
The second one is worse than first one, because second one has larger vulnerability windows (potentially even unlimitedly large).
Yeah, first situation is basically the same thing as SafetyNet but with socially important properties switched around.
In the second case I mean an HSM that's running somewhere (and has standard rules for being asked to perform operations with keys it stored, no attestation involved there), but can migrate/duplicate itself to a different host (so that it doesn't die if the host dies). That requires some reason to trust that whoever we ship off a copy of all our secrets to will behave just as we behave (or rather, whoever has the session key that will decrypt the secrets we're shipping out).
pol, drm
I agree on undesirability, but want to point out two situations when it can be a security feature (if there wasn't a stream of exploits against the variants I know of): selling computational power without ability to see what the buyer is doing and poor man's cloneable HSM with potentially much more complicated logic inside (which would export keys, but only to instances of itself running someplace else).
Maybe driving an acoustic guitar like a speaker? (The more interesting way that I haven't seen done would be to do it via conductive or ferromagnetic strings. Vibrating the body could still be interesting on its own, because you ~won't be able to excite some modes from some locations.)
You technically could do that with ActivityPub (each post has a replies collection that whoever hosts the post can control) and technically can have a client that will refuse to show replies that aren't present there.
Sadly (I think), replies to replies would be under the control of the first replier (as opposed to OP). For that reason I think that every system that has the property you want needs to treat posts and replies as different kinds of entities.
@lauren @FLGLchicago @hackbyte
What properties would a good term have?
Hm~ yes, this is not a situation where one needs to coordinate, so just doing that works.
Sorry for rambling, I should probably go to sleep.
But that's also allowed in the byzantine general's problem? There's no restriction on what messages can be passed around there.
If you can only do that in pairwise conversations, sussing out malicious people who say different things depending on who they speak with (and claim falsely what they've said to/heard from others) is nontrivial. Having a way to make a statement that ~everyone can see (and that no one will see a different version of, and that everyone can trust to have this property) makes that much simpler.
The communication has to happen under Byzantine fault conditions sometimes though, given that people will sometimes be maliciously dishonest in different ways when interacting with different people. But I think I overestimated how much worse this makes things, because after all everyone has an equivalent of a broadcast primitive.
Fair point; generally being more proactive about getting the other side's story is both generally good and completely(?) mitigates this problem.
IRL it's very obvious that the complaints are hidden from the target of the complaints. The situation I'm trying to paint is one where this is not obvious to others (because the complaints are ostensibly public, and yet not available to the target of the complaints specifically).
I guess you expect people not to treat "complaint is public" as "B likely has seen the complaint", and explicitly talk to B?
How does this model handle the case of person A making otherwise-public-but-not-available-to-B disparaging statements about B? (I assume -- potentially incorrectly -- that the A's lack of consent for B to read the statements is not publicly visible, because that's typically the case.) (I can imagine the way this usually happened on Twitter -- that ~everyone knew this to be a possibility and thus interpreted B's silence differently -- but wonder if you have some other possible solution in mind.)
Dla każdego epsilon znajdziesz takie N, że z prawdopobieństwem 1-epsilon ta wartość będzie bliżej niż epsilon do spodziewanej liczby.
2 nie jest prawdziwe w tej formie. Prawdziwe jest, że przy odpowiednio dlugich seriach rzutów c(I)/n będzie dowolnie blisko 1/6, ale c(I)-n/6 nie będzie się zbliżało do zera (tak naprawdę będzie rosnąć jak sqrt(n)).
I think this is a _very_ weird way to say "don't turn on without water inside/in the circuit". I suspect that the reason for the weird phrasing is that it was written by someone who didn't know English apart from technical vocabulary (so knew how to say anhydrous, and used "boot" in the sense of "booting").
The amusing (and slightly absurdist) way in which golang deals with that is that hash of a nan is a random value. See https://github.com/golang/go/blob/097b7162adeab8aad0095303aff8a045bbbfa6e0/src/runtime/alg.go#L115
Aren't you missing one `no` emoji or an equivalent? (Anhydrous means devoid of water.)
My main worry would be whether there isn't something tricky around horizontal operations (e.g. that ones that cross some boundary are much slower, or that only a few of them are passably fast).
I enjoy things around information theory (and data compression), complexity theory (and cryptography), read hard scifi, currently work on weird ML (we'll see how it goes), am somewhat literal minded and have approximate knowledge of random things. I like when statements have truth values, and when things can be described simply (which is not exactly the same as shortly) and yet have interesting properties.
I live in the largest city of Switzerland (and yet have cow and sheep pastures and a swimmable lake within a few hundred meters of my place :)). I speak Polish, English, German, and can understand simple Swiss German and French.
If in doubt, please err on the side of being direct with me. I very much appreciate when people tell me that I'm being inaccurate. I think that satisfying people's curiosity is the most important thing I could be doing (and usually enjoy doing it). I am normally terse in my writing and would appreciate requests to verbosify.
I appreciate it if my grammar or style is corrected (in any of the languages I use here).