Skip to content

Conversation

@rauwuckl
Copy link
Contributor

@rauwuckl rauwuckl commented Aug 7, 2025

the previous URL http://lambda-architecture.net/ seems to now be
controlled by spammers

the previous URL http://lambda-architecture.net/ seems to now be controlled by spammers
@github-actions github-actions bot added triage PRs from the community docs small Small PRs labels Aug 7, 2025
@shashankhs11
Copy link
Contributor

Hi @rauwuckl, thank you for the PR! I clicked on the link and confirm that it redirects to a new and possibly an unsafe URL. I agree with you that the link seems to be controlled by spammers now and could potentially be dangerous.

This issue seems minor and I believe the fix is trivial too, so I don't think we need a Jira ticket to track this.

Just a small request - could you please rename and prefix the PR title with - MINOR:
Maybe something like this? - MINOR: Remove SPAM URL in Streams Documentation

Tagging @mjsax @ableegoldman for review as it is related to streams

Attaching a screenshot for quick access:
image

@rauwuckl rauwuckl changed the title docs: Remove SPAM URL MINOR: Remove SPAM URL in Streams Documentation Aug 7, 2025
change URL to use HTTPS

Co-authored-by: Shashank <[email protected]>
@rauwuckl
Copy link
Contributor Author

rauwuckl commented Aug 7, 2025

thanks @shashankhs11 I changed the PR title as you suggested and made the URL use https

@shashankhs11
Copy link
Contributor

I think it is reasonable to include the url from wikipedia as an alternative. LGTM!

@github-actions github-actions bot removed the triage PRs from the community label Aug 8, 2025
Copy link
Member

@mimaison mimaison left a comment

Choose a reason for hiding this comment

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

LGTM

@mimaison mimaison merged commit 8deb6c6 into apache:trunk Aug 8, 2025
8 of 9 checks passed
@mjsax
Copy link
Member

mjsax commented Aug 11, 2025

Thanks for this fix! -- Can we also do a PR against kafka-site to do the same cleanup across all versions?

We should also cherry-pick this commit to 4.1 and 4.0 branches, maybe even 3.9, to avoid re-publishing the old url again by default?

@shashankhs11
Copy link
Contributor

I would be happy to help with a PR for kafka-site to apply the cleanup across all versions and can also help with cherry-picking to 4.1, 4.0, and 3.9, referencing this PR (#20321).

I want to acknowledge that this was @rauwuckl’s contribution, and I really appreciate the find and the fix, but I am ready to help.

@rauwuckl, please let me know if you were planning to tackle these steps, or I can take a shot at them to keep things moving.

@mjsax
Copy link
Member

mjsax commented Aug 11, 2025

@mimaison you merged this PR could do the cherry-picks. There is no need to do PRs for it, but we can just cherry-pick and push directly. -- If Mickael does not find time for it, I could help out with it.

For kafka-site, I let @rauwuckl and @shashankhs11 figure it out, who wants to do a PR. :)

@rauwuckl
Copy link
Contributor Author

Thank you all for the quick merge. I appreciate it.

As per @mjsax suggestion, I submitted pull request #712 against kafka-site.

To avoid clutter, I will not submit pull-requests against the mentioned version-branches of this repo. Following the suggestion that @mjsax or @mimaison push these changes directly.

mjsax pushed a commit that referenced this pull request Aug 13, 2025
The previous URL http://lambda-architecture.net/ seems to now be controlled by spammers

Co-authored-by: Shashank <[email protected]>
Reviewers: Mickael Maison <[email protected]>
mjsax pushed a commit that referenced this pull request Aug 13, 2025
The previous URL http://lambda-architecture.net/ seems to now be controlled by spammers

Co-authored-by: Shashank <[email protected]>
Reviewers: Mickael Maison <[email protected]>
mjsax pushed a commit that referenced this pull request Aug 13, 2025
The previous URL http://lambda-architecture.net/ seems to now be controlled by spammers

Co-authored-by: Shashank <[email protected]>
Reviewers: Mickael Maison <[email protected]>
@mjsax
Copy link
Member

mjsax commented Aug 13, 2025

Thanks. Merged the other PR.

Also took the liberty to cherry-pick this commit to 4.1, 4.0, and 3.9 branches. -- As we are getting a new RC for 4.0.1 release, it should pickup the change correctly. For 4.1 we need to make sure to not update the web-page docs incorrectly, as the current RC does not contain this fix yet.

@mimaison
Copy link
Member

Thanks for the backports. Since we're making a new RC for 4.1 we will automatically pick this up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants