Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add visibility param to reblog REST API #9851

Merged
merged 1 commit into from
Mar 15, 2019

Conversation

Gargron
Copy link
Member

@Gargron Gargron commented Jan 18, 2019

Fix #7322

  • Allow setting visibility for each reblog
  • Changes the default to reblog with the default chosen visibility setting instead of public
  • Use async worker for creating reblog notification to improve performance

@Gargron Gargron added the api REST API, Streaming API, Web Push API label Jan 18, 2019
@Gargron Gargron force-pushed the feature-reblog-visibility-api branch from f59d195 to beeb848 Compare January 18, 2019 18:10
@Gargron Gargron force-pushed the feature-reblog-visibility-api branch from beeb848 to 87ce030 Compare February 21, 2019 03:24
@@ -17,7 +18,7 @@ def call(account, reblogged_status)

return reblog unless reblog.nil?

reblog = account.statuses.create!(reblog: reblogged_status, text: '')
reblog = account.statuses.create!(reblog: reblogged_status, text: '', visibility: options[:visibility] || account.user&.setting_default_privacy)
Copy link
Contributor

Choose a reason for hiding this comment

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

On the one hand, I'm still uneasy with that change in behavior when we don't have UI to tell the visibility of a boost nor UI to specify it when boosting.
On the other hand, I think it makes more sense than the current behavior…

Copy link
Member Author

Choose a reason for hiding this comment

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

Use async worker for creating reblog notification to improve performance
@Gargron Gargron force-pushed the feature-reblog-visibility-api branch from 87ce030 to 2fa9961 Compare March 15, 2019 02:49
@Gargron Gargron dismissed ClearlyClaire’s stale review March 15, 2019 03:36

Most people are okay with reblog visibility following posting visibility preference

@Gargron Gargron merged commit ba84b6d into master Mar 15, 2019
@Gargron Gargron deleted the feature-reblog-visibility-api branch March 15, 2019 03:36
@lapineige
Copy link

Sorry if it's not the place to ask, but will only be activated for new boosts in >=2.8, right ?
It doesn't change the status of previous (<2.8) boosts, correct ?

@Gargron
Copy link
Member Author

Gargron commented May 15, 2019

Yes, correct

@lapineige
Copy link

And if we want to boost publicly some toot, we have to change the setting, boost, switch back to private visibility by default, and that would work ?

hiyuki2578 pushed a commit to ProjectMyosotis/mastodon that referenced this pull request Oct 2, 2019
Use async worker for creating reblog notification to improve performance
messenjahofchrist pushed a commit to Origin-Creative/mastodon that referenced this pull request Jul 30, 2021
Use async worker for creating reblog notification to improve performance
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api REST API, Streaming API, Web Push API
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ability to boost to followers only ("private boost")
4 participants