2019-11-14 04:17:24 +03:00
|
|
|
/- *rw-security
|
2019-10-01 02:25:25 +03:00
|
|
|
|%
|
|
|
|
+$ chat-view-action
|
2020-03-18 23:40:14 +03:00
|
|
|
$% :: %create: create a new chat
|
|
|
|
::
|
|
|
|
:: if :app-path and :group-path are different, :members must be empty,
|
|
|
|
:: as the :group-path is assumed to exist.
|
|
|
|
:: if :app-path and :group-path are identical, and the :group-path
|
|
|
|
:: doesn't yet exist, will create a new group with :members.
|
|
|
|
::
|
|
|
|
$: %create
|
2020-02-28 03:14:07 +03:00
|
|
|
title=@t
|
|
|
|
description=@t
|
2020-02-26 00:23:07 +03:00
|
|
|
app-path=path
|
|
|
|
group-path=path
|
2019-11-14 04:17:24 +03:00
|
|
|
security=rw-security
|
2020-02-04 22:12:51 +03:00
|
|
|
members=(set ship)
|
2019-11-14 03:53:47 +03:00
|
|
|
allow-history=?
|
|
|
|
==
|
2020-02-26 00:23:07 +03:00
|
|
|
[%delete app-path=path]
|
|
|
|
[%join =ship app-path=path ask-history=?]
|
2020-03-13 20:13:44 +03:00
|
|
|
:: %groupify: for unmanaged %village chats: recreate as group-based chat
|
|
|
|
::
|
|
|
|
:: will delete the old chat, recreate it based on a proper group,
|
|
|
|
:: and invite the current whitelist to that group.
|
|
|
|
:: existing messages get moved over.
|
|
|
|
::
|
2020-03-18 23:54:28 +03:00
|
|
|
:: if :existing is provided, associates chat with that group instead
|
|
|
|
:: of creating a new one. :inclusive indicates whether or not to add
|
|
|
|
:: chat members to the group, if they aren't there already.
|
|
|
|
::
|
|
|
|
[%groupify app-path=path existing=(unit [group-path=path inclusive=?])]
|
2019-10-01 02:25:25 +03:00
|
|
|
==
|
|
|
|
--
|