Help Wanted List

From Flashpoint Database
Revision as of 08:28, 10 August 2022 by Nosamu (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
  1. Help developing a system for automated Flashpoint builds: To improve release quality and frequency, we are working on an automated and reproducible way to build Flashpoint, including Windows, Mac and Linux builds. Currently we are able to build Flashpoint Infinity for Windows, but we are looking for help completing build configurations for Flashpoint Core and for Mac and Linux. A short overview of our build system is below. If you have knowledge of these tools, please join the #development-chat channel in our Discord and let us know that you'd like to help!
    • A self-hosted GitLab instance allows us to store and manage Flashpoint's repositories and build configuration files
    • Third-party binaries and other static files are stored in our Sonatype Nexus Repository Manager instance
    • The build is run on Linux, with the Earthly CI/CD framework providing a consistent environment
    • Ansible is the software that actually builds Flashpoint. Much of the work of maintaining our build system involves creating/modifying Ansible configuration files (playbooks).
  2. Help developing and documenting the Flashpoint Submission System: In 2021, we introduced a website for submitting curations, with the code available on GitHub. But we need help documenting the process for setting up a development environment so we can bring new contributors on board. If you're proficient with Golang, please try to set up a development environment for the site and document your process along the way. Be sure to join the #development-chat channel in our Discord server and ask Dri0m (the site's developer and administrator) for any advice and clarifications.
  3. Linux testers and developers: We are unable to offer an official Linux version of Flashpoint due to a lack of maintainers. We hope to once again offer an official Linux version, but we need help finalizing our new system for running Flashpoint using Docker containers. We call this new paradigm fpdocker, and you can find the latest experimental build pinned in the Mac & Linux Dev & Testing thread in the #development-chat channel in our Discord. Please test it out and let us know how it works for you! And if you'd like to help out, please take a look at our fpdocker repository and share your thoughts/questions in the Mac & Linux Dev & Testing thread.
  4. Mac testers and developers: A heavily outdated Flashpoint package for Mac is available from our Mac Support page, but we are currently working on an updated and hugely improved new build. But none of our Launcher developers currently have access to a Mac, so it would be very helpful for us to have a developer with a Mac join the Launcher team and help out with Mac-specific issues as they arise. To see what we're working on for Mac at the moment, please join the Mac & Linux Dev & Testing thread in the #development-chat channel in our Discord.
  5. Flashpoint Launcher developers: We use a custom Electron app called Flashpoint Launcher for displaying and launching games in Flashpoint. We need some more help with its development.
  6. Flashpoint Launcher extension developers: We are looking for developers to help develop new features for the Flashpoint project through launcher extensions. To learn more about creating launcher extensions, see the extension documentation and the API documentation.
    • See Launcher Extensions for some examples of useful launcher extensions.
    • One idea that we have for a future extension is a partial re-implementation of the Flashpoint Secure Player. This would allow us to support many more of Flashpoint's Technologies on Mac and Linux, since launcher extensions are cross-platform but Flashpoint Secure Player only runs on Windows. Below is a list of Flashpoint Secure Player features that we think could be ported to a Launcher extension. For more details, please ask in the #development-chat channel in our Discord.
      • Exporting custom environment variables to launched software
      • Changing the software's working directory
      • Hiding the software's window
      • Running software with elevated privileges
      • Restricting software to a single instance
  7. Flashpoint Website and Launcher translators: One great way to help us reach more people is localizing the Flashpoint Launcher into your language. See Translation Guide for more details on how to translate. We have also begun translating the Flashpoint website into multiple languages - we'll add information about how to help with this onto the Translation Guide soon.
  8. HTTPS support: Some games have obfuscation or exact URL sitelocks that make them only work on HTTPS URLs. We would like to support HTTPS in Flashpoint without installing a root certificate on the user's system. We need someone to set up the Apache server to use HTTPS, generate an SSL root certificate (self-signed should be fine), and direct one of our portable browsers to trust this certificate on all sites. The Apache server should act as a proxy for HTTPS traffic and serve files from its htdocs folder, just as it does for HTTP traffic. Proposed solutions include:
    1. One plan for implementing it would be based on this sample extension, and replace the response data outright with a version fetched over HTTP on certain URL match patterns.
      • filterResponseData was added in Firefox 57, though you could also restrict it on earlier versions in manifest.json.
      • Theoretically you could create a "fake domain" to store a configuration for this extension to be picked up by the proxy and then have the extension dynamically update its matched patterns every time the browser launches (manifest.json would not be able to be updated dynamically). This would require a browser based on Firefox 57+. You wouldn't even need to dynamically process the actual response, just overwrite it.
    2. Another potential solution would be something like this, which changes the URL of the request rather than modifying the response. It might perform better in terms of network requests, as they wouldn't be duplicated. I believe the domain fronter changes the URL back once the response is returned, so XHR would report the correct URL.
    3. Alternatively, given that FPBrowser is now hosted and compiled by us, we can probably redirect all the browser's HTTPS API calls to the HTTP ones.
  9. RTMP streaming support: Some games use Real-Time Messaging Protocol (RTMP) for streaming video or audio. We need help supporting this technology in Flashpoint.
    • Flash's RTMP connections are completely different from standard HTTP connections and are handled by the Flash plugin itself, so they do not appear in a browser's developer tools. We need help figuring out how to proxy RTMP connections, and specifically forcing Flash Player's RTMP connections to go through Flashpoint's proxy.
    • Flashpoint's Apache/PHP server does not support RTMP, and according to this list of RTMP server software, there may not be any way to do so. We need help figuring out how to add support for RTMP to Flashpoint's server, or adding a separate server for RTMP support.
    • Using RTMPDump, we can download the videos or audio streamed to a Flash game/movie. We need help figuring out which games in Flashpoint or elsewhere may be using RTMP, so we can download the media they depend on. The top priority should be checking games that are already in Flashpoint because we do not want to be unknowingly relying on external RTMP servers that may go offline at any time.
    • Here is an example of a game that uses RTMP for streaming video: Link, Curation
  10. Help implementing Kongregate user content and badges in Flashpoint: This Google doc lists all of the games on Kongregate for which we've scraped the user levels. A re-implementation of the Kongregate API is in progress, but it only supports badges right now, and some ActionScript 2 games and non-Flash games aren't working properly yet. We need help improving the reimplementation and possibly hacking the games so the user levels can be loaded in Flashpoint. It's especially complicated because games use HTTPS, and because of interactions between the games and the pages on which they're embedded.
  11. Replacing games hacked to bypass sitelocks with unmodified versions: This is a very low priority task, but would be desirable nonetheless. In Flashpoint's earlier years, certain games had to be directly modified as to bypass built-in sitelocks. However, as Flashpoint now has the ability to trick such games into believing they're being played online, this is no longer necessary. While there are no functional differences between a hacked game and a tricked unmodified game, having the original files would be preferable.
  12. ZIPping of legacy games: Currently this task is locked to staff contributors. Games added prior to Flashpoint 10.0 still use the legacy system, rather than the newly-implemented gamezip system for compression. Moving games over to the new game zip system, preferably games which are particularly large or otherwise problematic, would be massively helpful for file sizes.
  13. Sorting of extreme tagged games: Prior to Flashpoint 10, all extreme content was decided via a blanket on-off option. Flashpoint 10 introduced a tag system to allow more specific filtering of extreme content, but there still exists uncategorised content under the LEGACY-Extreme tag. Volunteers with a strong stomach may wish to assist in giving these entries more descriptive NSFW tags. See the Metadata Edits page for instructions on how to submit tag changes.

Former Projects:

  1. Differential updates: An updater for Flashpoint Ultimate has been released, and is available here.
  2. Action Message Format support: We finished adding an AMF implementation to PHP on Flashpoint's server, so now we are working to save user content databases for games that require AMF.
  3. Archiving and curating games: closed on March 31, 2019, and some of the games hosted there were lost forever. At Flashpoint, we worked to curate some of the games, and save the assets for as many as possible so they can be added to Flashpoint later.
  4. Archiving Pogo games: Pogo removed all of their Flash games in 2020. We worked to save some of these games, including packet captures of network activity to help with re-implementing Pogo's servers sometime in the future. Information about our efforts can be found in this Google doc. We still need help analyzing our packet captures and re-implementing enough of the server backend to make the single-player modes playable in Flashpoint.
  5. PHP script/library to read SWF headers: Staff member XXLuigiMario created a PHP script that can read the width and height of any SWF, along with a userscript to call this PHP script whenever the browser loads an SWF. To see it in action, download his patches for Flashpoint Infinity or Core.
  6. Portable Shockwave Player plugin: We finished integrating a portable Shockwave Player plugin with Flashpoint, and it is available in current Flashpoint releases. This was accomplished using our Browser Plugin Extender module.
  7. Hacking Unity Web Player games: We discovered a viable method for hacking Unity Web Player games, the details of which have been shared here.
  8. Flashpoint Info Check Extension: A Flashpoint Launcher extension which checks for and alerts the user of common issues is now integrated with Flashpoint builds. If new issues arise in the future, we may need help updating the extension to cover these issues though.

See Also: Help Wanted Games