[Owncloud] Inter-ownCloud Sharing

Mon May 28 08:13:51 UTC 2012

I agree with Jan,

user to user sharing, without the admin, is significantly cooler and more useful for users then requiring that the admin "connects" the servers.
It would be very very cool if we could implement it like this.

webfinger is a great way to discover other users. The problem is that it is not always available. It works only if you install ownCloud into the webserver root and some users might also consider it a security hole and switch it off. 
So it would be great if the sharing system would also work without webfinger.
Just without autocompletion obviously.

I´m not sure if "frank at franksowncloud.org" is the best syntax for a user "frank" on owncloud "franksowncloud.org". Users will most likely confuse this with an email address.
Perhaps we should try to find a different syntax for that.

frank!franksowncloud.org/owncloudfolder  or
(frank)franksowncloud.org/owncloudfolder or
frank=franksowncloud.org/owncloudfolder  or
frank/franksowncloud.org/owncloudfolder  or
frank%franksowncloud.org/owncloudfolder  

Frank

On 27.05.2012, at 17:24, Nils Jansen <nilsjansen at gmail.com> wrote:

> i agree. If nils at ownid.net wants to share something with
> frank at franksowncloud.org he needs to know his webfinger. The already
> existing user/group form field for shareing files, folders, calendars &
> events should be able to handle these external webfingers.
> 
> I think this would be most intuitive and least complicated on both devel
> and usability side.
> 
> The "accept sharing offer" feature and notification should be
> implemented globally, not only for inter owncloud sharing, no?
> 
> Looking forward to this feature very much,
> 
> Nils
> 
> Am 27.05.2012 11:26, schrieb Christophe M:
>> 2012/5/26 Michael Gapczynski <mtgap at owncloud.com
>> <mailto:mtgap at owncloud.com>>
>> 
>>    On Saturday, May 26, 2012 07:50:45 PM Bartek Przybylski wrote:
>>>> I agree this is it how it should be done. Bartek would you like to
>>>> comment?
>>> 
>>> Decision of binding owncloud instances only by admins was made for
>>> save resources and restrict access to information about instance.
>>> Binding between instances should allow instances to exchange
>>> information like userlist, groups etc.
>>> Obviously accessing sharing only by single user should also by
>>> available, but i dont remember did i point it out while proposal
>>> review.
>>> 
>> 
>>    Relying on admins to bind instances is too much restriction on who
>>    you can
>>    share with. I don't understand how this method saves any resources.
>> 
>>    Exchanging the list of users and groups might be nice, but I don't
>>    see why
>>    this is necessary. The main use case I see for sharing between
>>    instances is
>>    for two individuals with their own independent instances. Sharing
>>    with a group
>>    or looking through the user list on a different instance sounds really
>>    strange.
>> 
>>    The best possible solution is to integrate sharing with the contacts
>>    app and
>>    allow the linking of a contact to a remote ownCloud instance user.
>>    In the same
>>    fashion as Jan-Christoph pointed out with frank at franksowncloud.org
>>    <mailto:frank at franksowncloud.org>.
>> 
>>>> I noticed in your proposal that this is focusing on files.
>>    Please note
>>>> that
>>>> I'm working on refactoring sharing to work with other app content.
>>>> 
>>>> I'm starting to think that this project shouldn't be an app. I
>>    strongly
>>>> believe this should be a REST API in the public namespace for
>>    apps to
>>>> register specific actions with. We eventually need something so
>>    files can
>>>> be shared, reverted to past versions, etc. from desktop and mobile
>>>> clients. Apps other than just sharing should be able to talk between
>>>> instances and have actions triggered by remote clients. Doing this
>>>> separate from interc-ownCloud sharing will just be duplicating work.
>>> 
>>> Project beeing api instead of app, im not sure how that was mixed up.
>>> file sharing app was suppose to be example of api usage
>> 
>>    I don't understand what you mean.
>> 
>>    _______________________________________________
>>    Owncloud mailing list
>>    Owncloud at kde.org <mailto:Owncloud at kde.org>
>>    https://mail.kde.org/mailman/listinfo/owncloud
>> 
>> 
>> 
>> 
>> Hi !
>> 
>> Well I think that there is two completely different use case :
>> 
>> - Connect completely two OC instance to allow sharing between each users
>> of the two instance as if it was only one instance (the current proposal
>> with user list, ...). That one should be admin driven. May be used to
>> connect for example two enterprise  .. 
>> 
>> - Simple user sharing between two user of different instance. Knowing
>> the user name and the domain of the remote user ('B'), 'A' can initiate
>> a sharing request with 'B' to share files with him without needing admin
>> permissions ('B' do you want to be my friend). You have to know the
>> other user. After the sharing request is accepted, 'A' and 'B' can share
>> files. 'B' will never appear in the sharing list of 'C' on the same
>> server as 'A' as the share link is between 'A' and 'B'. This scenario is
>> more for "social" sharing.
>> 
>> 
>> Christophe
>> 
>> -- 
>> ----------------------------------------------------
>> 
>> Un poing levé, une main tendue
>> 
>> 
>> 
>> _______________________________________________
>> Owncloud mailing list
>> Owncloud at kde.org
>> https://mail.kde.org/mailman/listinfo/owncloud
> 
> -- 
> Nils Jansen
> Hermannstraße 48, 2. HH
> 12049 Berlin
> tel +49 (0)30 28376529
> fax +49 (0)30 8687048089
> mob +49 (0)176 23553612
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/listinfo/owncloud