8000 Add Meshage (me.meshage.app) by DaveMeade · Pull Request #2006 · ImranR98/apps.obtainium.imranr.dev · GitHub
[go: up one dir, main page]

Skip to content

Add Meshage (me.meshage.app) - #2006

Open
DaveMeade wants to merge 2 commits into
ImranR98:mainfrom
DaveMeade:add-meshage
Open

DaveMeade wants to merge 2 commits into
ImranR98:mainfrom
DaveMeade:add-meshage

Conversation

@DaveMeade
@DaveMeade DaveMeade commented Nov 12, 2026 •
Copy link
Copy Markdown

Adds Meshage (me.meshage.app), a multi-mesh, mobile-first messaging app for MeshCore and Reticulum, from its official source: the developer's own site, https://meshage.me. I maintain the app and the site.

Source and shape

  • HTML source with non-default settings, so one config under complex/.
  • The APK Obtainium installs is the same ARM64 release build the site offers for direct download; the app is also on Google Play.
  • Icon: the Play Store listing's icon (returns image/webp). Category: messaging.
  • The badge is already live: https://meshage.me/obtainium redirects to this site's /redirect with the same config, so scripts/generate_from_url.py rebuilds this file's configs entry from that link. The icon, category and description were added by hand.

Why these additionalSettings (everything else stays default, version detection included)

key value reason
intermediateLink[0].customLinkFilterRegex /apk/arm64/current-version\.mu$ the landing page links to a small plain-text release manifest; this hop reaches it
customLinkFilterRegex /apk/arm64/meshage\.apk$ the ARM64 build; excludes the Play link and the ARM32 build
versionExtractWholePage true the version is in the manifest body, not in the APK URL
versionExtractionRegEx #version_code=(\d+) the manifest's #version_code=22 line, the APK's Android version code
matchGroupToUse 1 the captured number
useVersionCodeAsOSVersion true compare it with the installed app's version code: builds of one release can share a version name (0.4.9+21 and 0.4.9+22), which a name comparison can't tell apart

The manifest is the file the app's own update checker reads, and it is published in the same step as the APK, so the version code and the file cannot drift. The release script reads the code from the APK itself. Obtainium lists the version as the code (22) rather than the name.

Checks

  • npm run typecheck, npm run build and npm test pass locally. npm run validate:check reports this file's icon OK; it exits 1 on six other apps' dead icon URLs, which this PR doesn't touch.
  • Tested on a phone with Obtainium 1.7.4 from the badge link: with version code 21 installed, a fresh import listed Meshage as 21 → 22, installed the update, and then reported it up to date.
  • The source is a plain website, so no star or creation-date data applies.

🤖 Generated with Claude Code

8000
Dave Meade and others added 2 commits November 11, 2026 22:15
Official source: the developer's own site, https://meshage.me. HTML source
with an intermediate link to the site's release manifest, which carries the
version string and the ARM64 APK URL.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Meshage ships builds that keep the version name: 0.4.9+21 and 0.4.9+22 are
both 0.4.9, so comparing names never offered the second. The site's release
manifest now carries #version_code=, read from the APK at release time. The
config extracts that and turns on useVersionCodeAsOSVersion, so Obtainium
compares it with the installed version code. #version= stays in the
manifest, so installs on the earlier config keep working.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0