The idea is that “roguelike” = a game like Rogue, which according to some people, requires checking most if not all of the boxes including ASCII, proc-gen, perma-death, turn-based, … while the term “rougelite” is less strict. But I think we’re past the point of that distinction being adopted into mainstream.

https://github.com/godotengine/godot-docs

This is the source for Godot’s documentation. You could clone the repo (in reST format) or download one of the releases (in HTML format) offline, so you wouldn’t even need to query anything online.

Taming animals so you can ride them, or let them pull carriages? Building roads for vehicles? Train tracks with functional trains? Cool airships? All made obsolete with this one-kills-all glider feature! Don’t let good game design get in the way of convenience! /s

A lot of contributors of FOSS projects make small changes that aren’t copyrightable.

The real question is not what the algorithm pushes to you, but whether their moderation actually bans bigots and removes their posts. Any other instance would lose their “right” to federate with a queer-friendly instance if they didn’t do that, so why would Threads get an exception?

Isn’t “queer friendly” and “federates with Threads” an oxymoron?

Indeed, it’s a neat way to visualize gravity, but that’s it. It lacks any sort of explanation of why masses appear to be pulled towards one another. (I will point to the other person in this thread saying it “explains gravity with gravity”.) This is why I think the metaphor you mentioned detracts from the original video.

I think that explains the “how” more than the “why”.

I don’t think that’s how it works and it would likely not be legal. By explicitly blocking Threads, you make a big statement about not wanting your instance’s posts to show up there. Also from a technical standpoint, I don’t think a “middle-man” instance will push posts from another instance to a third one. You’d have to explicitly scrape data that’s not available via the API. Please correct me if I’m wrong.

Could you please provide some sources for that? I’d like to know more.

First of all though, there is no such thing as a “hostile fork”. Being able to fork a project, for any reason, is the entire point of open source. And to be fair, not wanting to continue working for a for-profit company for free is a very good reason.

And yeah, when you suddenly turn a FOSS project that’s been developed with the help of a bunch of contributors, into a for-profit company, without making a big fuss about it beforehand and allow the contributors and community to weigh in, then yeah, that’s a hostile takeover of sorts, at least in my opinion. Developers gotta make money, but they could’ve done that by creating a new brand instead of taking over that of a previously completely FOSS project. Forgejo is preventing that exact thing from happening by joining Codeberg (a non-profit).

There’s been a hostile takeover at Gitea and it’s now run / owned by a for-profit company. The developers forked the project under the name Forgejo and are continuing the work under a non-profit. See also: Their introduction post and a page comparing the two projects. Feel free to look up more, since I haven’t familiarized myself with the incident all that much myself. Either way though, maybe consider using Forgejo instead of Gitea.

I did decide to delete all my comments and posts on Reddit. Sure, maybe I’ve posted some helpful comments, but why support Reddit with their continued existence? Remove content, and people might move to other sites to get their information.

I also decided to keep my account. Turns out some content stayed around, because I could not see and therefore delete it in locked subreddits. So when they came back, the comments came back too, and I was able to delete them, still.

I’m unable to test this, but I was browsing around and found that in a FontVariation you add “Standard Ligatures” to “OpenType Features” and then disable it. Would that by chance help solve your issue? There’s also a similar field in the font import options in “Metadata Overrides”.

I don’t know how many years it’s been, but I also have been driving Arch for a while. I might not recommend it to absolute beginners, because you do need some patience and experience (such as how to effectively google), but honestly besides some mostly self-inflicted issues, I felt like I had it all around easier than users of other distros (and Windows, of course).

My only experience with Mind Traveler was them engaging with almost every single comment in one thread, seemingly stirring up stuff. I’m not sure about others, but to me that’s not how I want anyone to interact with a forum such as Lemmy. I don’t want half of the comments in a thread to be from a single user trying to argue every single other person, being as noisy as they can be.

Also, what is your stake in this? You aren’t a particularly active user, at least from what I can see from my Lemmy instance. There might be reason to believe you’re an alt account of Mind Traveler or a friend trying to push some narrative.

Besides, if anyone is not happy with the actions of our Lemmy admins, which are unlikely to change, why not just move to another instance? That’s the beauty of the fediverse, after all. Unless, of course, they aren’t welcome on other instances either.

Please, no more drama or attempting to discredit Blåhaj Lemmy admins.

Regarding what I called a “witch hunt”, it seemed like some users quickly jumped on board accusing the previous owner of the libertyhub community of intentionally misgendering a user, when it appeared to be a singular slip up (“you” instead of “You”), that he quickly apologized for and fixed. Maybe there were valid concerns regarding the moderation of that community and it was indeed the right choice for the owner to step down – I am totally missing the context for this – but I felt like there was a large focus on the wrong issue that might’ve driven him away from Lemmy.

As a spectator with no stake in what happened, except of course wanting people to feel comfortable, I feel like two things were still left unaddressed:

• It looked like the owner of the affected community was driven out by something that almost resembled a witch hunt, with accusations that appeared to be unfounded or even maliciously pushed by people opposing the views or moderation style of the community.

• There was a particular user who stood out to me because they tried to respond to as many posts as possible, seemingly fueling the drama, or at least actively pushing their opinion on everyone. I feel like this is not the appropriate way to interact in such a forum, nor healthy for that individual.

What did the admins do or are planning to do in regards to these concerns?

When you say “trans woman” you affirm that they are women, and trans is just an adjective. When you say “transwoman” it can imply that they are something different altogether, and TERFs have certainly used it as such. Like, I dunno, a carpark isn’t a park? That’s the first example that came to mind, anyway.

I believe “copyright free” in this case doesn’t mean not protected by copyright, but rather that it was missing attribution, so they could not contact the original creator.

Anything you create is automatically protected by copyright, whether you put a “© copygirl” or something to that effect on it or not. To use someone else’s work, you either need to get permission from the author directly, or the work has to be available under a license that says you’re allowed to (typically comes with some requirements or restrictions). One can also release a work under public domain, but that isn’t legally possible in some countries. There’s also some exceptions like fair use but that’s another thing.

Something else to consider in place of or in addition to a build number could also be using the git commit hash of what you’re building. Though I would only use that for non-stable releases.

For example, stable versions of Zig look like 0.12.1 and then there’s in-development releases like 0.13.0-dev.351+64ef45eb0. It uses semantic versioning where the “pre-release” is dev.351, which includes an incrementing build number, and the “build metadata” is 64ef45eb0, the commit hash it was built from. The latter allows a user to quickly look up the exact commit easily and thus know exactly what they’re using.