Pixel Dungeon
This community is a place to talk strategies, tell stories, or discuss anything related to Pixel Dungeon or its many versions.
Rules:
-
1. No hate or adult themes of any kind: NSFW or illegal material, hate speech, personal attacks, harassment, doxxing, bullying, etc. are all strictly forbidden. Crude or offensive language should be kept to a minimum or avoided entirely.
-
2. Posts must directly relate to Pixel Dungeon: All content posted must directly reference Pixel Dungeon or one of its variants in some form. Loose connections or similar nomenclature from irrelevant works do not count.
-
3. Do not use other's work without giving credit: You may post things that were created by other people, but you must link to the original and credit the author. AI generated content is prohibited, as crediting the original authors is impossible.
-
4. Follow site-wide rules: https://legal.lemmy.world/fair-use/
We have a few title tags for standout posts:
- [MOD] - Posts by moderators about the community
- [DEV] - Announcements from a developer of a PD version
- [OC] - Self-made original content
Sister Communities:
view the rest of the comments
Any plans to include v3.0.0 in Accrescent for GrapheneOS users? See https://accrescent.app/
If you don't want to go through Google Play, I'd suggest downloading the game in APK form from Github. People are welcome to make unofficial distributions on stores like this though.
The problem with doing that is that Accrescent is a security-focused app store with a GrapheneOS-like perspective on security. For that reason alone, they would probably want an official person making the app for Accrescent.
Also, they say that F-Droid's practice of compiling their own builds is poor security, since it delays when the app is updated on the store, which means that patching security vulnerabilities is delayed. From that perspective, an unofficial maintainer for an Accrescent app would have to be very prompt with updates to the Accrescent package in order to be accepted into the store. They also do not like that F-Droid signs their packages with their own key, because that adds F-Droid as another developer that the user has to trust, in addition to the official maintainer.
So I do not think an unofficial maintainer would meet Accrescent's security standards or GrapheneOS's security standards. They would say that it is safer to either use their sandboxed Google Play or use Obtainium to download updates directly from Github instead. I personally use Obtainium. It is perfectly fine for me to do it that way. I just notice that the Accrescent app list is very small and needs more apps. And your game would probably be noticeable on there, due to the small app list. But it is fine; the GrapheneOS community is probably very small anyways.
Is there no way to set up a hands-off package that simply tracks Evan’s official releases on GitHub, grabs the release notes from there, fetches the APK from GitHub, and then verifies that the release been pushed by Evan using the keys he always uses to commit changes?
idk. they would still probably say to just get it from obtainium, which is fine by me.