What's Changed
Allow most UTF-8 characters in URI path and query. (#715)
This means paring Uris with previously illegal characters according the original RFC will now be accepted. They used to be...
Did you know that #deltachat literally shares cryptographic implementation code with #signal ? Both delta and signal use the ed25519-dalek crate ... Most messengers by now moved their cryptography to #rustlang . We did that in 2019. But in delta also all networking and message formats is implemented in Rust where other messengers (including signal) have a lot of platform specific code still.
I'm currently looking for a remote software development job
I have plenty of experience making software using all sorts of languages, frameworks and tools. Tho I have the most experience with Rust, C++, C#. I also usually do native cross platform applications and backend.
Interested to take a little tour through how #deltachat apps and the #rustlang core library are wired together?
@treefit and @WofWca provide a deep-dive into the history of apps migrating from a C-Foreign-Function-Interface to a #Rust based JSON-RPC mechanism, with entertaining horror stories like how an iOS release some years ago could delete profiles without the user intending it 😬
Foremost this is a quite technical post. Read our other blog posts if you want something more targeted at end users. If you have not yet looked at the Delta Chat source code, you might not know tha...
I think that’s pretty fair. FOSS projects rarely are shining beacons of change management done well.
I’m not sure I understand why so many people “in charge” of adopting/managing #Rustlang in some projects appear to despise the language so much. Feels very counter intuitive to me.
This marks my very first technical blog post, Interning at @servo has been an absolute joy—I’ve learned so much about browsers, Rust, and the open source community, and I’m beyond grateful!
Browsers are simply so much cooler than I ever gave them credit for. It is about halfway through my Outreachy internship, and I have still not fully processed how mind blowing it is that these thin…
Are you into #rustlang and looking for (remote) #work? Want to help #cancer #research? We're planning to add some major features to a CLI app that require some serious software engineering skills. Understanding of stats a big plus, genetics knowledge a bonus. Send me a DM!
It is popular to criticise surveillance/capitalism and to want/work towards a decentralized, secure and diverse communication and media landscape. However, there are real devices, networks, states and stores to navigate, inducing technical and usable-security challenges. #deltachat dev efforts are following a "speculative realism" instead of an idealist approach. We care about cooperative user testing, maintenability and development. We btw moved to #rustlang in 2019 ... when it wasn't cool :)
“We need to get one thing out of the way: Rust is cool. It’s fun.
“It’s tempting to try to sweep this under the rug because it feels gauche to say, but it’s actually important for a number of reasons.
“For one, fish is a hobby project, and that means we want it to be fun for us. Nobody is being paid to work on fish, so we need it to be fun. Being fun and interesting also attracts contributors.”
I can't wait to see how people use default field values in #Rust! It felt like an eternity to land this (specially if we count the years of discussion before the, I believe, 3rd RFC was accepted), but as of next nightly you will be able to write
Initial implementation of #[feature(default_field_values], proposed in rust-lang/rfcs#3681.
We now parse const expressions after a = in a field definition, to specify a struct field default value.
...
Before we start, have a look at this image. It is from a German book from the early Nineties, and it features some very interesting cover artwork. A knight with a cape and a big bushy mustache rides a friendly green dragon.
I’ve been on Fedi for a year now and have fallen in love with the platform, so here’s my introduction! I studied computer science with a focus on RTOS and FP/PL, but I’m about to start my final semester of law school. I’ll be practicing at a boutique firm that primarily handles IP cases once I’m barred. I foilboard and I play way too many rhythm games in and out of the arcade.
I contribute to open source projects where I can, and I write up my experience in my digital garden which I’ve been maintaining for over a year now. It’s also a good place to find usage tips for projects/tools that you might want to use.
My passion for tech also includes privacy, and I’m an advocate for minimizing your digital footprint. GenAI is a scam and its purveyors are causing real harm while they sell it as hard as they can.
Tip You will own nothing, and you will be happy. On my little corner of the internet, I document my adventures in tech and complain about the internet of shit.
I have presented Sliding Sync, a novel, fast and efficient synchronisation mechanism for the Matrix protocol, at the first Matrix Conference in Berlin. It's been many many months that I'm working on this project, and I'm joyful it's now available to everyone for a better Matrix user experience!
The article contains the recording + slides. I've highlighted other talks too.
This release brings rather complete support for the excellent new OpenPGP RFC 9580 (also known as "crypto refresh", or "v6")
RFC 9580 standardizes modern cryptographic mechanisms for OpenPGP: AEAD-based encryption, Argon2, and SHA2 fingerprints for the new OpenPGP v6 key format (v4 keys use SHA1).
Are you a FOSS developer? Do you want to learn #Rust #RustLang? I will give a two hour course on the basics of Rust Saturday, September 28, at 16:00 UTC. This is early evening for Europe, and morning in the US. (I can do another session that's more suitable for Asia, later.)
At the Kernel Maintainers Summit, the question wasn't, "Would Rust make it into Linux?" Instead, it was, "What to do about its compilers?"
The Rust in Linux debate is over. The implementation has begun. In an email conversation, Linux's creator @torvalds told, "Unless something odd happens, it [Rust] will make it into 6.1."
David Airlie, Red Hat kernel maintainer, about the Rust-for-Linux drama: "if people start acting as active roadblocks to work, rather than sideline commentators who we can ignore, then I will ask Linus to step in and remove roadblocks"
Is this *too much*? Historically, having two crate versions in your dependency tree and accidentally mixing types from them led to horribly obtuse error messages (expected `Foo`, found `Foo`). We've slowly chipped away at them, but somethings I fear I might have gone overboard with detail. 😬
Low-level Concurrency in Practice. This practical book helps Rust programmers of all levels gain a clear understanding of low-level concurrency. You'll learn everything about atomics and …
After many years away from the stage, I am back! It looks like I’m accepted to give a talk at the Matrix Conference (2024.matrix.org/) to present ✨ native simplified sliding sync ✨: how it differs from the first version of sliding sync (an experimental project implemented inside a proxy), how we’ve implemented it inside the Matrix Rust SDK etc. Gonna be fun!
I'm happy to announce the release of diesel-async 0.5.
It introduces support for the SQLite backend via a new SyncWrapperConnection type and it provides support for the new diesel Instrumentation interface. Checkout the full release block for more details:
![Rust compiler error output:
error[E0277]: the trait bound `CustomErrorHandler: ErrorHandler` is not satisfied
--> src/main.rs:5:17
|
5 | cnb_runtime(CustomErrorHandler {});
| ----------- ^^^^^^^^^^^^^^^^^^^^^ the trait `ErrorHandler` is not implemented for `CustomErrorHandler`
| |
| required by a bound introduced by this call
|
help: there are multiple different versions of crate `c` in the dependency graph
--> src/main.rs:1:5
|
1 | use b::CustomErrorHandler;
| ^ one version of crate `c` is used here, as a dependency of crate `b`
2 | use c::cnb_runtime;
| ^ one version of crate `c` is used here, as a direct dependency of the current crate
note: two types coming from two different versions of the same crate are different types even if they look the same
--> ~/c-v0.2/src/lib.rs:1:1
|
1 | pub trait ErrorHandler {}
| ^^^^^^^^^^^^^^^^^^^^^^ this is the required trait
|
::: ~/b/src/lib.rs:1:1
|
1 | pub struct CustomErrorHandler {}
| ----------------------------- this type doesn't implement the required trait
|
::: ~/c-v0.1/src/lib.rs:1:1
|
1 | pub trait ErrorHandler {}
| ---------------------- this is the found trait
= help: you can use `cargo tree` to explore your dependency tree
note: required by a bound in `cnb_runtime`
--> ~/c-v0.2/src/lib.rs:3:41
|
3 | pub fn cnb_runtime(_error_handler: impl ErrorHandler) {}
| ^^^^^^^^^^^^ required by this bound in `cnb_runtime`](https://fedi.ml/photo/preview/640/582508 "Rust compiler error output:
error[E0277]: the trait bound `CustomErrorHandler: ErrorHandler` is not satisfied
--> src/main.rs:5:17
|
5 | cnb_runtime(CustomErrorHandler {});
| ----------- ^^^^^^^^^^^^^^^^^^^^^ the trait `ErrorHandler` is not implemented for `CustomErrorHandler`
| |
| required by a bound introduced by this call
|
help: there are multiple different versions of crate `c` in the dependency graph
--> src/main.rs:1:5
|
1 | use b::CustomErrorHandler;
| ^ one version of crate `c` is used here, as a dependency of crate `b`
2 | use c::cnb_runtime;
| ^ one version of crate `c` is used here, as a direct dependency of the current crate
note: two types coming from two different versions of the same crate are different types even if they look the same
--> ~/c-v0.2/src/lib.rs:1:1
|
1 | pub trait ErrorHandler {}
| ^^^^^^^^^^^^^^^^^^^^^^ this is the required trait
|
::: ~/b/src/lib.rs:1:1
|
1 | pub struct CustomErrorHandler {}
| ----------------------------- this type doesn't implement the required trait
|
::: ~/c-v0.1/src/lib.rs:1:1
|
1 | pub trait ErrorHandler {}
| ---------------------- this is the found trait
= help: you can use `cargo tree` to explore your dependency tree
note: required by a bound in `cnb_runtime`
--> ~/c-v0.2/src/lib.rs:3:41
|
3 | pub fn cnb_runtime(_error_handler: impl ErrorHandler) {}
| ^^^^^^^^^^^^ required by this bound in `cnb_runtime`")
