Skip to content

Conversation

@kraktus
Copy link
Member

@kraktus kraktus commented Mar 9, 2025

The actual text labels are WIP, just want to make sure the implementation is right first. I initially thought about just adding a "promotion" tag, but having a separate field in the db will allow for easier filtering later.

image image

@kraktus kraktus force-pushed the ublog_commercial_disclosure branch from 9745ab3 to e1ada6b Compare March 9, 2025 13:53
@kraktus kraktus marked this pull request as ready for review March 9, 2025 15:29
@kraktus kraktus changed the title Ublog: disclose commercial content in posts Ublog: disclose sponsored content, affiliate links or commercial advertisement in posts Mar 9, 2025
Copy link
Collaborator

@ornicar ornicar left a comment

Choose a reason for hiding this comment

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

implementation looks correct 👍

live: Boolean,
discuss: Option[Boolean],
sticky: Option[Boolean],
ads: Option[Boolean], // boo!
Copy link
Collaborator

Choose a reason for hiding this comment

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

?

),
form3.checkbox(
form("ads"),
"Includes promotion",
Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe "promoted / sponsored content"

@ornicar
Copy link
Collaborator

ornicar commented Mar 10, 2025

I initially thought about just adding a "promotion" tag, but having a separate field in the db will allow for easier filtering later.

It's actually easier and better to filter as a UblogPost.topic, as a db index already exists

I would prefer that, except that your extra form toggle allows for a explanatory description, which is probably necessary.

@ornicar ornicar merged commit 70239b1 into lichess-org:master Mar 10, 2025
3 of 4 checks passed
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