SpringAll
SpringAll copied to clipboard
Ability to make reshares private
I think it would be wonderful to be able to make re-shares only to a limited audiece, since many things I re-share I might want to share with friends but not with other followers. As it is now, I often choose not to re-share out of this reason.
See #4467 and #1644 (always good to use the search facility before opening an issue).
As this is a duplicate, is it worth keeping it open?
Well #1644 is closed, so if we want to close this one we should reopen it.
Oops, I thought that one was still open. My mistake.
I believe that the Diaspora network needs to share "private" content (only into the network), Please, could be an excellent feature :)
I'm wondering if we have any technical problem to create a "public on diaspora" visibility which would have the exact same behavior of a public post except that you have to be logged to see it.
05.04.2016 09:59, Fla пишет:
I'm wondering if we have any technical problem to create a "public on diaspora" visibility which would have the exact same behavior of a public post except that you have to be logged to see it.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/diaspora/diaspora/issues/5770#issuecomment-205684964
Do you want to restrict a public post to the logged diaspora users? I don't know if it is a nice thing to do. It is like the web service tries to impose on registration.
No I want the user to be able to post either to "Public to the internet" or "Public to diaspora*".
05.04.2016 10:14, Fla пишет:
No I want the user to be able to post either to "Public to the internet" or "Public to diaspora*".
What is the point to separate this? Why would one want to publish a post on diaspora* while hiding it from logged off users?
We've had multiple discussions on both GitHub and Loomio about this and decided it's worthless. You absolutely cannot control the scope of your posts in a "public to diaspora" setting since it will get send to random servers anyway, so there is no difference to posting it public.
Nevermind resharing to the whole of Diaspora. If I want to increase the visibility of a post to many people who may be interested in it (an aspect) without my boss seeing it, without spamming the feeds of those who don't want to see it, and without restricting the author's ability to delete what they have written by copy-pasting it into a new limited post, I see reshare-to-aspect as the most efficient means of achieving that goal.
Requesting #1644 be re-opened.
i tend to reshare less since reshares are automatically public. there are things i'd like to show just a limited scope of people and not everyone who'll visit my feed.
A way to be able to do that would be to refer to a post from another one, which can be private. The complete proposal is exposed on discourse. Please join the discussion there.
why are discussions happening in two places?
@8spinach, the discussion should be taking place on Discourse, until the best way forward (if any) has been decided. This Github issue remains open as the issue has not been solved, but there's no point posting here until a decision on how to approach this issue has been decided (which will happen on Discourse).
Sharing a "public post" does not mean that I want everybody seeing that I'm sharing this public post. I discovered recently that my picture (the "basic profile", expression not so clear...) is now on search engines with all the public posts that I have shared. In another words, it's part of my identity that is revealed in all the Internet. Not so cool to discover... :-(
@jpggithub
I discovered recently that my picture (the "basic profile", expression not so clear...) is now on search engines with all the public posts that I have shared. In another words, it's part of my identity that is revealed in all the Internet. Not so cool to discover... :-(
If you'd looked at the tutorials on the project website, or at the in-app help section, you'd have found this mentioned explicitly.
Tutorials, part 1:
There are two parts to your profile: the basic profile, which is public, and the detailed profile, which is private by default. Your public profile is visible to everyone ...
In-app help feature:
Your basic profile (name, profile image and #tags) is public. ... Any profile information you make public can be viewed by anyone using the web, and can be indexed by search engines.
But this is off-topic for this issue.
My message was not so clear but it is not really off-topic. It is about diaspora manages privacy. By default, privacy would be preserved. Today, you must read the in-app help feature or/and the tutorials to understand how diaspora does not preserve your privacy by default. IMHO it is not a good thing.
I think the discussion in #4467 addressed this properly:
https://github.com/diaspora/diaspora/issues/4467#issuecomment-23490586
It may be best to just copy the public post URL into a new post and select aspect there, though perhaps a feature that does this automatically for you would be nice. For example: I click "Reshare", and instead of a "Are you sure?" dialog, I get a modal that asks for an aspect (or public), that allows me to post or cancel. Should I choose to post, it should create a post, reference the public post, and post it to the selected aspect.
There is a discussion about splitting reshares between "spread" (so, reshares which use the original post for likes / comments) and "quotes / references" (so the ability to create a new post (possibly private, with its own comments and likes). The "spread" would still be public, but the "quote" would be a way to do private reshare. Please read the discussion on discourse.
So its now 2021 and mastodon already fixed this it seems. Why did this discussion stall?
It seems? How it is fixed and where?