aboutsummaryrefslogtreecommitdiffstats
path: root/doc/de/main.bb
diff options
context:
space:
mode:
authorzotlabs <mike@macgirvin.com>2017-10-10 22:02:22 -0700
committerzotlabs <mike@macgirvin.com>2017-10-10 22:02:22 -0700
commitff8ee6fb2250d2188962f4b27de91b89465cc3d5 (patch)
treeb8b62ec3f45683ce3d46180e90b21c3d6d16efaa /doc/de/main.bb
parent1a7ccc462b8aeea7704562b8d14d31e3bcb41622 (diff)
downloadvolse-hubzilla-ff8ee6fb2250d2188962f4b27de91b89465cc3d5.tar.gz
volse-hubzilla-ff8ee6fb2250d2188962f4b27de91b89465cc3d5.tar.bz2
volse-hubzilla-ff8ee6fb2250d2188962f4b27de91b89465cc3d5.zip
for federated forums we need to keep track of what protocols are available to red/hubzilla channels to determine which posts need to be mangled for transport to individual networks - based on what networks the author can communicate with. We probably need this for all xchans and hublocs but at some point it becomes increasingly difficult to scrape this information and map out a compatibility matrix. It's also doubtful anybody will use this system because we basically have to forge comments between network sites involving different protocols and this is going to look like crap to anybody that isn't on red/Hubzilla. Eventually they have to fix their protocols for this to work correctly, but nobody seems to believe me that their networks are basically anti-federation, so we need something like this to highlight their walled garden specifications and the resulting federation problems in a form they can't really argue with.
Diffstat (limited to 'doc/de/main.bb')
0 files changed, 0 insertions, 0 deletions