val @val@oc.todon.fr

Funny how a century is actually defined by the time it takes for Earth to revolve around the Sun times your number of fingers squared

jmap: jean imap

@Seven Tiens c'est rigolo, j'écoutais la BO de l'alpha et de la beta ce matin

@CobaltVelvet ugh no

@bgcarlisle It's the second most voted feature request, but they are too busy adding hashtag completion https://github.com/tootsuite/mastodon/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc

@CobaltVelvet https://tools.ietf.org/html/rfc6797#section-12.1

@CobaltVelvet The whole point of HSTS is to disable this button.

@fulax @thaega +1
Par contre tu vas peut-être perdre les intérêts sur un mois ou une partie de l'année, si tu transfères d'un livret à l'autre.
Et t'as pas le droit d'avoir deux livrets A ouverts en même temps il me semble

Type checkers are just fancy linters

@CobaltVelvet and it SCALES

1519: thou/you
2019: you/y'all
2519: ???

Reminder that storage isn't free. When you post a video/gif on Mastodon/Pleroma/..., your instance stores it forever (unless you delete it).
Also, when you follow an account, your instance will store the media of this account for some time (eg. weeks). For example, following @noisemakerbot may take a few GB on your own instance.

You may not pay it yourself, but your instance admin(s) do.

The only valid orientations are: big spoon, small spoon, both at once, switch, and none.

@jess u gay

@GeoffreyFrogeye "as if the flow is splitting and then merging again on sync point"
Except it splits and merges multiple times per function. And sometimes merges after the function returns. That's the main selling point of Trio, keeping this under control.

"Maybe it’s a thing that you get used to?"
Doesn't mean it's good.

@gordon It's a bit less nice with Ansible because when you double-click the module's name, it also selects "_module"

@gordon Click any module, edit the URL

@GeoffreyFrogeye The whole asynchronous programming.
Yes the context is preserved, but the flow is hard to follow.

In "normal" programming, you have one call stack per thread; a call pushes a frame and a return pops one.
New call stacks (threads) are created rarely.
With async programming, stacks come and go multiple times per function, and when a function returns the stacks it spawned are still alive.
(Trio fixes the latter point though)