fix: use HTTPS for partner links in Base Services Hub - #1898
Open
xam-dev-ux wants to merge 1 commit into
Open
Conversation
Collaborator
🟡 Heimdall Review Status
|
t.me/billyjitsu, flowonbase.com, meow.com, gmgm.media, paperclip.xyz, plus1000aura.com, sealaunch.xyz and www.vacuumlabs.com all serve over HTTPS; the listing still linked to the HTTP versions.
xam-dev-ux
force-pushed
the
fix/services-hub-https-links
branch
from
September 1, 2026 18:35
f5293f8 to
5dc7cf1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed? Why?
Several partner listings in the Base Services Hub link out over
http://even though the destinations serve HTTPS: t.me/billyjitsu, flowonbase.com, meow.com, gmgm.media, paperclip.xyz, plus1000aura.com, sealaunch.xyz and www.vacuumlabs.com.Closes #1467.
Notes to reviewers
Only the link scheme changed, no wording or listing content touched.
How has it been tested?
Checked each of the 8 domains over HTTPS before changing (all returned a valid response, no failed handshakes).