Notices by raboof (raboof@merveilles.town)

@alcinnz what I miss in most 'email patches' workflows is that a contribution doesn't have a URL you can point to that gives a clear overview of the current state: is it rejected or still open, is there an updated patchset that is intended to replace it, are we waiting for the contributor or the project to take the next steps? Also other metadata like tags, assigning people etc.

I didn't see SourceHut address those, though I closed my account there long ago for different reasons.

Still in awe of this incredibly clear visual explanation of how/why Diffie-Hellman key exchange works.

Two parties want to agree on a shared secret, but they don't want a passive observer to be able to learn about it.

https://en.wikipedia.org/wiki/Diffie%E2%80%93Hellman_key_exchange

https://commons.m.wikimedia.org/wiki/File:Diffie-Hellman_Key_Exchange.jpg

#security

That lovely transition from asking yourself:

"Why does this not work?"

to

"Why did this ever work?"

... progress?