group migration #40
Labels
No Label
applications
BLOCKED
bug
design
duplicate
enhancement
fixed?
funding-needed
help wanted
infrastructure
invalid
payments
qubes
question
ready-for-implementation
refactor
spam
tapir-server
testing
tor
wontfix
No Milestone
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cwtch.im/cwtch#40
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
use cases:
If no-one is taking this I can jump onto it.
I'm thinking a series of functions in cwtch_peer.go?
@angus: This one needs some design before it is ready to be implemented. We have a meeting this week to go over some high level decisions and reach consensus on some which tasks are good to go and which need more design/thought - the issues should be in much better shape after Friday.
Sounds good, thanks. I'll dig around for some others I can work on.
After much discussion on this we've decided to move forward on a group-forking model.
The idea being that given the environment we can never assure the secrecy a group once there is a member that has been determined by the members to be adversarial (or not welcome etc.) - As such any mechanism we put in place to manage membership reduces to "setup another group".
Given that we plan to make "forking" groups very easy and build the metaphor around a cwtch group being a location (and if a location gets compromised is any way, then you have to move....)
More on this soon.