Show newer

@whitequark

If you are still curious about the mechanism of the weirdness: Can you tell how? (Did it get pushed to it? Did it fetch it? From A or from C?)

@whitequark

My very wild hypothesis is that for some reason B doesn't consider these messages (I forgot Matrix's term for nodes-in-the-room-history-dag) valid. Perhaps A changed its mind about its signing key? But I don't know why B haven't fetched them from C, trusting them because C considers them valid. I will need to reread how validity determination works, but now I need to sleep, so it has to wait until tomorrow. (I realized I don't get how you can at the same time prevent C from potentially impersonating A's users and at the same time accept nodes from C that mention a node from A that appears invalid as a parent.)

@whitequark

:(

I would really like to have more Matrix debugging tooling...

@whitequark

I wonder what happens if A keeps changing its mind about what its signing keys are.

@whitequark

How do you know that it didn't get federated directly from A to C? (Even if it did, it would still be a very weird failure mode.)

@mcc

That _is_ really surprising.

Ah, and you did try replacing the dialer to no effect already. :/

@mark

Huh, I'm very surprised that you find this line odd (I don't think I've seen this opinion in the past). I would appreciate if you answered a question or two so that I can understand it better (but do understand if you don't wish to).

The reason I find this line very natural is that I think in terms of which node is intended to be able to speak for which entities, especially that those entities are named in a way to remind us of that relation (domain in URLs, domain/instance part of a fedi ID). Do you think that it makes more sense to keep track of a more vague trust (as in, "that node is rather trustworthy") in general, that the mapping between nodes and entities is insufficiently natural, or something else I can't easily see?

sundog's hot take on fedihugging 

@djsundog

A potential issue is that it might be unclear who was nefarious: the originating instance or the server whose page we're previewing. I don't think it's very significant though (compared to e.g. the amount of shady and somewhat-hard-to-assign-blame-for stuff one can do with versions of a toot and sending them selectively to instances).

@mcc

I see another potential usecase: telling the user that they need to raise the volume if they hear nothing, because someone is probably trying to speak to them now. I usually set my call volume to minimum reasonable for the place I'm in and then when I call someone from a totally different location I somewhat nervously await the ringing tone so that I can adjust the volume (and when the ringing tone is late I run the whole "look at the screen to see what the problem is" dance).

@mark @mcc

In the sense that someone other than your client, your own instance (both of which you kind of need to trust anyway), and the actual site that's linked to (who's the source of the content, so the preview must trust it) can manipulate it.

The site showing different contents to different users is another issue that I agree exists and can cause similar problems _for malicious linked-to sites_. For nonmalicious ones consider e.g. a post expressing outrage at something bbc published with a link to the "article" on bbc with a helpful "preview".

@mark @mcc

It's a terrible idea to trust that preview though.

@dangerdyke @yassie_j @winter

Out of curiosity, what's the potential harm? (Is it ~biological or ~chemical?)

@timorl Uh... it does nothing? (I assume it's supposed to rotate stuff.) My browser's firefox, the extensions that seem potentially relevant are ublock origin and zotero connector. Nothing in the JS console, except for godot's welcome message, some complaints about audio mix rates, and a complaint about long-running stuff in a context that blocks rendering.

@_thegeoff

Oscilloscopes from the 80s, even DSOs, are in at most tens of thousands of components range (most of it in SRAM). Mine, apart from discrete components, has 74-series TTL logic chips, some opamp-like ICs, and 8kB (or 16?) of SRAM.

@timorl 4? The one where you have to avoid mixing in black

Ah, PSA: if you do actually collide with a bat, check very thoroughly whether (a) you got scratched in any way (b) you got your face in contact with the bat. If either happened, wash the scratch/your face thoroughly and urgently visit a doctor due to the risk of rabies.

Show thread

I think I nearly collided with a bat today. I was riding a bike along Sihl just north of Sihlcity (the path is between a small forested hill and a river with a highway overpass over it; it's sparsely lit with streetlamps) and saw (~single frame only, because of timing wrt my blinking) a dark concave-sided diamond shape in front of me and felt a gust of wind.

It's not that surprising, given that a bit further north friends of mine would semi-regularly notice bats over the rive (and I did once or twice), but the near collision is surprising given my very predictable motion.

@Datterich @koteisaev @baldur

Note also the "Agnieszka" in the screenshotted list (it's a pretty common Polish first name, so I guess there is more than one Icelandic woman with it).

robryk boosted

“How do you accidentally run for President of Iceland? | by Anna Andersen”

Glad somebody wrote about this because it’s an objectively hilarious UX case study

(And they just announced that eleven people managed to get the requisite number of endorsements in time) uxdesign.cc/how-do-you-acciden

Show older
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.