I remember the very strange control scheme it had on PS4 I think it was? You couldn’t bind your abilities to any button, just specific combinations like Square+Left, but not Square+Right, something like that. I wonder if they’ve changed that in the newer ones.

I only just found out about it and wanted to share since I havent heard any dicussion around this style of game. It looks fun, but I havent had a chance to sink much time into it.

I can’t seem to find it, but I think it was James Gosling, where he was blocked from reviewing code at Google because he hadn’t gone through the company’s approval process. I hope this wasn’t a myth I’ve been carrying on for this long.

Right, I did hear about that lawsuit way back when, I just didn’t know of these types of consequences. Very appreciated, especially the sources.

Is this for hardware RAID controllers, or have you experience software RAID like LVM or ZFS exhibiting the same drop out behavior? I personally haven’t but it be nice to look out for future drives.

Regex is Turing Complete after all.

Does Backblaze work for what you are doing? It been a bit since I’ve price compared them, but I think it was something around 5$ a month per TB?

Oh so its just referring to writing the mod’s code in the same file the mod is declared in being bad form? That seems very reasonable; since the point of a module is code separation so it makes sense to always put it in its own file. Good, I’m already doing that at least!

I don’t understand how to follow this bullet point that I was replying to.

do not use mod unless it’s test for the current module. No I don’t want to Star Wars scroll your 1000 line file. Split it.

I already know what mod does in a basic sense, I wanted to know what the commenter meant by this.

I don’t know enough Rust to understand by what you mean by the last one. My understanding was that mod name was just declaring the module that this file depends on. Could you explain what I should do instead? Since your other statements I totally agree with, I should probably agree with the last one.

The Venn diagram of game developers, who are also interested in/good at running a business has very little overlap. You need many different kinds of people to run a business, but a game developers is only one of those. In some rare cases it works out though.

Here’s a link to an instance of radicle for Yuzu. It’s a p2p git server implementation. I haven’t looked too much into it yet, but the tech seems interesting.

I guess burden was probably the wrong term. I appreciate your work, and I just get over protective of really cool freely available services from being overwhelmed. That’s an excellent suggestion.

I’m using Automatic1111’s SD web UI, so their API would be the most relevant to me, but there are others out there if you prefer to use something else an an optional backend.

Can I use my locally hosted SD API rather than burden the Horde with something like this?

The paywall as far as I know isn’t that much of problem. Cemu has/had a paywall for years. Several other, though less successful, emulators have had paywalled content/early access as well. The BLEEM emulator that was brought to court was a paid commercial product. So that currently is perfectly legal within the jurisdiction of those cases. Nintendo’s case against Yuzu was about piracy/DRM circumvention. That wasn’t brought to court, so we don’t know the outcome however.

I don’t believe Yuzu went to court, but that was the accusation Nintendo was suing them over. Ryujinx wasn’t sued, so Nintendo either didn’t believe they had done the same, or didn’t care. We didn’t get to have a discovery process for the case to find out for sure, so we don’t know.

IANAL, but they should be fine since they aren’t decrypting / breaking DRM they same way Yuzu was. They are a much cleaner codebase, much more similar to mGBA and Dolphin.

That’s sorta the curse of an open protocol is that anyone, even your enemies, can use them. I am no fan of Meta. I am a big fan of open standards, monkey’s paw and all. It is not a case of tolerating the intolerant. To restrict Meta out of using ActivityPub is against the spirit of open standards. The protocol is no longer open, and THEN we really have something to worry about.

Don’t worry I’ve been quoted EEE enough times. I really don’t think that is the direction this will go down. If Meta actually embraces it, then the whole of the fediverse grows over all. Then, if Meta does extend the ActivityPib protocol in a way the that becomes incompatible with the rest of the ecosystem, we just let them go and do their own thing. ActivityPub already has a userbase, if they join us, and then later on cause problems then everything just goes back to how it is right now. The final E can’t realistically happen because the existing ecosystem will just carry on exactly as it is now. If people on Threads want to communicate with us, then they need to speak the same protocol. If they don’t, then they don’t get to participate.

Do you genuinely believe that the whole community of the fediverse would just lie down and accept breaking changes to the protocol without resistance? There are too many talented and passionate people invested in this ecosystem, the absolute worst case scenario is the protocol itself gets forked, and again the exist communities just carry on. There is no extinguish time line. Everyone points to how Meta handled XMPP, please compare the user bases of ActivityPub vs XMPP. The world has changed a lot since then. Another example I’d like to point out is Hashicorp’s Terraform. They explicitly tried to EEE, and the moment they attempted the final E, it was instantly forked, and the open licensed fork was adopted into the Linux Foundation and the ecosystem carried on.

Take that what you will, but I am reasonably convinced ActivityPub has enough support and community that any EEE attempt will inevitably fail. The front ends will change, the hosters will come and go, the open standard is here to stay.