Skip to content

[Mozilla Branding Removal] Invalidate reticulum.io URLs - #6588

Merged
Exairnous merged 2 commits into
Hubs-Foundation:masterfrom
Exairnous:invalidate-reticulum.io-references
Aug 23, 2026
Merged

Exairnous merged 2 commits into
Hubs-Foundation:masterfrom
Exairnous:invalidate-reticulum.io-references

Conversation

@Exairnous

@Exairnous Exairnous commented Aug 17, 2026 •

Copy link
Copy Markdown
Member

What?

Replaces all instances of reticulum.io with reticulum.io.invalid. reticulum.io-outdated.

Why?

Reticulum.io was used extensively by Mozilla, but now that they are no longer doing things with Hubs (and since the Hubs Foundation doesn't own the domain), it's possible that these URLs could become a latent security risk.

Examples

N/A

How to test

  1. Do a search in all files for reticulum.io (e.g. grep -r --exclude-dir={.git,node_modules} "reticulum.io").
  2. See that all instances of reticulum.io have been replaced with reticulum.io.invalid. reticulum.io-outdated.
  3. Build and deploy the changes to an instance.
  4. See that everything works normally.

Documentation of functionality

No functionality has changed, so no documentation update is needed.

Limitations

None.

Alternative implementations considered

Commenting out the references was considered, but invalidating them was deemed safer/easier.

Open questions

None.

Additional details or related context

The replacements were preformed with the following commands:
first
git grep -lz "reticulum.io" | xargs -0 sed -i '' -e 's/reticulum\.io/reticulum\.io-outdated/g'

then (to address Hubs-Foundation/Spoke#1316 (comment))
git grep -lz "reticulum.io-outdated" | xargs -0 sed -i '' -e 's/reticulum\.io-outdated/reticulum\.io\.invalid/g'

Part of roadmap item "Invalidate old Mozilla server links in repos with previously finished branding removal"

What: replaces all instances of reticulum.io with reticulum.io-outdated.

Why: reticulum.io was used extensively by Mozilla, but now that they are no longer doing things with Hubs (and since the Hubs Foundation doesn't own the domain), it's possible that these URLs could become a latent security risk.
@Exairnous Exairnous added the Roadmap: Programming Indicates that this issue/pull request is on the Programming Team roadmap label Aug 17, 2026
@Exairnous
Exairnous requested a review from DougReeder August 17, 2026 04:52
@hobbs-Hobbler

Copy link
Copy Markdown

@Exairnous Question: Is the point here to add the "-outdated" so that the link just does not work?

@Exairnous

Exairnous commented Aug 19, 2026 •

Copy link
Copy Markdown
Member Author

@hobbs-Hobbler

@Exairnous Question: Is the point here to add the "-outdated" so that the link just does not work?

Yes, exactly.

(Though now it looks like we're going with .invalid instead of -outdated, see @DougReeder's review comment here: Hubs-Foundation/Spoke#1316 (comment))

Why: addresses review feedback from Hubs-Foundation/Spoke#1316 (comment) (.invalid is reserved for this purpose, so it's better to use that than our own fabrication of .io-outdated).

@DougReeder DougReeder left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Exairnous
Exairnous merged commit 986d07a into Hubs-Foundation:master Aug 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Roadmap: Programming Indicates that this issue/pull request is on the Programming Team roadmap

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants