robryk @robryk@qoto.org

@m0bi13

Z podobnej beczki, qmapshack jest wygodnym narzędziem do tworzenia/edytowania tras w gpx. (Wspominam o tym, bo zdarzało mi się używać umapa do rysowania tras; teraz raczej używam qmapshack do tego i później umapa żeby je komuś pokazać.)

@anedroid nie chodzi mi o to jak działa, ale o opis tego skąd napastnik zaczyna i jakiego celu ma nie móc osiągnąć, który normalnie może.

Jeśli napastnik zaczyna z możliwości wykonywania kodu jako podstawowy użytkownik, to czemu np. nie może wsadzić do $PATH katalog ze złośliwym midsu, które następnym razem gdy je uruchomisz wyśle mu wszystkie dane z konta-cienia?

@anedroid opisz proszę przed jakimi napastnikami to ma chronić

@sgf @ancientjames

Were there lawsuits when last provider of 2G stopped being one?

@jannem @VE3RWJ @mjg59

Do you see any part of the instrumentation that's close to your eye (e.g. the blade)? I don't doubt that you see parts that are further away.

@mjg59 @VE3RWJ

Huh. I just took a piece of black sewing thread (should be about as visible as a small gauge needle, I'd guess) and managed to poke myself in the eye with it without noticing anything other than slight distortion in field of view in the process. When I hold it hanging down from my eyebrow, I can't notice it's there at all unless it moves.

Do you think this is somehow unrepresentative or that I'm different?

@VE3RWJ @mjg59

Note that you literally can't see anything that close to the eye. Normally the reason you reflexively close the eye and flinch is that something touches your eyelashes; I'm not sure if you'd have any reflex if something touched your eye without touching eyelashes.

@kuba Nieno, chyba nie twierdzisz że zabarwienie ich na nowo nie zmienia koloru?

@kuba

Może używają tego do rozpoznawania ciebie z większych odległości? Z większych odległości dobrze widać kolor, a gorzej cokolwiek związanego z krojem, więc to pasuje do ich błędnego założenia.

(Wydaje mi się, że u mnie rozkład tego, które ubrania i jakie ich własności pamiętam pasuje do tego. Np. kojarzę kolor czepka i ramiączek kostiumu pływackiego większości moich znajomych, podobnie kolor ubrania na narty. Słabiej kojarzę kolory np. spodni, które typowo noszą.)

@matt @b0rk

Pedantic investigator ("let me see what this thing actually does and what edge cases it has") is related but am not sure if identical.

@b0rk

Question answerer strongly reminds me of https://en.wikipedia.org/wiki/The_Steerswoman

@rysiek

A way of using it that I found not irritating was to use it for questions of examples of things where (a) you are reasonably convinced they don't exist (b) it's easyish to verify if they do (e.g. molecules that contain helium). You don't run the risk of being fooled by its overeloquence on account of (a), and you don't end up unsure on account of (b). (The way (b) works is usually by way of you looking for a name of a thing that you can then look up.)

@avolha

Nie rozumiem tak dużego wzburzenia na temat tego, że atak DoS zatrzymujący pociągi da się przeprowadzić np. z samolotu. Jeśli ktoś by to uczynił to (a) bardzo łatwo byłoby stwierdzić, który samolot to robi (b) mógłby spowodować większe zamieszanie nadając np. fałszywe sygnały GPS.

@danluu

Might some of them be unable to see what's in front of you (as in, unable to see that you can't overtake the obstruction)?

@rq

BTW. https://github.com/google/wuffs/blob/main/doc/spec/rac-spec.md is an example of a spec that describes what a decoder must do, in a case where there are nontrivial constraints on it (that serve to make sure that you can't construct a compressed file that will decompress differently depending on whether you read from the beginning or not).

@rq

Well, it's a spec for the format. It says things like "a valid ZIP file MUST ...", but doesn't specify the behaviour of the parser (can the parser assume that this holds? must the parser fail if it doesn't hold? what if it doesn't hold in a part of the file the parser wouldn't even ordinarily read? etc.).

Quick grepping through those appnotes doesn't reveal any expectations around path other than ones in 4.4.17, which don't specify anything about uniqueness (nor about interpretation of nonuniqueness, but that is not something I'd expect in a specification of format as opposed to parsing).

@rq

Why isn't this just <insert archive format you like> base64-encoded?

@rq

Is the zip format standardized, or parsing of zips? Without looking I expect the former, because there are multiple ways to parse a zipfile: there's the infamous "does first or last entry for a given path count" problem (exacerbated by the distinction between "first in the directory in footer" and "first in byte order in the file itself").

@kravietz @EugeneMcParland @vfrmedia

The unprotectedness of the mechanism is (or maybe was) IMO a feature: it's hard to conceive of a way in which e.g. some trains obey a stop signal while others don't (as long as they have their radios set to the locally-correct channel). The extent of testing of train-local systems consists of sending the signal on a test channel (and making sure a test receiver acknowledged it) and asking a test transmitter to send a signal on the test channel (and checking that the appropriate actuation happened). If there was any authentication, then there'd be more potential failure modes.

@grrrr_shark

Sure, I get that _this_ is very different (both in mean and variance). But aren't the effects of trying to stay well above the-value-that-got-randomized-for-today similar? (Or are you saying that for many people this range starts so high that they never get to experience trying to stay in it for more than a day at a time?)