Funny to see this today. I had moved a repo from an old Mac laptop to linux months ago, and git couldn’t find the ref to HEAD, because HEAD was pointing to the case insensitive branch name, and it didn’t match the case of the branch. Manually edited HEAD to the correct case to fix it. I should probably recreate the repo for good measure…

If schools only focused on what students were motivated to learn, I’m not sure schools would really be accomplishing much. Not to say that schools shouldn’t foster motivation in students. Just that technology, especially social media, is very effective at distracting people.

Try out haiku, serenity, menuet, or templeos? Depends on how non-Unix-like you’d prefer.

Looks like a Bruce

“Our patches? They’ve got skulls on them…”

There’s an open issue for xwayland for a lot of the flickering issues under nvidia, with a lot of disagreement about how to solve the issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317

Not directly to your exact question, but do you have something like rspamd set up? I would consider doing some filtering with rspamd modules. It’s a lot of learning to go through, but has some good defaults. It can filter outgoing mail as well as incoming.

It’s a lemmy problem as far as I’m aware, I believe with 0.18.3.

Yea I remember when people would just stand around the headphone booths in music stores and sample whatever new CDs came out that week. Maybe it was worse in the cassette tape era?

The headphones were gross. And to be honest, most albums only have a couple good songs anyway.

Just guessing, you might be the first person to try to visit that community/magazine from your instance, so lemmy doesn’t have the posts from before trying to federate.

There should probably be a message after federating a new community that tells people that old posts aren’t retroactively added to your local instance (unless done manually or unless that changes in the future). Or just something that tells users when a community was federated locally.

I think so. I haven’t needed to use it yet myself. I think it should forget the community and not federate future posts, unless some rediscovers/adds the community again. This is likely wrong sorry. An ability to block and purge specific remote instance communities seems pretty important.

As an admin, you can use the web UI to purge a community from your instance.

There’s a fix for this currently open, so should be on the way soon.

Empty toilet paper rolls support the whole flat earth. Big toilet paper doesn’t want us to know.

That’s an authentic gimp meme with the pepper stamp 👌

Should be able to handle a few users OK. You might want a more permanent server to run it on if they want to keep using it long term though.