You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it is maybe possible to do this in the case where the status has already been populated, if the searched for URI is the same as the url or uri that was sent with the post (i.e. there's no redirection happening), but it would be complicated and maybe fraught (should you should statuses by silenced users? what about users that block you? these are all things to take into consideration....)
it is probably not currently feasible for us to fetch remote statuses that are private, even though I could imagine a HTTP Signatures way of doing it.
not parsing HTTP signatures on GETs for statuses is a thing that I've been missing due to my Kroeg instance not being as well populated and trying to retrieve entire post chains, but failing because there's posts that might be follower-only, but before I was a follower
Scenario:
Expected behaviour: Sandy's instance "knows" Paul's followers-only toot and knows that Sandy follows Paul. Sandy's search should bring up the toot.
Current behaviour: Sandy's search yields 0 results, because the toot they are searching for is set to followers-only.
This might be a duplicate but I honestly don't know what to search for. :S It is inspired by this thread.
master
(If you're a user, don't worry about this).The text was updated successfully, but these errors were encountered: