allow sharing

Wed, 15 May 2019 14:24:13 -0700 zuletzt bearbeitet: Wed, 15 May 2019 14:25:02 -0700

RockyIII

rockyiii@huby.infozoo.de

If I want to allow my followers to share my post the only working setting in
Channel Permission Limits > Can view my channel stream and posts
is “Anybody on the internet”    -         right or do I miss here somthing ?

What does  “Can source my public posts in derived channels”  actually configure  –  not the sharing option right?

!zotlabs.org | Hubzilla Development  !Hubzilla Support Forum

mehr anzeigen 11

Wed, 15 May 2019 14:49:02 -0700

people who for some reason receive your public posts in /network can then share the posts.

Wed, 15 May 2019 16:56:29 -0700

Remember, only public posts can be shared.

Wed, 15 May 2019 23:49:05 -0700

RockyIII

rockyiii@huby.infozoo.de

thanks

has the setting in “Can source my public posts in derived channels”

effect on the use of the "Channel Sources" plugin

Thu, 16 May 2019 01:19:55 -0700

El Dorado

mike@z.macgirvin.com

yes

Thu, 16 May 2019 03:34:55 -0700

RockyIII

rockyiii@huby.infozoo.de

Now if I set „Channel Permission Limits“ > „Can view my channel stream and posts“ to „Any connections“

the posts are marked as “Private Message” and still are delivers to HZ contacts… but Mastodon connections seam not to get this posts…

is this a know behavior ?
is this a feature which would work with OSADA ?

Thu, 16 May 2019 04:33:24 -0700

El Dorado

mike@z.macgirvin.com

is this a know behavior ?

Yes.

is this a feature which would work with OSADA ?

No.

I'll be frank. You are not an expert and should not be messing with expert permissions.

I'll be even more frank. Even if you think you are an expert and understand all the nuances of the permission system, do not change this particular permission. Ever.

Thu, 16 May 2019 04:38:59 -0700

RockyIII

rockyiii@huby.infozoo.de

I'll be frank. Don´t like what you are saying

Thu, 16 May 2019 05:08:13 -0700

El Dorado

mike@z.macgirvin.com

I'm trying to save you some grief and perhaps compromised privacy. But you're the expert. Do what you want.

Thu, 16 May 2019 05:37:08 -0700

RockyIII

rockyiii@huby.infozoo.de

Thanks Mike
and
Thanks  everybody who answering my questions.

Still learning,
sill no export
even if I use HZ since quiet some time now – what a great system – what dummy I´m

The options in the Security and Privacy Settings  are actually the reason why I still hang around here, even I´m  not an export and Linux freak – Yes man-

The pre defined Roles in “Channel role and privacy“ are just working fine indeed for most of the time… since few days now i try to accomplish something which is not a common case and I tried again some settings in the „Custom/Expert Mode“

playing around with the settings I discovered again what fantastic options HZ offers

Now looking at the options at  „Channel Permission Limits“ > „Can view my channel stream and posts“

Maybe it is an translation which is causing irritations

In German there is an given option called “Alle Hubzilla Mitglieder” - “Anybody in this network”
than on the other hand “Beliebige Verbindung” - „Any connections“ sounds like - that this option should work also with mastodon connections -

I know that AP connections are not compatible with some HZ features - that’s why I was wondering if OSADA would be working for this case…

anyway…

love you

Thu, 16 May 2019 10:59:46 -0700

I also like a lot the „Custom/Expert Mode“ ... but,

at the programming level we risk entering a "if" maze from which it is difficult to disentangle ...
so I understand well if then someone says: I do not assure you that in the present and future I will fix the bugs concerning this part.
Too many things to consider, too many plots ... too many compromises, which don't always work together.

Thu, 16 May 2019 13:21:52 -0700

El Dorado

mike@z.macgirvin.com

For anybody aspiring to be an expert, here are the details.

"Can view my channel stream and posts" is unlike *all* of the other permissions. All of the other permissions are enforced by your server. This particular permission needs help "at the other end" of the communications stream to work perfectly (if changed from the default setting). There are some problems with this.

1. No other network is aware of this permission, so they won't have any "helper code" at the other end.
2. Even if they did, you privacy cannot be assured because they could alter it.
3. If such a message is delivered to a network which has no helper code, it is unable to distinguish the message from a public message. Many systems will deliver such a message to their "public stream" as well as any followers you may have on that site.

I believe we have code in the pubcrawl (ActivityPub) and Diaspora addons which prevents your posts from being delivered to those networks for the reasons given if you've messed with this setting. So at one time, it was OK to use this setting as long as you didn't try and federate. Then Hubzilla 4.0 came along which connects to Zot6 servers. Zot6 servers do not have this helper code and messages to this network are not blocked. So now we have a problem.

If you would like to find the correct place in the code to fix this for Zot6 you can use the setting once again. However it still won't work with Mastodon - ever.

You may ask the question "Why didn't you fix this for Zot6 when adding the Zot6 code?"

Because it was a horrible idea to allow this setting to be changed in the first place for the given reasons. I want a network where privacy works, not where you have to explain arcane implementation details to people so they know when it does work and when it doesn't. In Zap/Osada, even if we allowed "expert" mode (which we don't as these projects were designed to be simple), we've disabled the ability to change this one setting. It is no longer provided.

The correct thing to do at this point would be to disable the ability to change this setting on Hubzilla also. It is officially deprecated. You are also certainly not the first person who tried to use it without understanding the issues involved. This will happen as we start to phase out the old Zot protocol and complete the transition to Zot6. This transition could take a few years and we simply haven't gotten to this piece of the intricate puzzle yet.