meteokr

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.

What do you mean by Mastodon selling out to Meta? Isn't Meta just building an ActivityPub based platform so we can talk to their users as far as I know. If they want to talk to us, then the onus is on Meta to stay compatible. If they aren't, then we just continue on as we have.

There's also Bitmagnet, it you'd like a local tracker for the Arr stack.

The article is "Conservative Hardware Evolution". Emphasis mine. The Switch2 will also be a conservative hardware evolution, exactly like the Wii. The Wii's hardware was extremely conservative, already ancient upon release. Rocked 0 boats.

Cemu doesn't seem to have a problem with profitability. The litigation was about circumvention of encryption and blatant piracy advocation.

That was the Wii actually. It being a slightly up clocked Gamecube. The WiiU was a massive hardware upgrade from the Wii at the time. The WiiU just had a host of other problems.

Then we just disable it, and run the DLSS natively.