Friendica VS rust

You might want to look into some of the Facebook-like open-source social networking programs like Friendica, Hubzilla, Libervia, or GNU Social

I think that Friendi.ca is the fediverse equivalent of FB, in the same way that Mastodon is to twitter. https://friendi.ca

In addition to what has been said, you can also use Friendica, another great decentralized alternative (server list). It supports RSS, along with being a regular social network.

facebook being whatever it is would be friendi.ca

Given the similarity to FB, what's the advantage over Friendica or Hubzilla? Both support federation with other servers and can be run as a closed community too.

The Fediverse has many different types of platforms, including video hosting on Peertube or Friendica which is similar to Facebook. Mastodon got the most publicity, but it only uses a fraction of the possibilities that ActivityPub offers.

or https://friendi.ca/

Friendica is powerful, but it's also very complex. If your primary goal for the server is simple discussions about your website, Friendica might be more than you need.

Are there any plans to set up some kind of presence in the decentralized fediverse (e.g. on Mastodon) or a community channel via the Matrix protocol? Services like Mastodon or Friendica are federated social networks licensed under FLOSS-licenses. Those "talk" to each other using open protocols like "ActivityPub" and/or "DFRN". Matrix provides similar functionality compared to Discord and is free (libre) and open source as well. Basing communication on free software can be seen as a political act. ;)

Here's an example of someone citing a disagreement between CRT and shell32:

https://github.com/rust-lang/rust/issues/44650

This in addition to the Rust CVE mentioned elsewhere in the thread which was rooted in this issue:

https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html

Here are some quick programs to test contrasting approaches. I don't have examples of inputs where they parse differently on hand right now, but I know they exist. This was also a problem that was frequently discussed internally when I worked at MSFT.

    #include 

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.

The above Assert<{N % 2 == 1}> requires #![feature(generic_const_exprs)] and the nightly toolchain. See https://github.com/rust-lang/rust/issues/76560 for more info.