Comments (9)
To be honest, I would also like us to implement it in this way. In the past, however, we had agreed on the variant that private profiles are completely private.
I would also prefer to take the approach of Mastodon - like here in your proposal. A private profile is nothing else than that you have to request someone. The visibility of the checkins would then be decisive.
But if you implement it this way, you have to set all public checkins of private profiles to followers only for safety's sake, so that they are not suddenly public.
I would be happy if there are other opinions. I would be in favor of implementing this issue.
from traewelling.
In my opinion, a private profile should never be able to post anything public, so that someone cannot accidentally post private information publically.
Maybe we should remove the possibility to change the visibility to public if you have a private profile?
from traewelling.
Maybe we should remove the possibility to change the visibility to public if you have a private profile?
I don't like this suggestion. I would like to have public checkins, but also some that are only visible to confirmed followers. This is currently not possible.
from traewelling.
I would also prefer a change of the current behavior. It's more transparent and easier to understand who can see my check-in, if it's final visibility isn't determind by two seperate settings.
so that someone cannot accidentally post private information publically
Private profiles could have the default visiblity set to "Followers only" and I could also imagine a more explicit way to set a check-in to a (semi-)public visibility (e.g. a "Include options that prevent my privacy setting" you have to confirm first, before the option is available) for users with private profiles.
also follower-only should be removed from public accounts, since it is meaningless and suggests a false security
I understand your rationale and (personally) wouldn't mind this being removed, but I don't think it's meaningless.
- Users that don't follow you neither see the check-in itself
- nor that there are (somewhat) hidden check-ins at all (hard to explain, but on a private profile it's safe to assume there are check-ins that you can't see, on a public profile you wouldn't; and at least I don't randomly follow someone, just to check if there are hidden check-ins)
So it's like a "I don't want to shout it from the rooftops, but if you're really interested in my check-ins here you go" option.
I'm in favor of implementing this change but what would happen to existing public check-ins from private profiles? Those would become visible, right? Maybe this needs additional thoughts...
from traewelling.
I'm in favor of implementing this change but what would happen to existing public check-ins from private profiles? Those would become visible, right? Maybe this needs additional thoughts...
This can be resolved with a simple migration, which sets all "public" checkins from private profiles to follower-only. Then nothing will effectively change in terms of behavior.
from traewelling.
It might also be an idea to set the check-ins to private if you have made the profile private, just to ensure that you don't forget to make specific check-ins private (if you don't have the timer activated)
The timer shouldn't really matter, as the check-ins are set to private anyway.
If we write the migration á la "update visibility
SET followers-only
WHERE (public
|unlisted
) AND private_profile
" there should be no problems from my point of view.
from traewelling.
In my opinion, a private profile should never be able to post anything public, so that someone cannot accidentally post private information publically.
my use-case is that i want to share some stuff only to my followers. for that i need to approve them. if followers aren't approved, then posting follower-only is the same as posting public with another step. because anyone could just follow me and see everything.
Maybe we should remove the possibility to change the visibility to public if you have a private profile?
when we keep it this way, that private profiles can't post anything publicly, then yes, public and unlisted should be removed. also follower-only should be removed from public accounts, since it is meaningless and suggests a false security.
from traewelling.
Another possibility could be to implement three different profile options. Public, Accept Followers and Private.
Private would be essentially the same as "Accept followers" only that you would only have the post-visibility-options "private" and "followers only" - no unlisted, no public.
This could reduce the complexity for the user and might not be as confusing.
from traewelling.
In my opinion it makes sense to treat "public" check-ins as such, because it makes clear that this check-in can be seen by everyone even when your profile is private. Maybe a warning can be raised if you're making a public check-in with your private profile:
This can be resolved with a simple migration, which sets all "public" checkins from private profiles to follower-only. Then nothing will effectively change in terms of behavior.
It might also be an idea to set the check-ins to private if you have made the profile private, just to ensure that you don't forget to make specific check-ins private (if you don't have the timer activated)
from traewelling.
Related Issues (20)
- Inconsistent UI: No new event selection with "drive along" feature HOT 1
- [Very Slow and locking Query] Global Dashboard
- [SlowQuery - 14 sec] select `statuses`.`user_id`, SUM(train_checkins.points) [...] HOT 2
- Don't show departures from current minute as departed
- Non-centered loading animation
- Lack of user interaction when errors occur during check-in HOT 1
- Remove mastodon connection on response "NO SUCH USER"
- 500 when accepting follow requests HOT 3
- No visual difference between drop-down menus and text inputs
- Missing "Remove stop" button in manual trip creation form
- Server error 500 when saving tags HOT 2
- Notification about mention in own status message
- Links in status messages not clickable but coincidentally contained Träwelling usernames clickable HOT 2
- Too many requested scopes HOT 1
- Bug report HOT 2
- Cannot check in for replacement trains (Ersatzzug) HOT 8
- Impossible to Check into train/select Destination HOT 10
- mastodon integration is forgotten instantly HOT 6
- Mastodon App creation done incorrectly
- Blank lines in status messages after emojis not visible
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from traewelling.