| import datetime | |
| import PyKCS11 | |
| from cryptography import x509 | |
| from cryptography.hazmat.primitives.asymmetric import ec | |
| from cryptography.hazmat.primitives import _serialization | |
| from cryptography.x509.oid import NameOID, ExtendedKeyUsageOID | |
| from cryptography.hazmat.primitives import hashes | |
| from cryptography.hazmat.primitives import serialization | |
Compiled by Steven Borrelli https://bsky.app/profile/stefanoborrelli.bsky.social
If you have a community to suggest, this is a growing list, & we'd love to add more.
In the new year, I plan on archiving the repositories below. Because I plan on only archiving the repositories, any project that depends on any of these projects will continue to work. However, I will no longer be accepting issues or pull requests and will never tag a new release.
The reality of each of the projects listed below is that I've almost completely ignored issues and pull requests for
| input: | |
| sequence: | |
| inputs: | |
| - generate: | |
| count: 1 | |
| processors: | |
| - http: | |
| verb: GET | |
| url: ${! env("CONSUL_ENDPOINT") }/v1/kv/${! env("CONSUL_KV_KEY") } | |
| headers: |
| input: | |
| broker: | |
| copies: 1 | |
| inputs: | |
| - http_client: | |
| url: "https://mas.to/api/v1/streaming/public" | |
| stream: | |
| enabled: true | |
| reconnect: true | |
| codec: "delim:\n\n" |
| input: | |
| broker: | |
| copies: 1 | |
| inputs: | |
| - http_client: | |
| url: "https://mas.to/api/v1/streaming/public" | |
| stream: | |
| enabled: true | |
| reconnect: true | |
| codec: lines |
Discord timestamps can be useful for specifying a date/time across multiple users time zones. They work with the Unix Timestamp format and can be posted by regular users as well as bots and applications.
The Epoch Unix Time Stamp Converter is a good way to quickly generate a timestamp. For the examples below I will be using the Time Stamp of 1543392060, which represents November 28th, 2018 at 09:01:00 hours for my local time zone (GMT+0100 Central European Standard Time).
| Style | Input | Output (12-hour clock) | Output (24-hour clock) |
|---|---|---|---|
| Default | <t:1543392060> |
November 28, 2018 9:01 AM | 28 November 2018 09:01 |
At the beginning of 2030, I found this essay in my archives. From what I know today, I think it was very insightful at the moment of writing. And I feel it should be published because it can teach us, Rust developers, how to prevent that sad story from happening again.
What killed Haskell, could kill Rust, too
What killed Haskell, could kill Rust, too. Why would I even mention Haskell in this context? Well, Haskell and Rust are deeply related. Not because Rust is Haskell without HKTs. (Some of you know what that means, and the rest of you will wonder for a very long time). Much of the style of Rust is similar in many ways to the style of Haskell. In some sense Rust is a reincarnation of Haskell, with a little bit of C-ish like syntax, a very small amount.
Is Haskell dead?
This is a collection of the things I believe about software development. I have worked for years building backend and data processing systems, so read the below within that context.
Agree? Disagree? Feel free to let me know at @JanStette.
Keep it simple, stupid. You ain't gonna need it.
