github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-08 21:59:09 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[GH-ISSUE #1551] RackNerd Affiliate Disclosure #8717

New Issue
Closed
opened 2026-04-30 04:43:31 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-30 04:43:31 -05:00
Owner
Copy Link

Originally created by @foxt on GitHub (Sep 27, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1551

Hey! I just wanted to start with just a note to say I'm not trying to attack or call anyone out here - I know OSS development is often very thankless and I very much am aware you need to keep the lights on and have no problem with you monetising your project in such a way, but I noticed in the README there's a line that reads

Many of our users have had a great experience with [RackNerd](https://my.racknerd.com/aff.php?aff=13788). Depending on promotions, you can get a [VPS with 1 vCPU, 1GB RAM, and ~20GB SSD for just around $12/year](https://my.racknerd.com/aff.php?aff=13788&pid=912). That's a great deal!

Now, I've never used RackNerd so I have no reference for how good or bad their service is (see #801 ), but I'm concerned that this doesn't properly disclose the affiliate relationship between RackNerd and this project and that it's likely that you're recommending RackNerd, at least in part, because they are offering you a kickback based on who is signing up with your affiliate link, rather than any unbiased merit.

Providing disclosure when you're promoting something based on a commercial relationship isn't just something should be required on a moral level - it's actually legally required in the US where I believe this project is based.

Originally created by @foxt on GitHub (Sep 27, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1551 Hey! I just wanted to start with just a note to say I'm not trying to attack or call anyone out here - I know OSS development is often very thankless and I very much am aware you need to keep the lights on and have no problem with you monetising your project in such a way, but I noticed in the README there's a line that reads > `Many of our users have had a great experience with [RackNerd](https://my.racknerd.com/aff.php?aff=13788). Depending on promotions, you can get a [VPS with 1 vCPU, 1GB RAM, and ~20GB SSD for just around $12/year](https://my.racknerd.com/aff.php?aff=13788&pid=912). That's a great deal!` Now, I've never used RackNerd so I have no reference for how good or bad their service is (see #801 ), but I'm concerned that this doesn't properly disclose the affiliate relationship between RackNerd and this project and that it's likely that you're recommending RackNerd, at least in part, because they are offering you a kickback based on who is signing up with your affiliate link, rather than any unbiased merit. Providing disclosure when you're promoting something based on a commercial relationship isn't just something should be required on a moral level - it's actually [legally required in the US](https://www.ftc.gov/system/files/documents/plain-language/1001a-influencer-guide-508_1.pdf) where I believe this project is based.
GiteaMirror commented 2026-04-30 04:43:32 -05:00
Author
Owner
Copy Link

@hhftechnology commented on GitHub (Sep 27, 2025):

https://docs.digpangolin.com/self-host/choosing-a-vps#support-and-reliability

Image
<!-- gh-comment-id:3341849728 --> @hhftechnology commented on GitHub (Sep 27, 2025): https://docs.digpangolin.com/self-host/choosing-a-vps#support-and-reliability <img width="1735" height="3572" alt="Image" src="https://github.com/user-attachments/assets/6de37e35-13d2-401f-ba88-5d92bb735ba4" />
GiteaMirror commented 2026-04-30 04:43:33 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Sep 27, 2025):

^^ thanks @hhftechnology. Yes we disclose but if this is not enough legally we can adjust.

Thanks for the concern! :}

<!-- gh-comment-id:3341915824 --> @oschwartz10612 commented on GitHub (Sep 27, 2025): ^^ thanks @hhftechnology. Yes we disclose but if this is not enough legally we can adjust. Thanks for the concern! :}
GiteaMirror commented 2026-04-30 04:43:33 -05:00
Author
Owner
Copy Link

@foxt commented on GitHub (Sep 27, 2025):

ah, i see it's noted in the docs but my concern was the readme!
https://github.com/fosrl/pangolin#fully-self-hosted

On Sat, 27 Sep 2025 at 5:53 pm, Owen Schwartz @.***>
wrote:

oschwartz10612 left a comment (fosrl/pangolin#1551)
https://github.com/fosrl/pangolin/issues/1551#issuecomment-3341915824

^^ thanks @hhftechnology https://github.com/hhftechnology. Yes we
disclose but if this is not enough legally we can adjust.

Thanks for the concern! :}

—
Reply to this email directly, view it on GitHub
https://github.com/fosrl/pangolin/issues/1551#issuecomment-3341915824,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC5QOWEONDWMG57TR3M7YB33U26JLAVCNFSM6AAAAACHVANFQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNBRHEYTKOBSGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:3342034639 --> @foxt commented on GitHub (Sep 27, 2025): ah, i see it's noted in the docs but my concern was the readme! https://github.com/fosrl/pangolin#fully-self-hosted On Sat, 27 Sep 2025 at 5:53 pm, Owen Schwartz ***@***.***> wrote: > *oschwartz10612* left a comment (fosrl/pangolin#1551) > <https://github.com/fosrl/pangolin/issues/1551#issuecomment-3341915824> > > ^^ thanks @hhftechnology <https://github.com/hhftechnology>. Yes we > disclose but if this is not enough legally we can adjust. > > Thanks for the concern! :} > > — > Reply to this email directly, view it on GitHub > <https://github.com/fosrl/pangolin/issues/1551#issuecomment-3341915824>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AC5QOWEONDWMG57TR3M7YB33U26JLAVCNFSM6AAAAACHVANFQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNBRHEYTKOBSGQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#8717
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?