New feature for great suggestion list: Blogpost/Travelstories and Events
-
@Timo-Martosatiman-MRA
There is an issue with Blogpost/Travelstories and Events:Blogpost/Travelstories can be published by one simple click. But then its total public. Before, both are not able to be found by other Users. But when published it can be found by everyone. Generally, this is acceptable.
Events can be configured as public or as private. But just if event is configured as private, it can be found by everyone. Also everyone can read description (Information) and can see participants of this event! Only routes, tracks and moments are only visible for participants.
This is really not acceptable! If an event is private, it mußt be private at all - like Blogpost/Travelstories.But the two options: private and public, does not fit our needs. Additionally, we need for Blogpost/Travelstories and Events some more privacy options: for friends, for groups, for participants and total public.
It's essentially, to get this feature if you will have Events. Subsequently, ther is a naturally need to share common experience with all event members. But seriosly, in most cases only with team- or event members!
Not only German Law about data protection, does not allow to share private information or fotos from people without their consent form. In other words: as organizer of an event, you will not be able to share any information of the event, as long as simply one member has not giving his formal agreement. But many people are willing to share it with team or group - but not all the time with total public!Would you please so kind, to put this on the great suggestion list?
Nothing is impossible ;-)
In past: GARMIN Zumo 210->GARMIN Zumo 395->GARMIN XT=> now: DMD T865-X + MyRoute-App, LocusMaps, OsmAnd.
In past: GARMIN MapSource ->GARMIN BaseCamp->Tyre->Kurviger->Calimoto=> now: MRA-Routplanner. -
@Guzzist said in New feature for great suggestion list: Blogpost/Travelstories and Events:
There is an issue with Blogpost/Travelstories and Events:
Blogpost/Travelstories can be published by one simple click. But then its total public. Before, both are not able to be found by other Users. But when published it can be found by everyone. Generally, this is acceptable.
Events can be configured as public or as private. But just if event is configured as private, it can be found by everyone. Also everyone can read description (Information) and can see participants of this event! Only routes, tracks and moments are only visible for participants.
This is really not acceptable! If an event is private, it mußt be private at all - like Blogpost/Travelstories.
But the two options: private and public, does not fit our needs. Additionally, we need for Blogpost/Travelstories and Events some more privacy options: for friends, for groups, for participants and total public.
It's essentially, to get this feature if you will have Events. Subsequently, ther is a naturally need to share common experience with all event members. But seriosly, in most cases only with team- or event members!
Not only German Law about data protection, does not allow to share private information or fotos from people without their consent form. In other words: as organizer of an event, you will not be able to share any information of the event, as long as simply one member has not giving his formal agreement. But many people are willing to share it with team or group - but not all the time with total public!
Would you please so kind, to put this on the great suggestion list?Good Point!
-
@Timo-Martosatiman-MRA
There is an issue with Blogpost/Travelstories and Events:Blogpost/Travelstories can be published by one simple click. But then its total public. Before, both are not able to be found by other Users. But when published it can be found by everyone. Generally, this is acceptable.
Events can be configured as public or as private. But just if event is configured as private, it can be found by everyone. Also everyone can read description (Information) and can see participants of this event! Only routes, tracks and moments are only visible for participants.
This is really not acceptable! If an event is private, it mußt be private at all - like Blogpost/Travelstories.But the two options: private and public, does not fit our needs. Additionally, we need for Blogpost/Travelstories and Events some more privacy options: for friends, for groups, for participants and total public.
It's essentially, to get this feature if you will have Events. Subsequently, ther is a naturally need to share common experience with all event members. But seriosly, in most cases only with team- or event members!
Not only German Law about data protection, does not allow to share private information or fotos from people without their consent form. In other words: as organizer of an event, you will not be able to share any information of the event, as long as simply one member has not giving his formal agreement. But many people are willing to share it with team or group - but not all the time with total public!Would you please so kind, to put this on the great suggestion list?
@Guzzist you have a point here. GDPR is a european legislation, applies to the whole EU, and stands model for the rest of the world.
I know also that it can be a pain to apply correctly and can hav negative consequences for "innocent" people and websites while it is targetting, amongst others, the big internet sharks that trade on private data
