Show newer

@hellbeast@bark.lgbt

> Oh and please don't take it for granted that your account can interact with something. Thanks.

Would you mind writing more about this part? I always assumed that the important property deciding whether I'm welcome to interact with something is the interaction itself and not my account's identity.

very unserious 

@whitequark there was once a study where people gave various drugs to web spiders and looked at the webs they spun, so that they could do that in the future to identify drugs by feeding spiders with them.

@lauren

The experiment from the paper involved asking people to search online explicitly. The paper left me confused regarding whether they are looking for effects of being asked to search, or correlation with actually searching (text says former, figure labels say latter).

@zwizwa @dpiponi if that were the case, vibrating the plate should not change the shape. I would expect otherwise.

@polamatysiak

Skąd się wzięło połączenie aktywów państwowych oraz energii i klimatu w jednej komisji? (Z opisu komisji na stronie sejmu wynika, że nie chodzi tylko o aktywa związane z produkcją energii.)

@sgf I am more worried about instances being able to gaslight other instances and that editing plus refusing to sign objects when they are pulled makes proving that it has happened much harder.

robryk boosted

@freemo and presumably on carrying them? (For example in CH access to guns is pretty open, albeit in most cases carries a registration requirement, but carrying them other than to move them between places is mostly illegal.)

Many European people will find what you are saying confusing or misunderstand it. I'd rather phrase it as "unrestricted access and unrestricted carry".

@freemo the point about guns is unclear for two reasons. First is not a phrasing that will mean things to people unfamiliar with the US. Secondly, I can't tell whether you want to say "whatever the constitution of the country says goes", "everyone should have a right to carry guns they could use at ~all times unless sentenced to a loss of that right", something in-between, or something significantly different.

@psn @danluu

Why doesn't that work in TV? This is the format of all(?) the Poirot movies starring Suchet.

@sebastian @ftdl

Gdyby administracja miała taki feature do dyspozycji, to mogliby go użyć tymczasowo aby jednocześnie (a) zablokować spam od nowych kont (b) nie wpływać na komunikację użytkowników, którzy już kiedyś się ze sobą komunikowali.

@sebastian @ftdl

Może przydatnym featurem byłoby blokowanie wiadomości od profili z instancji A, od których nie widzieliśmy żadnej wiadomości przed momentem B (lub o których ta instancja twierdzi, że są młodsze niż B)?

@patcharcana

Vifon might also be a well-known placeholder for generic instant anything.

@sethrichards @b0rk

Doesn't it make things ~infeasible sometimes? E.g. if you have a merge of a bunch of changes on the left and a bunch on the right, and the bug is introduced in 5th change on the right, but only active in presence of some changes from the right side, bisect can't help but point at the merge commit as the culprit, which isn't very helpful in finding that 5th commit on the right side.

@lachlan @b0rk

This also includes using rebase to edit history: doing `rebase -i` in a way that e.g. moves things around a merge is one of the things where I'd rather use lots of `git cherry-pick`.

@IAAA @AkaSci @NSFVoyager2

Vacuum is a pretty good insulator (you only radiate jest away), so hearing is not as expensive as one might think.

@b0rk For the case with merges I don't know of anything that's better than `log --graph` and I also don't really know how I'd want to see the cases with weird merges printed.

For the case with no merges, have you looked at `git log --topo-order --graph`? If there are no merges _at all_, the graph will be a Y-shaped tree with the contents of each of the left and right box grouped together. I've found the Mercurial equivalent (I don't remember the exact incantation for it, I have an alias for it at work) pretty readable. Sadly, I don't know how to get git to (a) make it obvious what goes in left and right box and (b) not make a huge mess if there are any merges whatsoever.

@b0rk Do you want to see plain lists of commits, or some hints to their relationships too? (This seems to matter most for the bottom box, which might not be "single headed" if there are commits that were merged into both branches at different points in their histories.)

Show older
Qoto Mastodon

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