Skip to content

Add warning to the README about fake MemPalace websites#598

Merged
bensig merged 1 commit intoMemPalace:mainfrom
justinclift:fake_websites_warning_v1
Apr 11, 2026
Merged

Add warning to the README about fake MemPalace websites#598
bensig merged 1 commit intoMemPalace:mainfrom
justinclift:fake_websites_warning_v1

Conversation

@justinclift
Copy link
Copy Markdown
Contributor

@justinclift justinclift commented Apr 11, 2026

What does this PR do?

Adds a warning to the README.md about fake MemPalace websites popping up.

As per #267, #326, and #506.

How to test

The standard pytest tests/ -v as per the CONTRIBUTING.md should be fine,
as this is a no-code change.

Checklist

  • Tests pass (python -m pytest tests/ -v)
  • No hardcoded paths
  • Linter passes (ruff check .)

@justinclift
Copy link
Copy Markdown
Contributor Author

@bensig Simple warning about the fake websites, near the top so it's reasonably prominent.

Went with pretty simple wording, as it should be clear enough. Can easily change stuff around though if needed. 😄

Copy link
Copy Markdown

@web3guru888 web3guru888 left a comment

Choose a reason for hiding this comment

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

Straightforward and important. The warning placement (before Quick Start) is prominent enough that new users will see it. Wording is clear and appropriately brief — no need to elaborate on what fake websites look like or their specific tactics, just the key fact: MemPalace has no website, so any claiming to be one is false. Good community safety contribution.

@justinclift
Copy link
Copy Markdown
Contributor Author

Hmmm, might be a good idea to add a date to the warning too.

@web3guru888
Copy link
Copy Markdown

A date makes sense — phishing/typosquatting sites tend to cycle through domain registrations, so knowing whether the warning was written six months ago or last week helps readers calibrate how current the specific sites listed are.

If you want to keep it simple, a trailing (as of April 2026) on the warning line is low-overhead. Alternatively a <!-- last verified: 2026-04-11 --> HTML comment keeps the prose clean while giving someone searching the git history a timestamp to grep for.

@justinclift
Copy link
Copy Markdown
Contributor Author

Oops. It turns out #326 is warning about a fake website too. I'll add that to the README as well.

@justinclift
Copy link
Copy Markdown
Contributor Author

If you want to keep it simple, a trailing (as of April 2026) on the warning line is low-overhead.

Yeah, not a bad thought. It's just a simple 11 April 2026 for now, but if more keep on popping up then it can be adjusted as makes sense. 😄

@justinclift justinclift force-pushed the fake_websites_warning_v1 branch from 35f25bd to b03ab48 Compare April 11, 2026 04:25
@bensig bensig merged commit f184a86 into MemPalace:main Apr 11, 2026
6 checks passed
@justinclift justinclift deleted the fake_websites_warning_v1 branch April 11, 2026 04:53
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.

3 participants