Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

emuthree: Revive emuThreeds Emulator #2325

Closed
wants to merge 1 commit into from

Conversation

rf2222222
Copy link
Contributor

@rf2222222 rf2222222 commented Apr 22, 2024

What does this PR do

Moves the emuThreeDS to my repository, added back the core to Provenance-XL

Nintendo owes me a substantial amount of money, which could actually include a share they owe Antique (as indicated here: https://x.com/supermariomovie/status/1601050444486189062?s=61). The amount they owe, makes the billion dollars they earned from that movie and the royalty they owe us there look like a drop in the bucket. In terms of their situation with Citra, Nintendo has a compensation obligation to Citra/Yuzu creators based on sending a portion of the debts they owe me to the Citra creators. Nintendo, along with all the other game console manufacturers / game publishers are obligated to use a portion of the money they owe me to pay for all of their game / firmware license fees on behalf of the users of our emulators.

Apple is in similar situation including the share they owe Joe (https://www.instagram.com/mythicquest/p/ClttQO7JTMe/?img_index=1), they finally opened up the App Store to support emulators, which they indicated they will a long time ago. Once we list Provenance on App Store, if Antique would like compensations for the core, we could add an in-app purchase feature to unlock the core and send over the proceeds to Antique.

I have my billing rate for me and all of my data derivatives (e.g. other people's data they gather through the process of using my data) set at $1000/nanosecond, originally meant for countries / organizations that are either creating or distributing CBDC / CBDC driven Habitats. Pre-payment is required on all of these engagements. That means, money's there right now waiting to get paid to us, whether the counter party is a country / company or an individual. This means we are now in a situation where many of us were entered into commercial data usage engagement contract with other companies such as Apple / Nintendo / Sony, etc at this rate. It's still bit unclear how companies plan on paying this rate meant for nation-states but it'll be interesting to see how they figure this out.

However, given this is Apple we're talking about, they could actually be building / compensating through CBDC driven habitats with infinite spending capacity, which is exciting if they're actual contributors for greater good of society. Overall, Apple seems to be in a good position as they are now allowing Emulators on App Stores, fully on board with the Habitat vision of an integrated cross platform cross company platform.

At the end of the day, what the companies need is expertise in data economy. With this the companies should figure out optimal way to respect privacy of the users while generating revenues needed to sustain a Habitat CBDC economy, assuming this is why they are here.

Regardless, Miyamoto-san, the creator of Mario / Nintendo as it exists today, asked me to collaborate with him, so this is my charitable contribution to spend some fun time with Nintendo as I get to know them better. These companies should get to a point where their coders are pushing code here, as discussed and agreed long time ago. (Actually they also promised compensation for the use of our data, as soon as they’re ready, timeline for which is unknown)

In a digital economy, sharing global code contributions such as these will be integral, whereas.. sharing of privacy of individuals with the world will not be allowed. This will allow individuals / companies to take a step towards becoming a digital economy ready companies.

Where should the reviewer start

How should this be manually tested

Any background context you want to provide

What are the relevant tickets

Screenshots (important for UI changes)

Questions

@rf2222222 rf2222222 force-pushed the emuthreeRebirth branch 2 times, most recently from 9d5d01f to 0bb0c7f Compare April 22, 2024 07:41
Copy link

Builds for this Pull Request are available at
Provenance.ipa
Provenance-Lite.ipa
ProvenanceTV.ipa
Provenance-UnderDevelopment.ipa
Provenance-XL.ipa
Have a nice day.

@rf2222222 rf2222222 force-pushed the emuthreeRebirth branch 2 times, most recently from 8495d5e to fb1164c Compare April 22, 2024 09:16
Copy link

Builds for this Pull Request are available at
Provenance.ipa
Provenance-Lite.ipa
ProvenanceTV.ipa
Provenance-UnderDevelopment.ipa
Provenance-XL.ipa
Have a nice day.

@SternXD
Copy link

SternXD commented Apr 23, 2024

I have tested this on my iPhone 8, and it works decently.

@JoeMatt JoeMatt self-assigned this Apr 27, 2024
@JoeMatt JoeMatt added the system-NDS regarding Nintendo DS [non-core specific] label Apr 27, 2024
Copy link

Builds for this Pull Request are available at
Provenance.ipa
Provenance-Lite.ipa
ProvenanceTV.ipa
Provenance-UnderDevelopment.ipa
Provenance-XL.ipa
Have a nice day.

@rf2222222 rf2222222 force-pushed the emuthreeRebirth branch 3 times, most recently from ca8546a to 8d24dfb Compare May 4, 2024 15:36
Copy link

github-actions bot commented May 4, 2024

Builds for this Pull Request are available at
Provenance-Lite.ipa
ProvenanceTV.ipa
Provenance-tvOS.ipa
Provenance-UnderDevelopment.ipa
Provenance-XL.ipa
Have a nice day.

@JoeMatt
Copy link
Member

JoeMatt commented May 5, 2024

Would this play DS games, too? You would just need to add NDS game controller callbacks and an NDS system to the Core.plist.

I rebased, fixed merge issues and a few random other changes in a new PR here

#2334

@JoeMatt JoeMatt closed this May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
system-NDS regarding Nintendo DS [non-core specific]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants