https://github.com/xero/covcom
looking for an open source, self hosted, signal style messenger alternative? checkout out #COVCOM, the covert communications group messenger, with both web-based and cli clients.
#XChaCha20 #MLKEM768 #Ed25519 #BLAKE3 #SPQR #E2EE #Ephemeral #N_party #chat
GitHub - xero/covcom: Covert communications for private group conversations. Share an invite, talk, close the tab, and it's gone. End-to-end encrypted with post-quantum cryptography, so the messages stay private today and unreadable to the computers coming tomorrow.

Covert communications for private group conversations. Share an invite, talk, close the tab, and it's gone. End-to-end encrypted with post-quantum cryptography, so the messages stay private tod...

GitHub

The performance of blake3 multithreaded is very impressive:

hmac-sha256 1.00 GB 0.327s <-- with hw accelerated sha256

blake2b-256 1.00 GB 0.952s <-- pure sw, used in borg 1.x

blake3 1.00 GB 0.442s <-- pure sw, single-threaded

blake3-mt 1.00 GB 0.078s <-- pure sw, with MT.

#blake3 ๐Ÿš€ ๐Ÿš€ ๐Ÿš€

Have pushed 0.9.5-dev branch to codeberg of foxing ( https://codeberg.org/aenertia/foxing/src/branch/0.9.5-dev ) in preparation for release tagging. A LOT of features and a couple of bug-fixes now the packet/file processing engine has stabilized ; including Semantic Routing to Parsers for Metadata Extraction and in-path Binary analysis using local ORT/BERT models ; letting you get semantic search powers for free when you copy something with foxingd/fxcp #linux #filesystem #bert #vectordb #postgres #xfs #stratis #blake3 #localllm
foxing

`foxing` (formerly xfs-mirror) aspires to be a production-grade, eBPF-powered replication engine for Linux filesystems (XFS, Btrfs, F2FS, Ext4). It captures filesystem events in the kernel and replays them asynchronously on a target directory, providing near real-time mirroring with robust consis...

Codeberg.org

๐Ÿ“ฆ Efficient file syncing for massive datasets? Forget classic rsync!

โšก #BLAKE3 hashes instead of timestamps โ€“ hash 70GB in just ~20 seconds thanks to multithreading across all CPU cores

#DevOps #Linux #SysAdmin #OpenSource #FileSync

๐Ÿ“Š Algorithm comparison for 70GB:
- BLAKE3: ~20 seconds
- MD5: ~1.5 minutes
- SHA256: ~4.5 minutes

๐Ÿ” The trick: Create a hash baseline, compare with `comm -13`, then use `rsync --files-from` to transfer only actually changed files

๐Ÿงต ๐Ÿ‘‡

๐Ÿฆ€ Rust weekly log

This week:

๐Ÿ“ก RustPulse
First OpenTelemetry + Jaeger integration in place (phase 1/3).
https://github.com/VinEckSie/rustpulse

๐Ÿ” Sealed in Rust
New chapter on cryptographic hash functions: SHA-2, BLAKE3, and beyond.
https://vinecksie.github.io/sealed-in-rust/02-core-primitives/02-02-crypto-hashes.html

#Rust #SystemsProgramming #Observability #OpenTelemetry #Jaeger #Cryptography #BLAKE3

GitHub - VinEckSie/rustpulse: โšก Secure, offline-first telemetry engine in Rust โ€” real-time metrics for edge devices via Axum, gRPC, and PostgreSQL.

โšก Secure, offline-first telemetry engine in Rust โ€” real-time metrics for edge devices via Axum, gRPC, and PostgreSQL. - VinEckSie/rustpulse

GitHub

Research topic of the day: Choosing a #hashfunction for 2030 and beyond - https://kerkour.com/fast-secure-hash-function-sha256-sha512-sha3-blake3

TLDR: #blake3 is cool & let's hope it picks up steam, #sha512 is the winner for integrating into current projects.

#research

If you're heading to #RustConf25 and want to chat about #iroh, #p2p, #blake3 or #QUIC, say hi to https://bsky.app/profile/b5.bsky.social. He'll be there!
b5 (@b5.bsky.social)

Worker crayon at n0.computer, we make iroh.computer

Bluesky Social

@glepage

...what I really cannot comprehend is why there is no #BEP to migrate #BitTorrent to #CDC and #BLAKE3, and I guess I can't (won't) ask because last time I checked signing up to their mailing list required a #Google account

Today I got to know that #nix 2.27 added #blake3 support and proper submodules and lfs support to #flakes! ๐ŸŽ‰
Other than supporting legacy systems or implementing cryptographic password functions that *should* be slow, why aren't your teams using GNU or BSD tar with #zstd compression and #xxHash or #Blake3 checksums yet? If time is money, please stop wasting either with legacy algorithms when there are faster, more secure, and more trusted options currently available.