I won’t use threads, but the Fediverse is relatively small. It would suck if they managed to play dirty tricks and steal a large fraction of current fediverse users.

The advantage of the Fediverse is exactly that, that each instance can decide if they federate or not. The thing that I’m wary of is a renewal of Embrace, extend, and extinguish. I’d like to think that Zuckerberg isn’t going to try playing dirty tricks, but we’ll see what happens if and when Threads ever becomes really successful.

This was recognized at least as far back as 1988:

https://en.wikipedia.org/wiki/Four_Horsemen_of_the_Infocalypse

Browsing with JS disabled by default and expecting most sites to have basic functionality like “display this text”

Whether this guy should be forced to turn over his passwords or not:

https://www.theregister.com/2017/03/20/appeals_court_contempt_passwords/

The appeals court found that forcing the defendant to reveal passwords was not testimonial in this instance because the government already had a sense of what it would find.

Neat, thanks!

It would be nice if communities that are similar enough could “share” a comment thread, so you don’t end up with comments scattered over many different communities for the same link. The mods could toggle something in the settings and say “This other community is good and we’ll be OK sharing posts with them”. You also wouldn’t have to explicitly crosspost.

Some apps will collapse those into a single post, but not all of them, and not all the time. It would be nice if that were better.

It would be nice if there was a way to handle instance/user migrations. If an instance gets their domain name taken away, there’s no way AFAIK for the admin to say “Here’s our new location, with a verifiable signature”. Likewise there’s no way for a user AFAIK to move their account with a verifiable signature that the new one is still them. Ideally this could all happen automatically with signatures getting synced automatically and all that.

I’m sure it would be a lot of work and no idea if ActivityPub would get in the way, but it would give people a lot more assurance that they didn’t pick a server that will screw them over by going down.

What is !steamdeck@lemmy.world doing over with the red dots 🤔

What parent is likely referencing

TBH I wonder if the current Microsoft is capable of executing that here. I don’t believe in a “changed” MS, but Linux is eating the world, and MS doesn’t really care about Windows much anymore. Azure happily runs Linux VMs

The collect’s in the middle aren’t necessary, neither is splitting by ": ". Here’s a simpler version

fn main() {
    let text = "seeds: 79 14 55 13\nwhatever";
    let seeds: Vec<_> = text
        .lines()
        .next()
        .unwrap()
        .split_whitespace()
        .skip(1)
        .map(|x| x.parse::().unwrap())
        .collect();
    println!("seeds: {:?}", seeds);
}

It is simpler to bang out a [int(num) for num in text.splitlines()[0].split(' ')[1:]] in Python, but that just shows the happy path with no error handling, and does a bunch of allocations that the Rust version doesn’t. You can also get slightly fancier in the Rust version by collecting into a Result for more succinct error handling if you’d like.

EDIT: Here’s also a version using anyhow for error handling, and the aforementioned Result collecting:

use anyhow::{anyhow, Result};

fn main() -> Result<()> {
    let text = "seeds: 79 14 55 13\nwhatever";
    let seeds: Vec = text
        .lines()
        .next()
        .ok_or(anyhow!("No first line!"))?
        .split_whitespace()
        .skip(1)
        .map(str::parse)
        .collect::>()?;
    println!("seeds: {:?}", seeds);
    Ok(())
}

Seconding as better for RSI. Plus they work anywhere, you don’t need specific surfaces for them

Good, that’s the only way people like that will change

There’s a whole series of these. Not sure where the trail ended, but here’s one of the iterations of this site:

https://perfectmotherfuckingwebsite.com/

Get pissed at NVIDIA. They’re the problem.

deleted by creator

You probably wouldn’t be committing this, unless you’re backing up a heavily WIP branch. The issue is that if you’re developing locally and need to make a temporary change, you might comment something out, which then requires commenting another now-unused variable, which then requires commenting out yet another variable, and so on. Go isn’t helping you here, it’s wasting your time for no good reason. Just emit a warning and allow CI to be configured to reject warnings.

This is the best explanation I’ve ever seen of monads: https://www.adit.io/posts/2013-04-17-functors,_applicatives,_and_monads_in_pictures.html

For some reason, you’ll find a lot of really bad explanations of monads, like “programmable semi-colons”. Ignore those, and check out the link.

It’s not a half-arsed copy, it’s borrowing a limited subset of HKT for a language with very different goals. Haskell can afford a lot of luxuries that Rust can’t.