robryk @robryk@qoto.org

Why do ~all mice and trackballs have keys with short travel? For keyboards, ~most custom builds use switches with large-fraction-of-cm travel. For mice and trackballs, I haven't seen a single custom build (not ploopy, not a few other trackballs or mice I've seen) that uses something other than microswitches, perhaps with a level arrangement, that gives travel in the range of a single mm.

What would be wrong with a mouse (or a trackball) that used mechanical keyboard switches for buttons?

#mechanicalkeyboards #keyboard

https://en.wikipedia.org/wiki/Category:Filkers is a very varied collection of individuals

@moonbolt

The original post was complaining[*] about basically a search engine that allows one to find every instance who blocks some particular instance. This is not what I would want to have: I would want to have something that answers the question of "does instance X block my instance". IIUC the undesired thing was aggregating that across all Xs and making that aggregation easy to access (i.e. easier than doing a web search for "inurl:about/more <instancename>" and manually grepping through results).

[*] for some value thereof, possibly weird word choice

> It's not too much trouble to respond into the void occasionally, is it?

I've just counted: happened to me 10 times last month, including 1.5 times when I spent nontrivial time and expected (and still expect) that the person would be interested in my response and would want to respond in a way I would find interesting. I'm not sure if that's occasional~

@moonbolt Hm. So, I was thinking of making something that would let one figure out if a particular instance blocks their instance[*], because I end up responding into the void once in a while (someone boosts a post from an instance that blocks mine and I spend time writing a reply to it; even if I always checked /about/more of the appropriate instance they sometimes fail to mention suspensions/fail to mention all suspensions there). Would you personally consider such a thing abusive in any way?

[*] I was thinking of two ways:
a) making use of the way "suspending" works in Mastodon: the instance considers signatures from the blocked instance invalid -- so just send some random public post from my instance there and see what's the response,
b) try to find a post on the maybe-blocked instance that should have appeared in a thread on the maybe-blocking instance and see if it's actually visible via a web request there.

@shaunh Maybe? Generally you don't care about neutral if the line ends in a transformer (or multiple), because you can use a transformer that has inter-phase windings on input. @puniko

@puniko What's the deal with the power line on the left (not the one for the railroad, but one of the two ones above it)? It has four conductors (not counting the grounded one at the top). Is it one three-phase line with a spare conductor or what?

@wolf480pl Sometimes the language doesn't allow you to tell the compiler something you know that is required to do its job well. Examples in C{,++}:
- a value pointed to by a ref cannot change
- a ref cannot alias with a global,
- a parameter cannot alias with one other parameter, but can with another parameter,
- these two pointer do point into the same region, but they are manipulated in such a way that _they_ never point simultaneously at the same thing (or something similar that allows one to implement pointer chasing without spurious reads, like "this pointer is always ahead of that one") (you can't do this if you get such two pointers as function parameters),
- "I don't care about floating point addition not being associative" (-ffast-math and friends are an attempt to patch this, albeit in a very clunky way that can cause absurd errors sometimes).

@dch

> - with no glaciers, there is no steady water supply during summer growing season

Are you saying that snow is not replaced completely by other precipitation, or that not-snow causes a much more bursty flow downstream (or both)?

@opensourcestudio Wouldn't rooms that used to contain any person with a different homeserver be preserved? If so, maybe this would be a way to preserve them all?

@niconiconi Is this similar to how owls muffle the sound of their wings?

@deerbard

`--description` (see https://github.com/ihabunek/toot/blob/master/toot/console.py#L300)

@moonbolt What would be the trigger for locking/unlocking?

@rogatywieszcz

`--description`: https://github.com/ihabunek/toot/blob/master/toot/console.py#L300

@feditips It's also helpful to consider which kind of block you want to apply: they have different consequences, sometimes even preventing two users who want to talk to each other (and don't care about their posts even being not visible to anyone else) from doing so.

@wizzwizz4 Oh, so this has some bizarre semantics: it doesn't just mute the subtree "originating" from the message you use, but does mute siblings and cousins too. And yet is not a per-conversation option, but a per-sent-message one. @feditips

@niconiconi How is then "content" different from "data"?

@feditips What does this do exactly? Prevent the reply tree of the message you've muted from from appearing in your timeline? Or does it also prevent replies to things upthread (i.e. siblings or cousins) from appearing too?

I'm also confused why this action is only available on my posts. This limitation doesn't seem desirable (I might want to mute a conversation that someone cc-d to me, without posting anything), so I would expect the limitation to be caused by the mechanism. However, I would guess that the mechanism behind it is "don't show anything that has <this post> upthread", which shouldn't need such a limitation. Am I misunderstanding how this works?