Commit graph

9 commits

Author SHA1 Message Date
nobody
a8e96322f0 it's done 2022-02-15 20:08:28 -08:00
nobody
ad52373312 move account and channel to zlib 2022-01-24 17:26:12 -08:00
zotlabs
87bfe83fd4 cleanup of really old and obsolete stuff from util 2020-07-01 23:03:34 -07:00
zotlabs
b44f194aa8 Deprecate the term 'master' from the codebase. 2020-06-15 00:29:56 -07:00
zotlabs
1d3540ac6c refactor include/follow (Connect::connect()) and update strings 2019-01-21 17:31:24 -08:00
zotlabs
4846ae5326 split off libsync from libzot 2018-06-04 18:40:11 -07:00
zotlabs
191edfdaa1 more heavy lifting 2018-05-31 21:05:09 -07:00
zotlabs
3e184ef403 z6 permissions work 2018-05-26 15:12:02 -07:00
zotlabs
b13fb1cca9 command line connect utility.
Usage: util/connect uid|nick channel

uid|nick must be a local channel. The target channel can be any channel. If a nick is supplied as a target it is assumed to refer to a channel on the localhost unless @host is provided. RSS feeds and remote networks can also be connected, assuming the appropriate protocols are already enabled for the local channel. If the target channel is a non-forum on the local system and you wish bi-directional communication to be enabled you will probably need to use a second connnect command with the source and target reversed.

Examples:

	util/connect bob marketing

	Connects bob to the marketing channel

	util/connect marketing bob

	Connects the marketing channel to bob.

	util/connect 6 channelone@macgirvin.com

	Connects the channel with channel_id 6 to the Channel One public forum.

	util/connect bob https://mysite.foo/feed.rss

	Connects bob to an RSS feed if RSS feeds are allowed as connections on this site

	util/connect bob jb@diasp.org

	Connects bob to a diaspora account on diap.org (both the site and Bob's channel must previously have the Diaspora Protocol enabled).
2016-11-01 15:27:34 -07:00