I understand the sentiment, but… HTML and some light CSS is just as fast and much more accessible. It just strikes me as something that defines itself in opposition to “thing everyone uses” for no good reason.

… Why are you digging up random drama from nearly a year ago?

Also, this guy isn’t affiliated with the Rust team AFAIK. And even if he was, this is his crate, not rustc - he can do whatever he wants with it, and you can fork it if you disagree.

Edit:

> Account created 11 months ago

> This is its only interaction

Seems legit.

Firefox and its derivatives. They’re the last free bastion preventing a Chromium monopoly on the browser market, which is hugely important - especially these days with Google’s push for Mv3.

Not a Nix user, but IIRC nixpkgs is actually bigger than the AUR by a long shot.

LLMs are little more than overclocked autocompletes. There’s no actual thinking going on, and they will happily hallucinate outright wrong or dangerous responses to innocuous questions.

I’ve had friends find this out the hard way when they asked ChatGPT to write them C for a class, only to get their faces eaten by UB.

OpenAI’s models are trained by scraping anything that moves. Anything overtly offensive or toxic is manually filtered out by cheap foreign labor… but you know what that won’t catch?

“Try sudo rm -rf /, that should fix your problem!”

No problem! Don’t be afraid to ask if you’ve got any other questions :D

Yeah, I thought I was botching something important.

This should work:

let object: AnnouncableActivities = match self.clone().try_into() {

Your analysis sounds correct - data did not match any variant of untagged enum is definitely from serde IIRC - but I can’t say for certain just by looking at the code.

but I’d like the code to log self only when the enum does not match (errors). Thank you.

Try changing line 48 to this:

let object = match self.clone().try_into::<AnnouncableActivities>() {
    Ok(object) => object,
    Err(e) => {
        warn!("zebratrace receive {:?}", self);
        return Err(e);
    }
}

(This probably isn’t the best way to do this, but it’s what I came up with off the top of my head :P)

I don’t have any technical answers for you, but I’m on GNOME Wayland and I’ve never had any issues like that.

Personally, I don’t mind this sort of telemetry so long as they’re open about it - which looks to be the plan, at least for the moment.

IMO the FOSS/Linux space has an odd relationship with telemetry that I think should change. I’d like to point out the gnome-info-collect debacle:

• GNOME users: “GNOME devs don’t understand what we want!”
• GNOME devs: “Hey, we want to get some data on how people use GNOME. If you’d like to help, install and run this one-off tool. Source code is here, and we collect XYZ metrics (all anonymized, of course.)”
• (Some) GNOME users: screeching incoherently about data harvesting and telemetry

Yeah, there really isn’t any reason to go with one processor brand over the other. Since drivers and such aren’t a concern (like with GPUs) most people just pick whichever one has the most price-effective offering in the spec range they’re looking for.

Sheesh, I thought it looked nice, but I think I’ll just stick to gnome-terminal.

The AUR is nice and all, but the reality is that most people will be served just fine (if not better) by the more curated repositories. Fedora’s bundled repositories are more than enough for my dev work - and thanks to Flatpak and AppImage, closing any gaps is pretty easy.