wiktor-k

7 ms·

1.
Inspecting OpenPGP Certificates(openpgp.foo)
1 points by wiktor-k 1y ago|0 comments
2.
by wiktor-k 1y ago
> ² With S/MIME you need to keep your old certificates around to decrypt old mails, so having a new one frequently is not practical You don't need to change your decryption key - the new certificate can use the same decryption
3.
by wiktor-k 1y ago
As described in the post they did in the past: https://github.blog/news-insights/git-notes-display/
4.
by wiktor-k 1y ago
> Is adding them manually to the commit message functionally equivalent to using the `--trailer` flag? Yes. The flag is perfect for scripts but it's exactly equivalent to adding the text manually.
5.
by wiktor-k 1y ago
> I always felt unwrap is preferable for diagnosing issues, which makes it useful in tests. A failed unwrap will point you directly to the line of code which panics, which is much simpler than trying to trace an issue through many layers
6.
by wiktor-k 1y ago
> I have no idea how the 'parser'[1] works I think parsing there depends on the actual value of the current token. So if you assign send to another variable and use that the "parser" will still recognize that it take
7.
by wiktor-k 1y ago
> That section briefly described that, broadly speaking, using unwrap() is okay if it’s in test/example code or when panicking indicates a bug. I've come to the conclusion that even in tests unwraps look ugly. Especially in doc
8.
by wiktor-k 1y ago
Key IDs are based on fingerprints and fingerprints are calculated by SHA-1 hashing the primary key's public key and the creation timestamp. A computationally easy way to influence the fingerprint is to tweak the creation timestamp whic
9.
by wiktor-k 1y ago
It's interesting to hear because Samsung had a Linux feature previously: https://developer.samsung.com/sdp/blog/en/2017/10/18/samsung...
10.
by wiktor-k 1y ago
> In my opinion, the whole concept that a company can break the law but no human can be held responsible is insane. Wait, isn't the board personally liable for their decisions? I'm not a lawyer, obviously.
11.
by wiktor-k 1y ago
> Eventually I couldn't justify buying the console version of a game that I was willing to play on Steam. I do that too but doesn't the same rule apply to Steam, too? (that is if it goes down, you can't download the games
12.
by wiktor-k 1y ago
> now deprecated javascript `with` statement where `with foo; bar` will resolve to `bar` if it is in scope, otherwise it will resolve to `foo.bar`. Technically, in JavaScript it's `with (foo) bar`. Source: https://develop
13.
by wiktor-k 1y ago
Oh yeah, SSH signing is incredible. I've also migrated to it and didn't look back. A couple of differences: - it's possible to specify signing keys in a file inside the repository, and configure git to verify on merge ( https
14.
by wiktor-k 2y ago
Exactly. I was surprised that this one doesn't support multi capture when available.
15.
by wiktor-k 2y ago
It's definitely an excellent example of complex but real typst code. Thanks for sharing!
16.
by wiktor-k 2y ago
I can wholeheartedly recommend them. Excellent introduction to the format, at least it was for me.
17.
by wiktor-k 2y ago
Thanks! Just for completeness apparently Alloy is at version 6 now ( http://alloytools.org/alloy6.html ) and the book is based on version 4 ( http://alloytools.org/book.html ). There's another resource lin
18.
by wiktor-k 2y ago
I've went through the TLA book of Lamport and it was quite approachable. Do you have any specific resources recommendations for learning Alloy and TLA+?
19.
by wiktor-k 2y ago
> I read/worked through Freedman's Statistics a couple of years ago and I walked away from it a different person. Wholeheartedly agree. It took me a year to slowly go through all chapters and this experience really influenced m
20.
by wiktor-k 2y ago
> > When was the last time you had to debug an ancient codebase without documentation or help from a team? > All the time. I guess the minor difference was that it was part of your paid job instead of a huge time sink to get hired.
21.
by wiktor-k 2y ago
The standard is quite new but there are already libs with full support (e.g. the pure Rust OpenPGP: https://fosstodon.org/@hko/113198947595455844 ). One interesting thing is that there's a test suite checking imple
22.
by wiktor-k 2y ago
That's exactly what's happening.
23.
by wiktor-k 2y ago
Yes! Something similar to https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
24.
by wiktor-k 2y ago
> Not being able to flash the firmware is a feature, not a bug. :) It is a feature only if they ship replacement devices in case of issues like this. If they don't and you're left with a broken device then I'd rather count
25.
by wiktor-k 2y ago
Sadly the "source on github" links are broken on https://pretextbook.org/examples.html
26.
by wiktor-k 2y ago
> Something like `foo.bar[function]()` is perfectly valid JS, A minor thing but `function` is a keyword in JS so technically it's not a "perfectly valid JS".
27.
by wiktor-k 2y ago
Just for completeness the html export issue is here: https://github.com/typst/typst/issues/721
28.
by wiktor-k 2y ago
> To be frank I quite like this idea. Can’t we standardize it somehow and add it to other email clients too? Just copying what I said in the other thread: there actually is a standard for that already: https://datatracker.ie
29.
by wiktor-k 2y ago
> Surely there’s an RFC for that right? Indeed, there is: https://datatracker.ietf.org/doc/html/rfc9078 It's used by Delta Chat (IM over email).
30.
by wiktor-k 2y ago
> I've always thought about just making a chat client app using email as the underlying standard. I'm happy to report that this already exists: https://delta.chat/

More ›